[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] Difficulties with restore: 'Could not restore the f

From: edgar . soldin
Subject: Re: [Duplicity-talk] Difficulties with restore: 'Could not restore the following files. Please make sure you are able to write to them.'
Date: Sun, 14 Nov 2021 21:20:45 +0100
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0


theoretically you should be able to restore with critical errors using (from 
the duplicity man page)

Try to ignore certain errors if they happen. This option is only intended to 
allow the restoration of a backup in the face of certain problems that would 
otherwise cause the backup to fail. It is not ever recommended to use this 
option unless you have a situation where you are trying to restore from backup 
and it is failing because of an issue which you want duplicity to ignore. Even 
then, depending on the issue, this option may not have an effect.
Please note that while ignored errors will be logged, there will be no summary 
at the end of the operation to tell you what was ignored, if anything. If this 
is used for emergency restoration of data, it is recommended that you run the 
backup in such a way that you can revisit the backup log (look for lines 
containing the string IGNORED_ERROR).

If you ever have to use this option for reasons that are not understood or 
understood but not your own responsibility, please contact duplicity 
maintainers. The need to use this option under production circumstances would 
normally be considered a bug.

be aware that it might skip or incompletely restore files! you will have to 
check the restore log after to find out which, so save it!

we asked you some questions before. would you mind answering please? especially

Was a mail client or server running at the same time as the backup or>>> 

Andrew: can you make sure the backup/files_mentioned were indeed
restored incompletely or corrupted.
or that the restore is actually interrupted! the log reads as if it finishes, 
albeit librsync errors are printed!

.. ede/duply.net

reply via email to

[Prev in Thread] Current Thread [Next in Thread]