Your batch file looks good - I think I was misunderstanding the error you were reporting.
You said it provides a warning, is the backup run even if this warning appears?
My guess is that you’re running into a command line parsing issue, but I’m not exactly sure where / why. Specifically, if you export your job as a command line you’ll likely see something like he following:
“C:\Program Files\Duplicati 2\Duplicati.CommandLine.exe” backup “ssh://MySever:12345//mnt/user/DuplicatiBackups/MyPC?auth-username=me&auth-password=mypassword&ssh-fingerprint=ssh-rsa_myRSA” …
I’m guessing the “&” characters in the destination connection string are being “eaten” somewhere causing
auth-password (and in this example
ssh-fingerprint) to look like separate parameters - which Duplicati wouldn’t recognize.
You might want to try simplifying the batch job for testing what’s going on during backup and non-backup tasks. For example:
IF *%DUPLICATI__OPERATIONNAME% EQU *Backup echo Backup>C:\output.txt
IF *%DUPLICATI__OPERATIONNAME% NEQ *Backup echo Not Backup>C:\output.txt
exit /B 0
That should let you look at C:\output.txt after test runs of various commands to make sure the appropriate IF blocks are firing.
Additionally, if the “auth-password” errors go away, then there’s a good chance the (parameter parsing?) issue is being introduced in the powershell call…