Re: [BackupPC-users] Howto backup BackupPC server

[Brien Dieterle]

Ludovic Gele wrote: Selon Brien Dieterle <[EMAIL PROTECTED]>: I don't think another instance of backuppc would work "very well" for a number of reasons. However, I think you could do well with copying the raw block device over netcat or ssh. If you are using LVM for the backuppc data you could take a snapshot and not affect regular backups, otherwise you should stop backuppc and unmount the partition first (you are using a dedicated partition, right? ;-) ) Couple tips if you try this: set the readahead on the block dev fairly high before you start dd (blockdev --setra 16384 /dev/device). Then pipe it out with dd and compress it with lzop ( dd if=/dev/device bs=10M | lzop -1c |nc host port). On the receiving end you'd run something like nc -l -p port >diskdump. This is what I use for LAN, but for slow links you'd probably want more compression. For good measure you might want to zero out the extra space on the drive before you dump it (dd if=/dev/zero of=blah bs=1M ; rm blah). Of course, this would require quite a bit of disk space and would limit your backup intervals and retention policies... Any other ideas, List? Hi folks, Why not drbd or unison? I think unison doesn't handle hard links and might have the same memory problems as rsync.  DRBD might actually be a good idea.  However, just using drbd incurs a small performance hit even when you're not syncing.  For offsite, you'd certainly want to use protocol A which allows for inconsistency.  However, I am not sure what would happen over an extremely slow link (you can only seem to have a certain amount of changes waiting on the sending side).  Another option could be to run the offsite system offline and only turn on the syncer during the day when no backups are running-- however that might actually move a lot of extra data to sync the entire chunks of the disk that were modified. Looks like we're all waiting for Rsync 3.0 to be released, which may or may not actually solve our problems :-) Oh, and it sounds like we're really talking about adding redundancy, not "backups", which might imply having revisions, etc.  If your pool gets corrupted or deleted, you better know about it before your Rsync job trashes your copy-- if you are using drbd you are already toast :-) So, I think the word is: don't bother.  Use the archive features in backuppc to archive your machines to USB or other offline media.  :-) brien

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/