Deja Dup restore not working

Asked by Johann W. von Krause

Hi!
I am working on a Linux Mint 19.1 Cinnamon machine. Before upgrading to 19.1 I made a full, non-encrypted Deja Dup backup of my complete Home folder on a separate disk.
Now, when I try to restore the data, to adifferent location, I get an error after a long time of "Preparing":
Wiederherstellung fehlgeschlagen
Mit unbekanntem Fehler fehlgeschlagen
Details:
Traceback (innermost last):
  File "/usr/bin/duplicity", line 1555, in <module> with_tempdir(main)
  File "/usr/bin/duplicity", line 1541, in with_tempdir fn()
  File "/usr/bin/duplicity", line 1393, in main do_backup(action)
  File "/usr/bin/duplicity", line 1476, in do_backup list_current(col_stats)
  File "/usr/bin/duplicity", line 704, in list_current for path in path_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 354, in combine_path_iters refresh_triple_list(triple_list)
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 341, in refresh_triple_list new_triple =get_triple(old_triple[1])
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 327, in get_triple path = path_iter_list[iter_index].next()
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 239, in sigtar2path_iter for tarinfo in tf:
  File "/usr/lib/python2.7/tarfile.py", line 2510, in next tarinfo = self.tarfile.next()
  File "/usr/lib/python2.7/tarfile.py", line 2352, in next raise ReadError("unexpected end of data")
 ReadError: unexpected end of data

I have tried the "worst case instructions" for manual untar, but that gives me about 10 000 files which I would need to reconstruct using the "cat" procedure. But I am over 70 years old, I will not live long enough to do that.

Does anyone know what else I can do?

Question information

Language:
English Edit question
Status:
Expired
For:
Déjà Dup Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.