[Duplicity-talk] using s3 backend and cannot restore

[Jason Dusek]

  I'm on Linux on EC2, using boto-1.3 and duplicity-0.4.11. I
  have incremental backups going way backup, of a Subversion
  repository. When I try to restore, I get trouble:

 :; duplicity --no-encryption -v9 s3://<secret bucket>/<secret> ~/foo
Main action: restore
0 files exist on backend
Extracting backup chains from list of files: []
Collection Status
-----------------
Connecting with backend: BotoBackend
Archive dir: None

Found 0 backup chains without signatures.
No backup chains with active signatures found
No orphaned or incomplete backup sets found.
Last full backup date: none
Using temporary directory /tmp/duplicity-fMQQIs-tempdir
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 463, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 458, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 428, in main
    restore(col_stats)
  File "/usr/bin/duplicity", line 206, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/bin/duplicity", line 221, in restore_get_patched_rop_iter
    backup_chain = col_stats.get_backup_chain_at_time(time)
  File "/usr/lib/python2.5/site-packages/duplicity/collections.py",
line 717, in get_backup_chain_at_time
    raise CollectionsError("No backup chains found")
duplicity.collections.CollectionsError: No backup chains found

  I'm really not sure where to start with us -- your insights
  would be helpful to me. Thank you.

--
_jsn