This release is a canary release intended to be used for testing.
This release is expected to progress to a stable release if no major blockers are found.
Unlike regular canary builds, this one has a major change in the build system, so it now runs on .NET8.
The builds are self-contained so Mono or .NET installations are not required to install.
Important changes from last Beta
Updated to .NET8 with OS specific builds
Using Kestrel as the API/UI server
Mandatory password and new authentication scheme for server
Settings database version updated to v8
Backup database updated to v13
New tool to manage a running server
Due to incompatibility with duplicati_client a new tool is included, named Duplicati.CommandLine.ServerUtil.exe/duplicati-server-util.
Upgrade from v2.0.9.105
If you are upgrading from 2.0.9.105 please see the release notes from 2.0.9.106 for how to prepare the database.
Upgrades from other versions do not need special steps.
Detailed list of changes:
Added missing options to Agent commandline
Fixed a warning when using the S3 backend
Sending package type id to usage reporter
Reduced log output and increased heartbeat period for Agent
Upgraded all my Windows machines yesterday and Linux was just done, all are working - can confirm the S3 messages have all gone for those backups that have run.
However, upgrading all 6 Windows machines (Win11 Pro + Win Server 2022) from .110 to .111 once again left me with two separate entries in Programs and Features, with the .111 showing as a smaller install for some reason. Had to completely uninstall both then the same install job worked fine - no loss of config or data as far as I can tell.
Not sure what is going on with the MSI, I was also pushing out updates to Firefox, Thunderbird and LibreOffice to the machines and none of them behaved that way. Perhaps for the next push of Duplicati I add an extra pre-step to uninstall Duplicati first.
BTW, what’s Agent? I kept meaning to ask before when the MSI started appearing for download.
I think uninstall seems like a good precaution. I have tried several times to reproduce the issue and have not been able to. Do you perhaps use some kind of software rollout system to install the packages?
The agent is a version that is constrained to connect only to the Duplicati Console (https://app.duplicati.com). It can then be managed through the console with no local UI.
It is still in a testing phase, and currently mostly intended for enterprise-style installations where many machines needs to managed from a central place.
We will announce the Agent setup in more detail later. Anyone who wants to try it out can contact support via the Duplicati website or write to hello@duplicati.com.
Yes, I use ManageEngine’s “Endpoint Central 11”, I run the free version as I only use it to manage my Servers and PCs at home, though only for Windows machines.
I found some docs, but not the right ones. Do you usually have a Windows service running?
If so, can the software rollout system stop the service with sc or something to avoid issues?
Yes, they all run as a service, using the local system account, the only way I have ever run it, so you could be onto something.
The EC job has a pre-job step to stop both the service and for killing the tray-icon in case it’s also still active e.g. I’m logged in. It also starts the service again on a post-job step.
I notice that the service can take some time to close down on Linux, so perhaps it’s similar for Windows and either it’s failing or it leaves a sub-process behind that could still be taking time to stop but allows the service stop command to complete. There’s also a chance the kill tray icon is not working.
There is something strange with the trayicon in the 2.0.9.109 - 2.0.9.111 releases.
In earlier releases the Open command was marked as default, but in this version there is no default.
Without the default I have to use 2 clicks to open Duplicati (right click on the trayicon and then click on Open), but I can live with it. Left clicking on the icon gives no response, so I suspected a failed installation.
Updating without restart is also a little bit tricky in Windows.
I am very happy wih the move to Net8. It’s much faster on my 500 GByte backup (local and Onedrive).
I have 2.0.9.111 installed on my Debian testing machine, and if I look at the About page it tells me to “update” to the same version. Clicking “check for updates now” doesn’t fix it. Is this expected?
Are you using the WindowsService?
Then I may have a fix ready soon as described here.
Otherwise, what Windows version and details are causing the restart?
Yes! There is a massive speed improvement already. And we are investigating faster restore at the moment.
Not expected.
Did you perhaps get the update notice before updating? So it knows there is an “update” from the previous version, but it somehow fails to figure out that this is also the current version?
That is likely the problem. The value has persisted, but is not changed after an update check. The versions are likely compared with == instead of >, so it just notices that it is different not that it is older. I have created an issue for this: