Comment 54 for bug 487720

Revision history for this message
Michael Terry (mterry) wrote :

I thought I'd write a little HOWTO on recovering from this bug, in case people hit it from using versions that aren't fixed. It won't be able to restore all original files, but you can restore most.

The central issue is that one or several of the backup volumes will be corrupted and likely not the correct size. So the first step is to identify which ones. The second step will be to restore everything *but* the files that are supposed to be in that volume.

Step 1: Identify corrupted volumes

A) Find your manifest file. If you did not encrypt your backup, it will end in ".manifest". If you did, it will end in ".manifest.gpg" and you will first have to run "gpg --decrypt MANIFESTFILE" to decrypt it.

B) Search for the provided "Manifest hash" in the error message. It will be a string like "11cd330357618de52e4e5361a6e63b09ee951ae2". This will show you which volume is corrupted.

C) In this same volume block, you can see "StartingPath" and "EndPath". This is the range of files that are supposed to be in that volume. You won't be able to get these back. :-/

Step 2: Restoring all other files

D) Using Deja Dup, you can restore many files at once by using either the "lost files" method [1] or the "revert files" method [2]. Make sure you avoid trying to restore any file that you found to be inside a corrupted volume.

[1] http://live.gnome.org/DejaDup/Help/Restore/LostFile
[2] http://live.gnome.org/DejaDup/Help/Restore/Revert