FullFileCompare
From RdiffBackupWiki
It would be cool to be able to check the backup against the actual files to make sure that everything is ok.
my understanding is that normally rdiff-backup doesn't do compares unless it has reason to believe a file has changed; doing needless compares would obviously slow down the backup process.
A mode to do a seperate comparison pass without making a backup, or (probably less good) an option to tell rdiff-backup to always compare everything when backing up, regardless of metadata changes, would be helpful.
-- Andrew Bressen <bressen@savannah.nongnu.org>
0.13.4 now has this feature. I haven't tested it yet, but it should be cool. see the changelog for details
-- Dave Kempe
There's a compare feature now, but it only does metadata. This is much quicker obviously and has its uses, but the original idea is still a good one. Moving back to unimplemented suggestions :)
-- BenEscoto
I think this is implemented in the current version. The manpage for 1.1.5 describes:
--compare-full
This is equivalent to '--compare-full-at-time now'
--compare-full-at-time time
Compare a directory with the backup set at the given time. To
compare regular files, the repository data will be copied in its
entirety to the source side and compared byte by byte. This is
the slowest but most complete compare option.
--compare-hash
This is equivalent to '--compare-hash-at-time now'
--compare-hash-at-time time
Compare a directory with the backup set at the given time. Reg-
ular files will be compared by computing their SHA1 digest on
the source side and comparing it to the digest recorded in the
metadata.
-- Andrew Ferguson
Nevermind, the --compare-full and --compare-hash features merely compare the files in the repository against what we expect to be there. (ie, verify the repository)
What this Feature Suggestion is for is rsync's --checksum option, which is to calculate a checksum for each file *during* the backup, and use that (instead of file size & modification time) to determine whether the file needs to be backed-up at all.
Moving back to unimplemented suggestions. :-)
-- Andrew Ferguson
This is essential (at least an option) to ensure the integrity of the backup. It would take more time, but how else are you sure that the backup is correct? Given that this is missing, I'm starting to wonder if should be using rdiff-backup. --Bod, 24 Feb 2012
Back to SuggestedFeatures
