On 06/06/2012 02:10 AM, Florian Kaiser wrote:
The creators were aware of this and build in a verify-at TIME option.
Using this after each backup will make a test-restore of every file up
to the given timestamp and thus verify each increment, giving you the
guarantee that you will be able to restore up to that state.
That is dangerously misleading.
A) The test only verifies that the files that existed at TIME can be
restored to their state at that time. Such a restoral might or
might not make use of all the intermediate increments between the
current mirror and the given TIME.
B) There is no test that a restore to any other time can be performed
without error. The only checksum that is verified is the one for
the given TIME. The only mirror_metadata file (which is where the
checksums are stored) that is read is the one for the given TIME.
The mirror_metadata files for other times could be corrupted or
missing, and no error will be reported.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
_______________________________________________
rdiff-backup-users mailing list at [email protected]
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
