steve.du...@pgcmls.info schrieb: > Dear all, > > A friend recommended that I use rdiff-backup to maintain a back up of an > inconveniently large, reasonably slowly changing file repository. > > I would like to keep the back up copy on a warm standby system, so that if > the primary host fails, I can reconfigure the standby to replace it. > > I understand that modifying the back up files will invalidate the rdiff > snapshots. > > Is there a sane way of keeping the snapshots valid that does not involve > maintaining a second back-up copy?
I think you will need LVM snapshots for this. When the standby goes hot, create a read/write snapshot of the backup, make that snapshot available to the clients. > > When the primary host comes back up, are there any extraordinary > considerations for updating its repository ? You will have to push the changes in the snapshot somehow to the primary (rsync -au ?). Then you can destroy the snapshot and do business as usual. Jakob _______________________________________________ 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
