Re: [Duplicity-talk] Re: Duplicity error "found incomplete backup sets" - possibilities for restore??

[Kenneth Loafman]

Thomas,

Please post the 'ls' of the ftp directory.  I'm curious why this is
failing at this point.

It sounds like a file may be missing from the backup set.  There should
be three distinct file types for full backups, one *.manifest.gpg, one
*.sigtar.gpg, and multiple *.vol*.diftar.gpg.  If the sigtar is missing,
a recovery can still be done, but if the manifest is missing, duplicity
will fail.  Also, the vol* files should be continuous 1-N with no gaps.

I noticed also that you received the warning about NcFTP v3.20 and that
you are on a 64-bit platform.  This is a bad combination.  I know that
particular version has a habit of crashing in certain circumstance, so
you may want to think of upgrading.

...Thanks,
...Ken

address@hidden wrote:
> can you send a 'ls' of the ftp space in question?
> How did you create the backup? I am duplicity version and ftplicity conf
> file (to see your settings in detail).
> 
> Also.
> 'Warning, found incomplete backup sets, probably left from aborted session'
> tells us that duplicity finds something. So we are on right track.
> Please also send a 'ftplicity hetzner status' output.
> 
> .. ede
> 
> On 14.08.2009 12:10, Thomas Schabetsberger wrote:
>> Hi Ede,
>>
>> I added the option "--old-filenames" but the output is still the same:
>>
>> redstar2:~# ftplicity hetzner fetch
>> vz/private/36/var/www/onlineregistry/mie2009/config.php /root/mie2009
>> 2009-06-09 --old-filenames
>> Start ftplicity v1.5.0.2, time is 08/14/09 12:07:07.
>> Using profile '/root/.ftplicity/hetzner'.
>> Using installed duplicity version 0.5.19, gpg 1.4.6 (Home: ~/.gnupg)
>> Test - Encryption with key 6804F0AD (OK)
>> Test - Decryption with key 6804F0AD (OK)
>> Test - Compare Original w/ Decryption (OK)
>> Cleanup - Delete '/tmp/ftplicity.19047.1250244428_*'(OK)
>>
>> --- Start running command FETCH 12:07:10.867 ---
>> Running duplicity - FAILED (code 30)
>> Output: Warning: Option --old-filenames is pending deprecation and
>> will be
>> removed in a future release.
>> Use of default filenames is strongly suggested.
>> NcFTP (ncftpput) version 3.2.0 may fail with duplicity.
>> see: http://www.ncftpd.com/ncftp/doc/changelog.html
>> If you have trouble, please upgrade to 3.2.1 or later
>> NcFTP version is 3.2.0
>> Using temporary directory /tmp/duplicity-0kCG4S-tempdir
>> Main action: restore
>> Args: /usr/bin/duplicity --verbosity 5 --encrypt-key 6804F0AD --sign-key
>> 6804F0AD --gpg-options= --restore-time 2009-06-09 --old-filenames
>> --file-to-
>> restore vz/private/36/var/www/onlineregistry/mie2009/config.php
>> ftp://27147:address@hidden/redstar2/ /root/mie2009
>> /usr/bin/python 2.4.4 (#2, Oct 22 2008, 20:20:22)
>> [GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)]
>> duplicity 0.5.19 (August 06, 2009)
>> Linux redstar2.med-home.com 2.6.18-ovz-028stab053.5-smp #1 SMP Sat Mar 1
>> 20:36:11 UTC 2008 x86_64
>> Temp has 217697447936 available, backup will use approx 34078720.
>> Reading results of 'ncftpls -f
>> /tmp/duplicity-0kCG4S-tempdir/mkstemp-sz_lj5-1
>> -F -t 30 -o useCLNT=0,useHELP_SITE=0  -l 'ftp://88.198.42.132/redstar2/''
>> Warning, found incomplete backup sets, probably left from aborted session
>> Last full backup date: none
>> Traceback (most recent call last):
>>    File "/usr/bin/duplicity", line 825, in ?
>>      with_tempdir(main)
>>    File "/usr/bin/duplicity", line 818, in with_tempdir
>>      fn()
>>    File "/usr/bin/duplicity", line 775, in main
>>      restore(col_stats)
>>    File "/usr/bin/duplicity", line 436, in restore
>>      restore_get_patched_rop_iter(col_stats)):
>>    File "/usr/bin/duplicity", line 458, in restore_get_patched_rop_iter
>>      backup_chain = col_stats.get_backup_chain_at_time(time)
>>    File "/usr/lib/python2.4/site-packages/duplicity/collections.py",
>> line 805,
>> in get_backup_chain_at_time
>>      raise CollectionsError("No backup chains found")
>> CollectionsError: No backup chains found
>> --- Finished 12:07:24.462 - Runtime 00:00:13.594 ---
>>
>> Best regards,
>> Thomas
>>
>>
>> On Freitag, 14. August 2009 11:25:33 address@hidden wrote:
>>> There was a change of the filenames in the backups in between.
>>> Try the --old-filenames command line switch. You can add to your conf
>>> file or append it to the ftplicity command line.
>>>
>>> Your next full backup should be done without it to use the new names in
>>> the future. May be you want to create a new profile to circumvent
>>> switching.
>>>
>>> ... ede
>>>
>>> On 14.08.2009 11:20, Thomas Schabetsberger wrote:
>>>> Dear Ede,
>>>>
>>>> thanks for your instruction, I have now 0.5.19 installed with the
>>>> following result, which does not look good:
>>>>
>>>> redstar2:~# ftplicity hetzner fetch
>>>> vz/private/36/var/www/onlineregistry/mie2009/config.php /root/mie2009
>>>> 2009-06-09
>>>> Start ftplicity v1.5.0.2, time is 08/14/09 11:13:02.
>>>> Using profile '/root/.ftplicity/hetzner'.
>>>> Using installed duplicity version 0.5.19, gpg 1.4.6 (Home: ~/.gnupg)
>>>> Test - Encryption with key 6804F0AD (OK)
>>>> Test - Decryption with key 6804F0AD (OK)
>>>> Test - Compare Original w/ Decryption (OK)
>>>> Cleanup - Delete '/tmp/ftplicity.12301.1250241182_*'(OK)
>>>>
>>>> --- Start running command FETCH 11:13:02.818 ---
>>>> Running duplicity - FAILED (code 30)
>>>> Output: NcFTP (ncftpput) version 3.2.0 may fail with duplicity.
>>>> see: http://www.ncftpd.com/ncftp/doc/changelog.html
>>>> If you have trouble, please upgrade to 3.2.1 or later
>>>> NcFTP version is 3.2.0
>>>> Using temporary directory /tmp/duplicity-lj8o_V-tempdir
>>>> Main action: restore
>>>> Args: /usr/bin/duplicity --verbosity 5 --encrypt-key 6804F0AD
>>>> --sign-key
>>>> 6804F0AD --gpg-options= --restore-time 2009-06-09 --file-to-restore
>>>> vz/private/36/var/www/onlineregistry/mie2009/config.php
>>>> ftp://27147:address@hidden/redstar2/ /root/mie2009
>>>> /usr/bin/python 2.4.4 (#2, Oct 22 2008, 20:20:22)
>>>> [GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)]
>>>> duplicity 0.5.19 (August 06, 2009)
>>>> Linux redstar2.med-home.com 2.6.18-ovz-028stab053.5-smp #1 SMP Sat
>>>> Mar 1
>>>> 20:36:11 UTC 2008 x86_64
>>>> Temp has 217743781888 available, backup will use approx 34078720.
>>>> Reading results of 'ncftpls -f
>>>> /tmp/duplicity-lj8o_V-tempdir/mkstemp-R1rz41-1 -F -t 30 -o
>>>> useCLNT=0,useHELP_SITE=0  -l 'ftp://88.198.42.132/redstar2/'' Warning,
>>>> found incomplete backup sets, probably left from aborted session Last
>>>> full backup date: none
>>>> Traceback (most recent call last):
>>>>     File "/usr/bin/duplicity", line 825, in ?
>>>>       with_tempdir(main)
>>>>     File "/usr/bin/duplicity", line 818, in with_tempdir
>>>>       fn()
>>>>     File "/usr/bin/duplicity", line 775, in main
>>>>       restore(col_stats)
>>>>     File "/usr/bin/duplicity", line 436, in restore
>>>>       restore_get_patched_rop_iter(col_stats)):
>>>>     File "/usr/bin/duplicity", line 458, in
>>>> restore_get_patched_rop_iter
>>>>       backup_chain = col_stats.get_backup_chain_at_time(time)
>>>>     File
>>>> "/usr/lib/python2.4/site-packages/duplicity/collections.py", line
>>>> 805, in get_backup_chain_at_time
>>>>       raise CollectionsError("No backup chains found")
>>>> CollectionsError: No backup chains found
>>>> --- Finished 11:13:14.494 - Runtime 00:00:11.676 ---
>>>> redstar2:~#
>>>>
>>>> There are thousands of files, which were not altered manually. The
>>>> errormessage tells, that the bakcups are incomlete somehow. If this is
>>>> the case (maybe due a timeout, or so), is it possible to take one
>>>> set of
>>>> files (from a particular date with the word "full" in it) and manually
>>>> decrypt/extract them?
>>>>
>>>> Is there another (duplicity/ftplicity assisted) way left?
>>>>
>>>> Thanks,
>>>> Thomas
>>>>
>>>> On Freitag, 14. August 2009 10:58:31 address@hidden wrote:
>>>>> As Ken said:
>>>>>
>>>>> please update to 0.5.19. The ftp backend code went through some
>>>>> changes
>>>>> ... I am pretty sure the error resolves itself.
>>>>> Remove the distro duplicity first...
>>>>> Then download and extract duplicity*.tgz
>>>>> Go in the folder and 'python setup.py install'.
>>>>>
>>>>> ... tell us how it went .. ede
>>>>>
>>>>> On 13.08.2009 19:26, Thomas Schabetsberger wrote:
>>>>>> Dear Ken,
>>>>>>
>>>>>>> I'm guessing from the traceback that you have a fairly old
>>>>>>> version of
>>>>>>> duplicity.  The backup is most likely good, you just need to do an
>>>>>>> upgrade to the newest stable version, 0.5.19, which you can download
>>>>>>> at https://launchpad.net/duplicity/stable/0.5.19.  Recovery may
>>>>>>> not be
>>>>>>> possible if you have modified the remote backup in any way.
>>>>
>>>> _______________________________________________
>>>> 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
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>

signature.asc
Description: OpenPGP digital signature