Re: [Duplicity-talk] duplicity 0.6.12 / AssertionError during incremental backup

[Kenneth Loafman]

2011/6/30 Michael Schneider <address@hidden>

Hi,

"suddenly", duplicity stopped making backups to my imap-server.
After listing the backup sets present, it throws this AssertionError:

[...]
File duplicity-inc.20110614T181901Z.to.20110619T192531Z.vol47.difftar.gpg is part of known set
File duplicity-inc.20110614T181901Z.to.20110619T192531Z.vol48.difftar.gpg is part of known set
Removing still remembered temporary file /tmp/duplicity-5EE3VM-tempdir/mkstemp-TG9ab8-1
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1249, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1242, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1147, in main
    globals.archive_dir).set_values()
  File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 681, in set_values
    self.get_backup_chains(partials + backend_filename_list)
  File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 804, in get_backup_chains
    map(add_to_sets, filename_list)
  File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 794, in add_to_sets
    if set.add_filename(filename):
  File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 93, in add_filename
    (self.volume_name_dict, filename)
AssertionError: ({1: 'duplicity-inc.20110614T181901Z.to.20110619T192531Z.vol1.difftar.gpg', 2: 'duplicity-inc.20110614T181901Z......

No, this is not a known issue.  What's wrong is that somehow volume 48 appears to have been duplicated in the IMAP server.  I'm not sure how to resolve this, but somehow 'duplicity-inc.20110614T181901Z.to.20110619T192531Z.vol48' appears twice.  If you can get a list of the emails with size and date, we might be able to make an educated guess as to which one to remove.

Have you done a retry, or restarted a backup?

...Ken