hi david,
> However, if I get Tim right, he is talking about an interrupted _initial_
> backup run. In this case, giving up the entire history obviously does not do
> any harm. Without any metadata (i.e. the rdiff-backup-data subfolder), afaik
> a forced rdiff-backup run will take whatever there is in the target folder
> as a base and won't retransfer existing parts. So my solution might be the
> right thing to do in this special case.
thanks for your explanations ... i was a bit confused to see a lot of
"Processing changed file" messages of files which have already been
transferred ... could be that checksumming these files is a performance
bottleneck on the NAS device ... so doing the rdiff-backup locally and
uploading via rsync might be an option ...
thanks, tim
_______________________________________________
rdiff-backup-users mailing list at
rdiff-backup-users@...
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-usersWiki URL:
http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
