I’m doing a test restore of /AppData from a local backup, however it eats up my 20gb ramdisk and then fails.
The result of the restore ends up at 32 files, 14.9gb, 27882 folders.
Here’s what’s in the temp folder at the point of failure. As there are 20 minutes between the creation date of some of those files, I’m guessing it doesn’t clean up files mid restore?
Is there a flag or something that’ll prevent copying all the files to temp? The dblock files live on a local drive so I should just be able to directly extract from them without creating copies.
Obviously in emergency I can remap %TEMP% back to a physical location, but for now it would be good to know if larger restores are possible without that.
It does actually clean up (or at least it should).
The logic here is to keep a cache of files that Duplicati needs to restore some files later.
You can control the size with --restore-cache-max=5gb for instance.
Not directly as Duplicati will need to download some files. But you can use the --restore-legacy=true option to toggle the previous restore mode, which only processes 1 file at a time. With overlapping download, that is at most two volumes in the temp folder at a time.
I tried --restore-cache-max=10gb but it still filled up the ramdisk with new files. From a quick google it looks like it could be -–restore-volume-cache-hint instead?
