Deja Dup restore failure

Asked by jeremy herbert

I have Ubuntu 11.04. I made a backup of my stuff with Deja dup, AT THE TIME I HAD WUBI. NOW I HAVE AN ACTUAL PARTITION, and I am trying to restore it but it is not working. The output is:

Failed with an unknown error.

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1262, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1255, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1209, in main
    restore(col_stats)
  File "/usr/bin/duplicity", line 539, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in Write_ROPaths
    for ropath in rop_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 493, in integrate_patch_iters
    for patch_seq in collated:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in yield_tuples
    setrorps( overflow, elems )
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 367, in setrorps
    elems[i] = iter_list[i].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 328, in next
    self.set_tarfile()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 322, in set_tarfile
    self.current_fp = self.fileobj_iter.next()
  File "/usr/bin/duplicity", line 575, in get_fileobj_iter
    backup_set.volume_name_dict[vol_num],
KeyError: 1

Question information

Language:
English Edit question
Status:
Open
For:
Déjà Dup Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Michael Terry (mterry) said :
#1

Looks like you got bit by bug 498933. This means that due to a bug, the previous backup you made has a hole in it, in the form of a missing volume file. :(

Is the backup set shareable? We have not been able to determine what causes this bug yet, and would love more data.

Is the backup set important? It's apparently possible to (mostly) recover from this, but it requires a bit of work and luck. I can guide you through that if you're interested. If so, first thing I would need is any file that ends in *.manifest in your backup location. You can't upload files to questions, so maybe open a bug first.

Revision history for this message
jeremy herbert (jerguy1928) said :
#2

currently its just sitting on my external drive, but i will upload it and would like you to guide me through it.

Revision history for this message
jeremy herbert (jerguy1928) said :
#3
Revision history for this message
jeremy herbert (jerguy1928) said :
#4

I actually reviewed the manifest and the files, volumes one and 2 are missing in the backup and the manifest doesn't have a location for them. if i chnage the manifest to not include 1 and 2, will that fix it?

Revision history for this message
jeremy herbert (jerguy1928) said :
#5

I tried changing manifest like i suggested before, didn't work

Revision history for this message
Michael Terry (mterry) said :
#6

(So I'm looking at this, I haven't gone away. I'm faking the problem you have and seeing if there's a way to stitch the volumes together so as to not notice the missing ones.) You're sure only 1 and 2 are missing?

Revision history for this message
jeremy herbert (jerguy1928) said :
#7

Yes i am sure i just checked.

Revision history for this message
jeremy herbert (jerguy1928) said :
#8

Yes i am sure i just checked.

Revision history for this message
Michael Terry (mterry) said :
#9

I haven't had luck so far. I had thought that what you tried (removing the volumes from the manifest) would have worked. I'm still looking for a workaround. But I'm going on vacation next week, so it may be a while.

Revision history for this message
jeremy herbert (jerguy1928) said :
#10

ok

Can you help with this problem?

Provide an answer of your own, or ask jeremy herbert for more information if necessary.

To post a message you must log in.