Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I need files from an old server that ran a daily duplicity backup and was deactivated six months ago. The backup files are store in an Amazon S3 bucket and the last backup was made about six months ago. When I try to restore it using duplicity, It doesn't find any backup chain. My guess is that it cannot find any backup chains because the last signature date is very old, and it expects a relatively new one to exist. Using the -t argument doesn't solve the problem. Any ideas? Thanks for taking a time to help.

-v9 full output:

$ duplicity -v9 --no-encryption --allow-source-mismatch s3+http://<S3_NAME>/ ~/restore/
Using archive dir: /home/<USER>/.cache/duplicity/8d63fa05952285d6243341c30b9ad3b6
Using backup name: 8d63fa05952285d6243341c30b9ad3b6
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.u1backend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.ftpsbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.sshbackend Succeeded
Import of duplicity.backends.ftpbackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Import of duplicity.backends.cloudfilesbackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Main action: restore
duplicity 0.6.18 (February 29, 2012)
Args: /usr/bin/duplicity -v9 --no-encryption --allow-source-mismatch                             s3+http://<S3_NAME>/ /home/<USER>/restore/
Linux <COMPUTER_NAME> 3.2.0-35-generic #55-Ubuntu SMP Wed Dec 5 17:42:16 UTC 2012 x86_64     x86_64
/usr/bin/python 2.7.3 (default, Aug  1 2012, 05:14:39) 
[GCC 4.6.3]
Using temporary directory /tmp/duplicity-YSboMf-tempdir
Registering (mkstemp) temporary file /tmp/duplicity-YSboMf-tempdir/mkstemp-AVob8O-1
Temp has 480694202368 available, backup will use approx 34078720.
Local and Remote metadata are synchronized, no sync needed.
0 files exist on backend
0 files exist in cache
Extracting backup chains from list of files: []
Last full backup date: none
Collection Status
Connecting with backend: BotoBackend
Archive dir: /home/<USER>/.cache/duplicity/8d63fa05952285d6243341c30b9ad3b6

Found 0 secondary backup chains.
No backup chains with active signatures found
No orphaned or incomplete backup sets found.
Removing still remembered temporary file /tmp/duplicity-YSboMf-tempdir/mkstemp-AVob8O-1
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1403, in <module>
  File "/usr/bin/duplicity", line 1396, in with_tempdir
  File "/usr/bin/duplicity", line 1330, in main
  File "/usr/bin/duplicity", line 623, in restore
  File "/usr/bin/duplicity", line 645, in restore_get_patched_rop_iter
    backup_chain = col_stats.get_backup_chain_at_time(time)
  File "/usr/local/lib/python2.7/dist-packages/duplicity/", line 952, in     get_backup_chain_at_time
    raise CollectionsError("No backup chains found")
CollectionsError: No backup chains found
share|improve this question
Please post the exact error message that occurs when you attempt to restore it – Mathias R. Jessen Jan 9 '13 at 14:06
Hi, just posted the full -v9 output. Thank you – cfragni Jan 9 '13 at 14:28

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.