Hi Greg,
On Mon, 17 Mar 2008, Greg Freemyer wrote:
I also maintain a local and offsite rdiff backup copy.
But I only have rdiff create the first copy. Then I rsync that to my
offsite location.
I have about 150GB of data I backup. rdiff + rsync takes about 45
minutes most nights if there is not a significant change to my dataset.
(FYI: I have a number of spindles involved via raid, so I'm not slowed
by disk i/o as much as one might expect.)
The bad news is that if my first set gets corrupted, then rsync will
relay the corruption out to the offsite copy. My reason for two copies
is disaster recovery, not backup repository corruption. May need to
rethink that based on this discussion.
What I've started doing to work around this is to rsync the original data
(not the rdiff-backup copy) offsite and run rdiff-backup locally on the
remote server. Not perfect, I end up with two copies of all the data on
the remote server, but at least it does work and appears to save
bandwidth.
Cheers, Chris.
--
_____ __ _
\ __/ / ,__(_)_ | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Ruby/Perl/SQL Developer |
\__/_/_/_//_/___/ | We are GNU : free your mind & your software |
_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
