Unable to complete restore over NFS - Duplicati.Commandline.Recovery.exe

[ts678]

@Bungeetaco

One issue with this that I did not factor in, is that I unfortunately wasn’t able to install Duplicati on the host directly, or via a jail.

@Yonxx_Finkle

I have all my data on freenas and duplicati runs as a docker.

Shows another option that at least used to work. I mention it, but we’re already swimming in options.

@Bungeetaco

it seems the modules have been updated and do not get recognized by the script anymore

Python is going through a rough transition from Python 2 to Python 3, but I don’t know if that’s what’s behind your troubles. This would probably be worth a GitHub issue in hope of getting that script back.

Why is the Migration to Python 3 Taking So Long?

@Bungeetaco

Unfortunately no, this is a VM, thus it doesn’t have any visibility over the host.

The “thus” might depend on what exact VM it is. VirtualBox can happily do VirtualBox/SharedFolders.

@Bungeetaco

it seems they never were created during backup

That’s bizarre. They should have been, and they’re even audited as part of after-backup verifications.

@Bungeetaco

the path is using the same type of slashes as the rest of the filesystem

It’s not the path you type there. It’s the paths that Duplicati originally backed up, which are in your dlist file and presumably are forward slashes because the use of NFS which gives hint against Windows…

What was view of NFS paths from Duplicati VM? If forward, then you’re attempting a cross-OS restore using RecoveryTool. I couldn’t find previous notes on this blending, but it wasn’t working when I tried it.

EDIT:

How the restore process works shows the "path": "C:\\data\\mydoc.txt" as a Windows example. Your dlist file might have forward slashes. You can certainly open up the zip file and peek at filelist.json, however unless the Duplicati VM ran Windows, you probably have forward slashes in your path listings.