want a "check" command
Bug #660895 reported by
Martin Pool
This bug report is a duplicate of:
Bug #1354880: Verify should not compare anything with filesystem (mtime, permissions or file contents etc) unless --compare-data is used.
Edit
Remove
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Duplicity |
New
|
Undecided
|
Unassigned | ||
Bug Description
It would be nice if duplicity had a "check" command, that checked the internal consistency of the backup without actually restoring it.
The 'verify' command is not enough, because it tells me "is it the same as local disk" not "could this be restored?" If local disk changes while the backup is underway, verify is always going to fail.
Ideally there would be two variations, a cheap one that only reads metadata and an expensive one that reads back all of the increment files.
Revision history for this message
| Aaron Whitehouse (aaron-whitehouse) wrote | #1 |
To post a comment you must log in.
Martin, thank you for your bug report. I believe that this should now be resolved by using the verify command on recent versions of duplicity (without the --compare-data flag). Please let me know if this does not satisfy your requirements.