If I go to download from there, it offers to download of ‘duplicati-2.1.0.5_stable_2025-03-04-win-x64-gui.msi’
From the name it looks like it’s installation of duplicati (same as I have installed on my machine, as I mentioned, I’m running 2.0.7.1_beta_2023-05-25).
I do not know anything about the console etc. (nor do I really care).
I want to understand whether this ‘stable release’ has any limitations compared to what I already have.
Then you have no interest in the pricing plan of the Duplicati Console.
Your only interest is in the free-and-open-source Duplicati client itself.
Aside from possible bugs (new releases usually fix bugs but can add new ones),
there shouldn’t be any intentional limitations. Maybe the developer can reassure.
How about you look at the release notice? Here are the highlights of the change:
and below that there are details. The change surprise some people trip on is the new password, although if you open the browser from the TrayIcon you might see no difference because no password is needed for that case. Other uses see this more.
The first problem you may see is the recent discovery that updating from 2.0.7.1 doesn’t work right, so just go to the Downloads page yourself to get the software.
That’s the one suitable for most Window systems. Install if release note looks OK.
Downgrade from 2.1.0.2 to 2.0.8.1 is available if you need it. 2.0.8.1 is a smaller jump from 2.0.7.1 than 2.1.0.5 is (therefore less chance of any technical surprise).
In fairness to @solf I just went to the Duplicati page and I found it confusing too. I didn’t see anything that differentiates between “Duplicati Console” and “vanilla” Duplicati on either the main page or the pricing page.
The open-source client builds have no artificial limitations, and we do not plan to add any.
The pricing page only describes the pricing of the console option, and here we apply a limit of the last 200 backup reports shown. This does not prevent you from having many more though.
And the console only shows the backup reports, it does not limit or interfere with the local client.
Thanks for the feedback, I will see if we can make it clearer.
There is no mention of the open-source client, because it is free to use, but we use the same website for both the console and to host the download page.
I am testing stable release Duplicati on macOS Sequoia on M4 Apple Silicon.
Duplicati has Full File Access permissions.
However, I still get many warnings about files in the User Library that are either used by another process or have access denied. I have to setup dozens of filters to fix this.
Can Duplicati under the hood exclude these problematic files via some setting or have a setting to exclude what Time Machine normally excludes?
Yes. This is caused by .NET (and Duplicati by extension) is trying to play nice and observe the locks placed on files. You can set the advanced option --ignore-advisory-locking=true and Duplicati will ignore at least the “used by another process”.
For the “access denied” errors, there is not really an option to do much, as they will fail no matter what. There is not an option to avoid the error messages either, as that could mask some unwanted excludes.
What files are you trying to back up that you do not have access to?
Thanks, I will try the option to ignore “used by another process”
The problematic files are all in /Users/xxxx/Library or /Library. Some are cache files, others have LOCK in their name. I think they are all files that should not get backed up in the first place.
Duplicati even tried to backup its own sqlite database. I can send you log examples if helpful.