My apologies - you did explain it correctly the first time, I just didn’t read your post closely enough. But I think I understand now - the problem is with a mapped drive as the SOURCE, not as the destination.
I believe kees-z’s answer is correct - you need to either run Duplicati as the user who mapped the Z: drive or you need to add the Z: drive mapping to the user the Duplicati IS running as.
Change Service User
If Duplicati is running as a service, then the “Duplicati service Properties (Local Computer)” image in my previous post is where you can update “This account” to be the user for whom drive Z: was mapped.
Add access to LOCALSYSTEM (hack)
I believe it is possible to give the LOCALSYSTEM account a mapped drive, but it will then be usable by everybody on the computer. So if you give LOCALSYSTEM a mapped Z: drive when you log in as your normal user you will have that Z: drive.
Dynamic mapped pre/post script drive (hack)
- Create a batch file with something like this:
net use V: "\\10.3.10.17\" "myPassword" /USER:"\\10.3.10.17\nas1_informatica" /PERSISTENT:YES
- Create a batch file with something like this:
net use V: /DELETE
- In your Duplicati job add a
--run-script-before
parameter that points to the first script and a--run-script-after
parameter that points to the second script.
(Note that while the backup is running it’s possible other users on the machine will have access to the V: drive, I’m not sure.)
Dynamic mapped drive batch file & Task Manager (hack)
Other options include not running Duplicati as a service and instead using the Windows Task manager to run a batch file which would:
- map the drive (with something like
net use Z: "\\10.3.10.17\" [password] /USER:"\\10.3.10.17\nas1_informatica"
- run the Duplicati backup as a commandline call
- remove the mapped drive (with something like
net use Z: /DELETE