ubuntu14.04 LTS / duplicity 0.6.23 / hash trouble when trying to restore
I have created a full backup (approx. 262GB) using version 0.6.23. Backup destination was a folder on an external USB drive. During backup, the power supply of the USB drive was interrupted and the backup stopped.
Repeating the last (full) backup command line I was happy that it found the latest volume and appeared to take the appropriate actions, here's part of the out (luckily, I had saved all logs, both of the first and the second run):
[...]
Found primary backup chain with matching signature chain:
-------
Chain start time: Sun Apr 5 18:05:44 2015
Chain end time: Sun Apr 5 18:05:44 2015
Number of contained backup sets: 1
Total number of contained volumes: 2338
Type of backup set: Time: Num volumes:
-------
No orphaned or incomplete backup sets found.
PASSPHRASE variable not set, asking user.
PASSPHRASE variable not set, asking user.
RESTART: Volumes 2338 to 2338 failed to upload before termination.
Restarting backup at volume 2338.
Deleting /tmp/duplicity-
Restarting after volume 2337, file andreas_
A .
A andreas_home
A andreas_
A andreas_
A andreas_
A andreas_
A andreas_
[...]
I did "check" the archive using the "--list-
Now when trying to do the full restore I get hash mismatches. Looking through existing reports I found there are tons of these bug reports, mainly back in the older versions, but if I had known I would have refrained from using duplicity and rather done a simple copy/paste backup. aaargh.
I get this kind of errors:
[...]
Writing 10 Aqua/80 Dienstleister/
Deleting /tmp/duplicity-
Processed volume 7 of 8661
Invalid data - SHA1 hash mismatch for file:
duplicity-
Calculated hash: a229d6d62c6c0cb
Manifest hash: b90a7f7e93407f3
...which causes the process to stop.
question 1) what is the command-line option to skip the problematic volume/file and carry on? --force and --ignore-errors won't do the job.
For now, I only found descriptions of how to manually extract the surviving files, but I have to admit I am not looking forward to do this with 500'000 files manually.
I have 8661 volume files, each having a size of 26.3MB (5631 volumes) or 26.2MB (3030 volumes). The very last volume #8661 has got only 26.1MB size. So it looks to me as those files were "complete".
question 2) any hints what is going wrong and how to do a clean restore?
Many thanks in advance,
Andreas.
PS: Gave it another try after upgrading to version 0.7.02, same behaviour.
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Duplicity Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask Andreas for more information if necessary.