Re: [Duplicity-talk] 2 incomplete backup sets

[Cláudio Gil]

Hi,

Not that I am an expert but I've been using duplicity with the flag "-full-if-older-than" and thinking about what would happen. Maybe you didn't complete an incremental backup and, when restarting, duplicity decided to do a full backup instead. Could it be?

I don't think there is a way to continue a specific set as you should only have one partial backup set and that is continued automatically. Also, I don't expect restore to work with an incomplete backup set. Even if you have the manifest and sigtar in the local cache, they are incomplete and the last volume was not uploaded.

Cheers,
Cláudio

Em 11/02/2015 22:24, "Jeffrey Yunes" <address@hidden> escreveu:

Hi duplicity experts,

I have a couple questions and suggestions.

Do you know why I would ever have "2 incomplete backup sets?" That is, why did duplicity start a new backup set before completing the first one? Is there a way I can continue an incomplete backup?

Also, can I can restore a file from an incomplete backup set?

Finally, when my disk ran out of space, I eventually got an error that sounded like there was a network problem. I think it would be nice to have a more descriptive error message.

Thanks!
-Jeff

sudo duplicity -v 9 list-current-files sftp://address@hidden//media/jeff/Part1/backup.duplicity/

Warning, found incomplete backup sets, probably left from aborted session
Last full backup date: none
Collection Status
-----------------
Connecting with backend: SSHParamikoBackend
Archive dir: /Users/jeff/.cache/duplicity/8adb7199de998b91885f18324fed345a

Found 0 secondary backup chains.
No backup chains with active signatures found
Also found 0 backup sets not part of any chain,
and 2 incomplete backup sets.
These may be deleted by running duplicity with the "cleanup" command.
Releasing lockfile <LinkLockFile: '/Users/jeff/.cache/duplicity/8adb7199de998b91885f18324fed345a/jeff-laptop-2013.local-7ee79300.2718-1486341856114572708'
--
'/Users/jeff/.cache/duplicity/8adb7199de998b91885f18324fed345a/lockfile'>
Using temporary directory /tmp/duplicity-jbWkiF-tempdir
Traceback (most recent call last):
File "/usr/local/Cellar/duplicity/0.6.25/libexec/bin/duplicity", line 1509, in <module>
  with_tempdir(main)
File "/usr/local/Cellar/duplicity/0.6.25/libexec/bin/duplicity", line 1503, in with_tempdir
  fn()
File "/usr/local/Cellar/duplicity/0.6.25/libexec/bin/duplicity", line 1352, in main
  do_backup(action)
File "/usr/local/Cellar/duplicity/0.6.25/libexec/bin/duplicity", line 1441, in do_backup
  list_current(col_stats)
File "/usr/local/Cellar/duplicity/0.6.25/libexec/bin/duplicity", line 667, in list_current
  sig_chain = col_stats.get_signature_chain_at_time(time)
File "/usr/local/Cellar/duplicity/0.6.25/libexec/lib/python2.7/site-packages/duplicity/collections.py", line 977, in get_signature_chain_at_time
  raise CollectionsError("No signature chains found")
CollectionsError: No signature chains found

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk