Ticket #2512 (closed defect: worksforme)
Duplicity Restore - Error output: Invalid data - SHA1 hash
| Reported by: | anonymous | Owned by: | jamor@… |
|---|---|---|---|
| Milestone: | 2.0.X | Component: | base |
| Severity: | normal | Keywords: | |
| Cc: | satyris@… |
Description
When i try to restore my backup with Duplicity (GUI or command --> same result), there were failures.
root command /usr/share//ebox-ebackup/ebox-duplicity-wrapper --force -t 1289221211 --file-to-restore etc/zarafa file:///home/admint2s/zenbackups --no-encryption /etc/zarafa failed. Error output: Invalid data - SHA1 hash mismatch: Calculated hash: bcacd4556799a5f9df422ae3856b9cf98c233504 Manifest hash: 6b8377f45b33735c731b2335659417dabda1f799 Command output: Local and Remote metadata are synchronized, no sync needed. Last full backup date: Mon Nov 8 14:00:11 2010 . Exit value: 21
So far i understand, its a problem with different Hashes, but dont know why that?!
I tried it with:
duplicity restore --file-to-restore /etc/zarafa --restore-time 2010/11/08 file:///xxx/xxxx/zenbackups --no-encryption /tmp/zarafa
but no luck.
Attachments
Change History
comment:2 Changed 3 years ago by javier.amor.garcia@…
Hello,
this may be a bakcup corruption so the calculated file md5 does not match with the manifest's stored md5. However ometimes duplicity error messages are a bit misleading so it would be interesting to rerun the command with th '-v9' switch to see full output. Could you do so and attach here the output so we could examinate better the case?
Thanks
comment:3 Changed 3 years ago by javier.amor.garcia@…
Another thing, after getting the log you coudl try to restore it with the --force parameter.
comment:4 Changed 3 years ago by jamor@…
- Status changed from new to closed
- Resolution set to worksforme
Since there is mot more input I suppsoe the user has solved its problems with '--force' and the error was caused by the backup's storage.
If I am wrong, please reopen this ticket
comment:5 Changed 2 years ago by satyris@…
- Status changed from closed to reopened
- Resolution worksforme deleted
The situation: My zentyal-server has made a fullbackup (duplicity) in filesystem. This files are transfered
with FTP to my Fritzbox/Usbstick?. Then i tried to copy this files to a virtualbox zentyalserver
with duplicity. If i use the option --file-to-restore everything is fine, but if i use the
normal restore option i get an error "invalid data - SHA1...".
Invalid data - SHA1 hash mismatch: Calculated hash: 874cd0a48936861ea85d97779e9c7cf6362d33a8 Manifest hash: 5991cbc59a6a49dd50244a1c5c49ecc910251c13
What i did:
- removed the ~/.cache/duplicity Directory
- tried the whole process again and again
- tried it with backup on an usbHD
duplicity restore ftp://ftpuser:xxx@fritz.box/Verbatim-STORENGO-01/zenbackups / --no-encryption --force -v 9
I dont understand why the first volumes are fine, but then the hashes mismatch?
Processed volume 3 of 214 Registering (mktemp) temporary file /tmp/duplicity-n5Tu03-tempdir/mktemp-6Fibxw-6 Running 'ncftpget -f /tmp/duplicity-n5Tu03-tempdir/mkstemp-3GdlPn-1 -F -t 30 -o useCLNT=0,useHELP_SITE=0 -V -C 'fritz.box' 'Verbatim-STORENGO-01/zenbackups/duplicity-full.20110408T121533Z.vol4.difftar.gz' '/tmp/duplicity-n5Tu03-tempdir/mktemp-6Fibxw-6'' (attempt #1) Invalid data - SHA1 hash mismatch: Calculated hash: 354b3df86aa329b06a5fadac51ffef194d0ccca8 Manifest hash: fc7a6b7257bc4952062e3da59e7d4fe1ef769c28 Removing still remembered temporary file /tmp/duplicity-n5Tu03-tempdir/mktemp-6Fibxw-6 Removing still remembered temporary file /tmp/duplicity-n5Tu03-tempdir/mkstemp-3GdlPn-1 Removing still remembered temporary file /tmp/duplicity-n5Tu03-tempdir/mkstemp-D67PM_-2
comment:6 Changed 2 years ago by jacalvo@…
- Status changed from reopened to closed
- Resolution set to worksforme
Have you tried upgrading to the last duplicity version (0.6.13, published 6 days ago is the last available). Reopen if still happens after the upgrade.
comment:7 Changed 2 years ago by satyris@…
- Status changed from closed to reopened
- Resolution worksforme deleted
Sorry, tried it with duplicity 0.6.13 on both machines and no luck.
Processed volume 4 of 226 Registering (mktemp) temporary file /tmp/duplicity-DVMSlw-tempdir/mktemp-0d1_YO-6 Invalid data - SHA1 hash mismatch: Calculated hash: 72f8f18e81764dcf2cdb11f7a7e9a3db2adf7283 Manifest hash: fc83c667cc44a33a39df03ce7a1280888fd4ea5d Removing still remembered temporary file /tmp/duplicity-DVMSlw-tempdir/mkstemp-QFN1OO-1 Removing still remembered temporary file /tmp/duplicity-DVMSlw-tempdir/mktemp-0d1_YO-6
The only difference is real machine is AMD64 and virtual (virtualbox) one is i386
comment:8 Changed 2 years ago by jacalvo@…
- Owner changed from javier.amor.garcia@… to jamor@…
- Status changed from reopened to new
comment:9 Changed 2 years ago by jamor@…
- Status changed from new to closed
- Resolution set to worksforme
This seems a data corruption.
If restore with --force does not work try the restoration by hand: https://live.gnome.org/DejaDup/Help/Restore/WorstCase#Restoring_by_Hand