For too long, Duplicati has been stuck in a perpetual beta phase, but now the cycle is broken!
After forming Duplicati Inc, we have been able to hire staff to help deal with the issues that were preventing the removal of the “beta” label. Combined with incredible contributions from the community we have been able to identify and solve many issues.
Besides the many fixes we managed to implement, there are also many new features:
Performance tuning of the backup process
Support for encrypting database fields
Support for remote control via the Duplicati Console
Secret providers for protecting passphrases and credentials
Going forward, this means we can follow the intended release staging where we have:
Canary: Weekly or bi-weekly builds providing quick access to new fixes and features
Experimental: Initial preparation of release builds
Beta: Builds that are expected to be stable enough for production usage
Stable: Final builds that are ready for production usage
But of course we are far from done! We are already far along with the 2.2 release that includes a new and more modern UI and a much faster restore process.
If you want to help out making Duplicati even better, try out the canary builds as they roll out.
Congratulations on the new milestone, but I just tried to create an account at duplicati.com using my email address. Are you seriously restricting access to your product to people who have cell phones?
Then click the link “Can’t scan? Try this” and it should show you the key you need to add to your OTP app. You can copy-paste that code from the webpage into your OTP app.
If the problem is that you do not have a phone to install an OTP app on, there are plenty desktop OTP applications.
Some of the better ones can take a screenshot and find the QR for you.
If you do have a phone, I strongly recommend using OTP on that, as the OS security model is much stronger for things like protecting the OTP seed.
Thanks for pointing out that the cancel flow is confusing. We have an internal issue for fixing it.
This is such amazing news! Congratulations on the progress and the official company. I’ve been relying on Duplicati for years now and it’s been such a relief to know my essentials are backed up efficiently and regularly.
Hi there, congrats on the 2.x release - the new UI looks fantastic!
I have used the Beta for around 6 years now and have been extremely
happy with it so the logical step was to download and install the new Windows version, I have a few questions please:
I see that email notifications are behind a “Pro” upgrade / paywall, is this the only way to check if back-ups have been successful (other than logging in each time to check?)
How long will you continue to support the “old” beta versions for? As a fairly long-time user I have this set-up exactly the way I need, so wondering how long I have before I need to migrate to 2.x?
Ohh, I think I mis-understood - I thought this announcement was saying that Duplicati 2.x was a full replacement for the current client, but also with a portal access to oversee machines/backups.
I realise now that the current client should be unaffected and it is an overarching portal that has been introduced to manage the machines/backups - and that this portal (should) simply link to the current client (2.1.0.3_beta). Is that correct?
The problems I am having now are:
1 - I have gone through the instructions on the portal to “link” my account to the client, but it is not showing my Total Machines or Total Backups.
I can see them if I go to Settings>Registered Machines, but I can’t see my machine/backups in the dashboard.
2 - The backups are running and completing successfully but they are now showing they “encountered 2 warnings”, but there is no detail on what caused the warnings.
Any ideas how to solve either of these two issues?
I’m not 100% sure but the issue seemed to be I was running the 2.1.0.3_beta - I uninstalled that and installed the stable version (now 2.1.0.5) and after my next backup completed it was showing in the portal then.
This is a bit confusing, but for now the “Machines” view (and “total machines” and “total backups”) only show data from backup reports. When you register the machine it only shows in “Registered machines”. You need to configure Duplicati to send backup reports for them to show in "Machines.
We are working on a new “Machines” page that will integrate things so it is less confusing and also introduce a single-click option to set up logging backup reports.
In the console, you can click the backup that was failed, and look at the Log tab to see what the warnings are.
Can you log in to the console and click the “Support ?” link? That will create a ticket with your account information in our support tool, and from there I can look at what could be the cause.
Otherwise, does the local Duplicati show as “Remote control is connected” ? If so, it looks like you may have multiple accounts, and it is connected to another account.
I’m trying to understand if there are any new restrictions on the free version that there weren’t before?
For example, the pricing page says (for the free version): ‘View the last 200 backups’ (I’m kinda assuming this talks about ‘backup versions’ for the specific backup?)
I checked one of the backups I have on 2.0.7.1_beta_2023-05-25 and I seem to have 220 versions at the moment. I’m not saying I absolutely need all of them, but is the ‘200 backups’ limit is going to interfere with this?
As for the installed software, I have a test job that’s at 256 versions – no problem.
I don’t think you ever told it about a specific backup. Mine’s certainly a mix of jobs.
EDIT 1:
This is the screen I showed with the limit, and it looks like collected history, so may be somewhat like Job → Show logs in the installed software – except a wider view, probably more essential to an organization with lots of backups to keep monitoring.
