Page 1 of 1

Deja Dup backup from Ubuntu, restore fail in Mint

Posted: Mon Jan 21, 2013 5:10 am
by junaidkabir
Hello Everyone,

I am not suer if it really works or not. I took a backup of my system running in ubuntu 12.04 (using deja dup backup tool). Now i am trying to restore in in Linux Mint 14 (using deja dup). But the backup is failing after start (showing following errors). Am I trying to do something which is technically unsupported? If not can anyone please show me the right direction?

Traceback (most recent call last):
File "/usr/bin/duplicity", line 1412, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1405, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1339, in main
restore(col_stats)
File "/usr/bin/duplicity", line 630, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 522, in Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 494, in integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 379, in yield_tuples
setrorps( overflow, elems )
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 368, in setrorps
elems = iter_list.next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 112, in difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 329, in next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 323, in set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 666, in get_fileobj_iter
backup_set.volume_name_dict[vol_num],
KeyError: 1

Regards,
Junaid

Re: Deja Dup backup from Ubuntu, restore fail in Mint

Posted: Tue Jan 22, 2013 12:52 am
by snison
Just an obvious question... are you running as sudo?

Re: Deja Dup backup from Ubuntu, restore fail in Mint

Posted: Tue Jan 29, 2013 10:53 am
by junaidkabir
snison wrote:Just an obvious question... are you running as sudo?
Sorry for the late response. Tried running as sudo as well. Didn't work. Ended with the same error as before. :(