On Thu, Jan 6, 2011 at 1:47 PM, Freddie Cash <[email protected]> wrote: > On Thu, Jan 6, 2011 at 11:33 AM, Marcin Kuk <[email protected]> wrote: >> Rsync is good, but not for all cases. Be aware of databases files - >> you should do snapshot filesystem before rsyncing. > > We script a dump of all databases before the rsync runs, so we get > both text and binary backups. If restoring the binary files doesn't > work, then we just suck in the text dumps. > > If the remote system supports snapshots, doing a snapshot before the > rsync runs is a good idea, though. It'll be nice when more > filesystems support in-line snapshots. The LVM method is pure crap.
do you also use the --in-place option for rsync? i would think this is critical to getting the most out of "btrfs folding backups", ie. the most reuse between snapshots? im able to set this exact method up for my home network, thats why i ask... i have a central server that runs everything, and i want to sync a couple laptops and netbooks nightly, and a few specific directories whenever they change. btrfs on both ends. better yet, any chance you'd share some scripts? :-) as for the DB stuff, you definitely need to snapshot _before_ rsync. roughly: ) read lock and flush tables ) snapshot ) unlock tables ) mount snapshot ) rsync from snapshot ie. the same as whats needed for LVM: http://blog.dbadojo.com/2007/09/mysql-backups-using-lvm-snapshots.html to get the DB file on disk consistent prior to archiving. C Anthony -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
