rdiff-backup behaves similar to rsync in this respect -- it requires enough temp space to make a copy+patch of your largest file... it doesn't update files in place (doesn't even have the option to do that).
btw you're doing something somewhat like another tool called dirvish does... rdiff-backup shouldn't be confused by files within its mirror which are hardlinked to files outside the mirror. -dean On Thu, 3 Aug 2006, [EMAIL PROTECTED] wrote: > Hi all, > > Sorry if this has been answered - the rdiff-backup wiki isn't working for me > at the moment (no response from the server). I couldn't find any posts > answering my question on this list. > > As per the subject line, I'm keen to pool storage on a central backup server > across backups from multiple machines (vaguely a la BackupPC). Say I had run > rdiff-backup from /usr on two client machines with target directories b1 and > b2 on the server respectively. > > Were I to write a script that checksumed (and then full-compared files) across > b1 and b2 and hard-linked those files that were identical, would I be at risk > of having the next rdiff-backup from b1 ever modify files as seen from b2? > > PS I'm very pleased with rdiff-backup - particularly the diffing within files. > > > _______________________________________________ > rdiff-backup-users mailing list at [email protected] > http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users > Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki > _______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
