I upgraded my Duplicati from (I think) 2.2 or thereabouts. I was using a NAS drive attached to my Windows client the native SMB. It’s no longer working after the upgrade.
To make matters worse, I can’t seem to mount my NAS drive either via a URI (“\\nas\home\Duplicati Backups”), a mounted drive (“N:\Duplicati Backups”) or your (apparently new) SMB transport.
I am using a Synology NAS box with it’s SAMBA file server.
I can see via URI and/or mount and share on my windows system with no problem. The File System transport does not see either a “network” base path, nor does it see the N: drive I have mounted.
If I try the SMB transport all I get back is a “Failed to authenticate to server nas with status STATUS_INVALID_SMB” error. The target URL it reports is “smb://nas/home” which should be correct as far as I can tell.
I am, (or used to be) fairly familiar with SMB, but any of the variations on the SMB parameters seem to be unsuccessful. Any suggestions would be appreciated.
Well, with the help of ChatGPT, I was able to reinstall my upgrade without the “Install Duplicati as a Windows Service” feature, this brought back my old backup configuration.
As a suggestion to the developers, it might help if your install process detected the configuration of the old version and saved it as the default setting for the new install.
I still wonder why the first upgrade (with Windows Service) didn’t work. It should have at least detected the SMB server and share, even though it wouldn’t have credentials for it.
That is a Windows “quirk”. The mapped network drives lives in the user context. When you run Duplicati as a different user (a service in this case) it gets its own mapped drives, meaning it has none as there is no direct way to configure them.
If you need to run Duplicati as a service, the new SMB backend should fix that and also work when running as a service as it does not rely on Windows path mapping.
Thanks, I understand (now) what the issue was, my suggestion was that during the install, the installer detect that Duplicati is installed (it already does this) but that it is installed as a service or an user app, then set the “Install Duplicati as Window Service” button to match, thus reducing the possibility of an issue on an upgrade.
It actually does that. But the “Install as service” feature was added in 2.4, so it cannot know for older installs, and defaults to not install as a service (which was the only option pre-2.4).
