corrupted backup, CRC check failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
New
|
Undecided
|
Unassigned |
Bug Description
duplicity 0.6.10 and 0.6.11
I have a 22G backup that is corrupted. That was being backed up from an OSX MacBook Pro with duplicity 0.6.10 compiled against OSX 10.5's python (Leopard). I can't check the exact version as this machine died now. The data was being backed up to Amazon S3.
I am trying to recover the backup on a Linux machine with duplicity 0.6.11 after copying the data locally, but it fails with a CRC error after about 5G of data being processed. I was able to recover more of the data past the initial CRC check failure by asking for specific folders and files, and I eventually narrowed things down to a short list of files that could not be recovered. I am attaching the error log for the first file that I can not recover.
I doubt there is much way to recover all the individual files at this point, but I thought I'd point out a few things:
- I highly recommend the --test-restore option getting done (https:/
- It took some serious script-fu to continue recovering past the initial CRC error. There's still a significant amount of data that is lost, but it's not that bad. Duplicity should have an option to continue working through the backup and attempt to recover as much as it can.
I was also struggling with a CRC error over the past week. I would also request a --test-restore option and being able to pass over CRC errors.