>
> For files not in rdiff-backup-data: it doesn't. I just tested that. It
> creates a new file and then moves ("mv -f") it over the original file.
> A hard link retains the original contents.
> For files in rdiff-backup-data: i have no idea. You could try it out: cp
> -al, create md5sums for everything, then rdiff-backup again, then check
> the sums.
>
I tested rdiff-backup-data too, it seems like the only file that
changes is 'rdiff-backup-data/backup.log' which I don't think is ever
read by rdiff-backup at any stage (i think i read that in the man
page).
So I assume it's safe to hard-link copy the backup folder in case
something went wrong, even though rdiff-backup seems able to recover
from interrupted backups quite well (tried that too).
Somehow, I still trust tarballs more.
_______________________________________________
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
