I can confirm that I'm seeing a similar issue, but this was caused by voluntarily interrupting the backup by using the "continue later" button.
Here is the python backtrace :
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1359, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1342, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1222, in main
globals.archive_dir).set_values()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 684, in set_values
self.get_backup_chains(partials + backend_filename_list)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 807, in get_backup_chains
map(add_to_sets, filename_list)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 797, in add_to_sets
if set.add_filename(filename):
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 94, in add_filename
(self.volume_name_dict, filename)
AssertionError: ({10: u'duplicity-full.20111020T125029Z.vol10.difftar.gpg', 11: u'duplicity-full.20111020T125029Z.vol11.difftar.gpg', 12: u'duplicity-full.20111020T125029Z.vol12.difftar.gpg', 13: u'duplicity-full.20111020T125029Z.vol13.difftar.gpg'}, u'duplicity-full.20111020T125029Z.vol13.difftar.gz')
This is easily reproducible using local file system storage by following those steps :
1) Define the storage as a directory on a local disk
2) Start the backup and provide a password for encryption
3) use 'watch ls /the/backup/directory' to see the backup files appearing. They should end in .gpg
4) Interrupt the backup using "continue later" button
5) Restart the backup
6) Wait for new files to be created in the directory. They will now end in .gz
7) Interrupt the backup again like in #4
8) Restart the backup a third time, it will fail with the backtrace cited above.
It looks like, when interrupted and then restarted, deja-dup restarts _without_ encryption, which explains why the .gz file appears. When looking at the .gz file using a simple 'tar tvzf *.gz', it is indeed not encrypted and completly readable.
I can confirm that I'm seeing a similar issue, but this was caused by voluntarily interrupting the backup by using the "continue later" button.
Here is the python backtrace :
Traceback (most recent call last): duplicity" , line 1359, in <module> tempdir( main) duplicity" , line 1342, in with_tempdir duplicity" , line 1222, in main archive_ dir).set_ values( ) python2. 7/dist- packages/ duplicity/ collections. py", line 684, in set_values get_backup_ chains( partials + backend_ filename_ list) python2. 7/dist- packages/ duplicity/ collections. py", line 807, in get_backup_chains add_to_ sets, filename_list) python2. 7/dist- packages/ duplicity/ collections. py", line 797, in add_to_sets filename( filename) : python2. 7/dist- packages/ duplicity/ collections. py", line 94, in add_filename volume_ name_dict, filename) full.20111020T1 25029Z. vol10.difftar. gpg', 11: u'duplicity- full.20111020T1 25029Z. vol11.difftar. gpg', 12: u'duplicity- full.20111020T1 25029Z. vol12.difftar. gpg', 13: u'duplicity- full.20111020T1 25029Z. vol13.difftar. gpg'}, u'duplicity- full.20111020T1 25029Z. vol13.difftar. gz')
File "/usr/bin/
with_
File "/usr/bin/
fn()
File "/usr/bin/
globals.
File "/usr/lib/
self.
File "/usr/lib/
map(
File "/usr/lib/
if set.add_
File "/usr/lib/
(self.
AssertionError: ({10: u'duplicity-
This is easily reproducible using local file system storage by following those steps : directory' to see the backup files appearing. They should end in .gpg
1) Define the storage as a directory on a local disk
2) Start the backup and provide a password for encryption
3) use 'watch ls /the/backup/
4) Interrupt the backup using "continue later" button
5) Restart the backup
6) Wait for new files to be created in the directory. They will now end in .gz
7) Interrupt the backup again like in #4
8) Restart the backup a third time, it will fail with the backtrace cited above.
It looks like, when interrupted and then restarted, deja-dup restarts _without_ encryption, which explains why the .gz file appears. When looking at the .gz file using a simple 'tar tvzf *.gz', it is indeed not encrypted and completly readable.
hth