Re: [Duplicity-talk] Skipping missing/corrupted volumes?

[Red Street]

I'm using 0.6.24. I will try out 0.7.x, thanks for the note.

Thanks for the restore by hand guide. This worked to get most of one
set of my data back since there were no incrementals in that set.
Being able to do this was one of the reasons I went with duplicity.

For another set that is missing a couple of incrementals I'm guessing
there is no way out.

Thanks again!

On Wed, Oct 7, 2015 at 2:19 AM,  <address@hidden> wrote:
> what is your duplicity version? hanging on corrupt volumes should be fixed in 
> 0.7.x somewhen. try the latest.
>
> here a the "Restore by hand" guide (on the bottom). it's quite laborious.
>  https://wiki.gnome.org/Apps/DejaDup/Help/Restore/WorstCase
>
> ..ede/duply.net
>
> On 07.10.2015 00:32, Red Street wrote:
>> Also, since I'm getting somewhat desperate to have my data, or what
>> remains of it, restored, is there a way to tell duplicity to only
>> restore what are in a set of given volumes? If not, and if I can't do
>> this through duplicity, can I do it by decrypting and then untarring
>> the volumes I have?
>>
>> On Tue, Oct 6, 2015 at 3:19 PM, Red Street <address@hidden> wrote:
>>> On Tue, Oct 6, 2015 at 2:07 AM,  <address@hidden> wrote:
>>>> On 06.10.2015 01:43, Red Street wrote:
>>>>> I have a full backup set with hundreds of volumes. A small subset of
>>>>> them are either missing or corrupted. Is there an easy way to tell
>>>>> duplicity to simply skip these volumes (and files associated with
>>>>> them), and restore the remaining?
>>>>>
>>>>
>>>> try --ignore-errors . read it's description in the manpage first
>>>>  http://duplicity.nongnu.org/duplicity.1.html
>>>>
>>>> it might be possible that duplicity does not recreate the chain completely 
>>>> or at all because of the missing volumes. check the initial output with 
>>>> max. verbosity '-v9'. if so, you can try to create empty dummy files with 
>>>> the appropriate names to virtually "fill" the gaps in your chain.
>>>
>>>
>>> I had to create an empty dummy file (vol169). I used "duplicity -v9
>>> --ignore-error <url> <path>" Unfortunately, I couldn't get it to work.
>>> duplicity hangs and does nothing after this output:
>>>
>>>
>>> Processed volume 168 of 291
>>> Registering (mktemp) temporary file
>>> /tmp/duplicity-CEShxW-tempdir/mktemp-ujn2PY-71
>>> Invalid data - SHA1 hash mismatch for file:
>>>  duplicity-full.20XXXXXZ.vol169.difftar.gpg
>>>  Calculated hash: da39a3ee5e6b4b0d3255bfef95601838967593ab
>>>  Manifest hash: 939f35c5b9426613f38d8472e1abbf234896abdf
>>>
>>> Releasing lockfile <lockfile.LinkFileLock instance at 0xb6d7166c>
>>> Removing still remembered temporary file
>>> /tmp/duplicity-CEShxW-tempdir/mktemp-ujn2PY-71
>>> Removing still remembered temporary file
>>> /tmp/duplicity-CEShxW-tempdir/mkstemp-G35kU4-1
>>> Removing still remembered temporary file
>>> /tmp/duplicity-CEShxW-tempdir/mktemp-WkWnjy-3
>>>
>>>
>>> On a related note: is there a way to get duplicity to start with
>>> volume 168 in this case? Each time I try this, I get a failure, but I
>>> have to remove my destination directory and wait for duplicity to
>>> restore everything from the first volume until volume 168.
>>>
>>> Thanks!
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk