This release is a canary release intended to be used for testing.
Changes in this version
This release marks the soft-launch of the Duplicati Storage service, giving a zero-configuration setup of storage. The Duplicati Storage backend works like any other backend, but there is no configuration to set up. Once the client is connected to the console, it can use the Duplicati Storage backend.
The service is currently in soft-launch mode and anyone interrested can contact Duplicati support to have a storage trial activated on their account.
In this release there is an experimental setting option that makes the actual operations (backup, restore, verify, etc.) run in an isolated sub-process. When this setting is enabled, the Duplicati server will spawn a new process for each operation, and the operation will run in that process. This means that if the process crashes or hangs, the Duplicati server will not be affected. It also allows the Duplicati server, and by extension the user, to force-kill a stuck process. While this feature is tested, it is not enabled by default as we are aware that there might be subtle issues and would like feedback on how the feature works in real-world scenarios.
The previous “SharePoint” and “OneDrive for Business” backends have been marked as deprecated, as Microsoft shut down the API they were calling. The migration step is to use the “SharePoint v2” backend (renamed to just “SharePoint” in this version) which uses the Microsoft Graph API.
This version also adds a new backend for the Spanish proivder Movistar, thanks to @redmars27. The backend is marked as “untested” as it can only be used (and tested) by Movistar customers.
This update also adds some more guards to the synthetic filelist generation update from 2.3.0.102, and a fix for OneDrive timeouts.
Hi, this version has broken Hyper-V VM backups. It was working with previous Canary version 2.3.0.102. The Hyper-V objects has disappeared from the source file browser in both new and legacy UI.
Log snippet from 103
2026-05-23 11:13:52 +02 - [Error-Duplicati.Library.Main.Controller-FailedOperation]: The operation Backup has failed
UserInformationException: Backup aborted since the source path %HYPERV%\4adff6c6-eb07-4a26-9146-66d86ad0f64d does not exist. Please verify that the source path exists, or remove the source path from the backup configuration, or set the allow-missing-source option.
Log snipper from 102
“2026-05-09 15:09:39 +02 - [Information-Duplicati.Library.Modules.Builtin.HyperVOptions-StartingHyperVQuery]: Starting to gather Hyper-V information”,
“2026-05-09 15:09:59 +02 - [Information-Duplicati.Library.Modules.Builtin.HyperVOptions-HyperVMachineCount]: Found 9 virtual machines on Hyper-V”,
“2026-05-09 15:09:59 +02 - [Information-Duplicati.Library.Modules.Builtin.HyperVOptions-IncludeHyperV]: For VM APPS - adding D:\VHD\APPS.vhdx”,
“2026-05-09 15:09:59 +02 - [Information-Duplicati.Library.Modules.Builtin.HyperVOptions-IncludeHyperV]: For VM APPS - adding D:\VMS\APPS\Virtual Machines\4ADFF6C6-EB07-4A26-9146-66D86AD0F64D.VMCX”,
"2026-05-09 15:09:59 +02 - [Information-Duplicati.Library.Modules.Builtin.HyperVOptions-IncludeHyperV]:
Does it work if you downgrade to 2.3.0.102 ? There were not intentional changes to Hyper-V support in this build.
That indicates that %HYPERV% is not correctly translated. I think this could happen if VSS fails to load so the virtual machines cannot be queried. Do you see any errors related to VSS in the logs?
Downgrading to 102 the backup was successful. Ignore my comment about the Hyper-V objects not showing in the source file browser, I was looking for it in the destination screen. I can confirm that on 103 I can see the Hyper-V object on the source file browser.
On 102, I get this VSS event log entry.
Volume Shadow Copy Service information: Snapshot creation initiated for Snapshot Set {9768a0b6-0e38-49d6-bf25-6d69cb3ff1de}.
Process command line: “C:\Program Files\Duplicati 2\Duplicati.Server.exe” --webservice-interface=any “–windows-eventlog=Duplicati 2:Duplicati Server” --ping-pong-keepalive=true
Process Caller Stack:
Process[0]: Duplicati.Server.exe
Process[1]: Duplicati.WindowsService.exe
Process[2]: services.exe
On 103, I don’t get this eventlog entry or any other VSS log entries.
Thanks for confirming. The only thing I can see that could potentially cause problems is if you set up a new backup, and then the input might change from %HYPERV% to %HYPERV%\ which could trigger something.
Is your setup with a new or edited configuration when you switch between versions?
Could you check by exporting the configuration from .102 and .103 and look for the “Sources” part and see if this has changed?
Hi! Has anyone else noticed that the GUI port changed from “8200” to “8300” in v2.3.0.103? This is a nit, but a bit of a surprise if you bookmark the GUI page in your browser.
The first instance of the web server is listening on TCP port 8200. Additional instances listen on port 8300 and higher.
2.0.9.106_canary_2024-09-03 added a controversial feature of port memory, so once the port gets bumped up, it stays until you manually force it to come down.
Server port for TrayIcon in current docs explains the old way, plus new memory:
By default, Duplicati uses the port 8200 as the communication port with hosted server. Should that port be taken, usually because another instance of Duplicati is running in another user context, Duplicati will automatically try other ports from the sequence: 8200, 8300, 8400, ..., 8900.
Once an available port is found, this port is stored in the server database and attempted first on next run.
It doesn’t say how to correct this. Previously you just restart. Now you start with:
--webservice-port: The port the webserver listens on. Multiple values may be supplied with a comma in between.
(taken from CLI command --help)
Any idea what the conflict might have been? Likely some other Duplicati in use.