Re: [Duplicity-talk] SHA1 hash mismatch - need restore in any case, a bit urgent

[Michael Terry]

So, if deleting your ~/.cache/duplicity like Clemens suggested didn't
work, I have written some instructions for how to recover files
manually from volumes.  It's not pretty, but maybe it would help if
you're desperate.  It also should let you get around the issue of the
first volume being bad (assuming that volume didn't hold the data you
cared about).

https://live.gnome.org/DejaDup/Help/Restore/WorstCase#Restoring_by_Hand

-mt

On 8 April 2011 15:18, Igor Balic <address@hidden> wrote:
> I have inspected files again, more carefully, volume 1 (of ~500) of full 
> backup is corrupted (unexpected end of archive when gunzipping manually), 
> it's 10MB long, but it should be 50MB. :(
> Is there any way to skip files in this volume and just proceed with others? 
> It's all non-ecrypted.
>
> Igor
>
>
> -----Original Message-----
> From: address@hidden [mailto:address@hidden On Behalf Of Clemens Eisserer
> Sent: Friday, April 08, 2011 9:04 PM
> To: Discussion of the backup program duplicity
> Subject: Re: [Duplicity-talk] SHA1 hash mismatch - need restore in any case, 
> a bit urgent
>
> Hi igor,
>
> I saw the same error when I tried to restore a backup of mine.
> In my case I just deleted all cached metdata, and it suddenly worked.
>
> Although I am a bit unsure how much I can trust duplicity now :/
>
> Good luck, Clemens
>
> 2011/4/8 Igor Balic <address@hidden>:
>> Hi,
>>
>> sorry for urgency. We have a duplicity full backup and one increment.
>> Backups are not encrypted. Output is:
>>
>> duplicity restore --force  --no-encryption --file-to-restore /
>> file:///duplicity/___/home2    /root/res
>> Local and Remote metadata are synchronized, no sync needed.
>> Last full backup date: Tue Feb  8 19:39:53 2011
>> Invalid data - SHA1 hash mismatch:
>> Calculated hash: 3ca1ea655bdcc978ddb2711bed013e30bd880a03
>> Manifest hash: f46cab5c38e1ae506133c8f568e5773e0f5f7626
>>
>> I need a way to restore files, despite this error, --force doesn't help,
>> neither does using --file-to-restore, or without it.
>>
>> Backups went OK, without error, file sizes seem OK, no errors when backup
>> was made, both machines are 64 bit.
>> I just need to somehow override this error, modifying duplicity executable
>> is OK.
>>
>> I can pay for fast solution, since I really need it... No usable solution
>> found in archives.
>>
>> Igor
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>