Backup Central

I've found that for my data (local backup to different disk), rdiff-backup
spends a lot of its time dealing with deleted (or renamed -- though I
understand the limitation there) files. I switched to --no-compression, since
space is not a major issue, and it got somewhat faster, but it still spends a
lot of time copying files from the mirror into increments snapshot before
deleting the mirror.

Would it be possible to make it rename the file in this case, instead? It
looks like might be possible to have increment.makesnapshot detect this case,
but someone who's more familiar with the code would probably have a better
idea.

(Note that I haven't tried the development version, only glanced at the
changes, so if this is already supported somewhere that'd be great to know.)

_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

The attached patch seems to do what I want, and makes my incremental backup at
least twice as fast. However, I haven't been able to test it in all
scenarios, so I'd appreciate feedback. In particular, there are probably some
error conditions I should catch, or other situations in which a rename won't
work. It could also be done with hardlinks to avoid the change in backup.py,
but that would only work for regular files.

(Patch applies to both CVS and 1.2.8.)

_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki