Verify should not compare anything with filesystem (mtime, permissions or file contents etc) unless --compare-data is used
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Refer to the mailing list discussion here:
http://
By default verify should not be concerned with the current (post-backup) contents of the filesystem at all, whether that is actual file contents or timestamps. This is particularly the case now that we have the --compare-data option that people can use if they want this functionality.
The comparison of dates/modtimes should only be carried out if --compare-data is used. On that basis, verify should not give an error if the file-system changes after the backup, so long as it can restore the files and they match the signatures from the time of the backup.
Once this behaviour is implemented, the man page should read:
"Enter verify mode instead of restore. Verify tests the integrity of the backup archives at the remote location by checking each file can restore and that the restored file matches the signature of that file stored in the backup, i.e. compares the archived file with its hash value at archival time. Verify does not actually restore and will not overwrite any local files. If the --file-to-restore option is given, it will restrict verify to that file or directory. The --time option allows the selection of a specific backup to verify. Duplicity will exit with a non-zero error level if any files do not match the signature stored in the archive for that file. On verbosity level 4 or higher, it will log a message for each file that differs from the stored signature. Files must be downloaded to the local machine in order to compare them. Verify does not compare the backed-up version of the file to the current local copy of the files unless the --compare-data option is used (see below)."
Related branches
Changed in duplicity: | |
importance: | Undecided → Medium |
milestone: | none → 0.7.01 |
status: | New → Fix Committed |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
Please find attached a Bash script that shows the current behaviour of verify.