duplicity-team team mailing list archive

[edso <question264557@xxxxxxxxxxxxxxxxxxxxx>]

Question #264557 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/264557

    Status: Open => Answered

edso proposed the following answer:
On 03.04.2015 18:16, Domoradov Alex wrote:
> New question #264557 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/264557
> 
> Hello,
> 
> I'm using the following system
> 
> OS: CentOS-6, x64. duplicity-0.6.22-3.el6.x86_64. Today I have encountered with issue during restore process
> 
> # duplicity -t 3D --force restore file:///backup/vhosts/ /home/restore/
> 
> Last full backup date: Sun Mar 22 22:07:29 2015
> Invalid data - SHA1 hash mismatch for file:
> duplicity-full.20150322T220729Z.vol16.difftar.gz
> Calculated hash: f225519ed7c773b418cd1697e3010e343bb79fad
> Manifest hash: d2b34a36ff6c80c5dbbc9aaf27d927439f86bcd5
> 
> 
> the file looks correct
> 
> # gzip -v -t duplicity-full.20150322T220729Z.vol16.difftar.gz
> duplicity-full.20150322T220729Z.vol16.difftar.gz:        OK
> 
> Could anyone point me in the right direction?
> 

duplicity thinks it is corrupt. that's what it saves the checksums for.

first update to latest stable 0.6.25 to make sure you have the latest
greatest most bugfixed version.

then create a new full and remember that your backup after the timestamp given in the filename is probably broken in case you have to restore something from your old backup. you can give the parameter --ignore-errors to have the restoration run through but read it's description on the manpage
 http://duplicity.nongnu.org/duplicity.1.html

finally, it's possible while unlikely that you ran into a bug there. try
to run a verify with --ignore-errors and check the output as described
on the manpage doc for the parameter.

..ede/duply.net

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.