PatchingFileLocalFailed while Restoring to NEW LOCATION


I run tests with Duplicati to see how it works.

One test was a backup of my active WINDOWS partitition “C” (using VSS and the whole bunch of exclude filter groups), and restore to a new destination (another local drive “I”). I got 0 errors and several WARNINGS for various applications running in the background, like this:

“2023-04-28 01:39:19 +02 - [Warning-Duplicati.Library.Main.Operation.RestoreHandler-PatchingFileLocalFailed]: Failed to patch file: "I:\RC\Users\CW\AppData\Roaming\Adobe\CoreSync\GUDE\gude-2023-04-24.log"
with data from local file "C:\Users\CW\AppData\Roaming\Adobe\CoreSync\GUDE\gude-2023-04-24.log",
message: The process cannot access the file "\\?\C:\Users\CW\AppData\Roaming\Adobe\CoreSync\GUDE\gude-2023-04-24.log" because it is being used by another process.”

Why is the RestoreHandler patching the restored file with anything taken from the original file?


Duplicati will attempt to use data from source files to minimize the amount of downloaded data. Use this option to skip this optimization and only use remote data.

For thorough restore tests, one should use that option.
It also stops troublesome non-VSS restore file reading.

1 Like