Hello everybody
I am trying to restore data from a back up and having a little (big) problem.
The recovery fails...
The command I give is:
duplicity --no-encryption file:///networkShares/backup/home home_2/
As far as I can tell this is the correct form to do restore.
The restore starts, but some time after about 20% of restore process I get this error:
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Fri Aug 12 18:18:54 2011
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1241, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line
1234, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1188, in main
restore(col_stats)
File "/usr/bin/duplicity", line 538, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 522, in Write_ROPaths
ITR( ropath.index, ropath )
File "/usr/lib/python2.6/dist-packages/duplicity/lazy.py", line 335, in __call__
last_branch.fast_process, args)
File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 37, in check_common_error
return function(*args)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 575, in fast_process
ropath.copy( self.base_path.new_index( index ) )
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 510, in
new_index
return self.__class__(self.base, index)
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 486, in __init__
self.setdata()
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 491, in setdata
self.stat = os.lstat(self.name)
OSError: [Errno 84] Invalid or incomplete multibyte or wide character: 'home_2/lazarf/CHAOS/HOME_Z/JMRUI/jMRUI-3.0/doc/help/help_files/ppt9B [R\xe9cup\xe9r\xe9].ppt'
I do not remember the duplicity version which was used to make the backup.
I am restoring it with 0.6.08b-0ubuntu2.1. Most likely likely backup was made with 0.6.08 (but the debian fllavour) but I am not sure.
What does this error mean and is there a way to recover the data.
Is it important that data is being restored onto ntfs-partition while the
original data used to sit on ext3?
Is this some sort of file-naming issue? I have no way to restore it on ext3 at the moment... (no space)
Thank you very much for your help
Lazar