Don’t some parts of it work now, for example the ability to hold off job starts (or something like that…)? Settings has “Pause after startup or hibernation”, and I think the UI button will let you resume if desired.
Tray Icon also has Pause and Resume capability, so if removal is the plan for now, that needs change.
If you really want to test, you could probably try 2.0.3.3 Beta to see what pausing it can do. The 2.0.3.6 concurrency rewrite is where most of the pause-the-running-operation capabilities were lost, I believe.
It might be interesting to know if any operation besides backup was ever pause-capable. An operation taking more than a little while arguably might want pause ability, e.g. if a laptop needs to go off-network.
By that measure, one may like to pause Repair, Recreate, Restore, and a variety of maybe-slow things.
Question is what state things get left in if somebody or something (Windows…) reboots during pause? Possibly it can be made a little safer (due to better control) than rebooting while active, but I don’t know.
Don’t some parts of it work now, for example the ability to hold off job starts (or something like that…)?
Yes, sorry I wasn’t clear. I meant only removing the ability to pause a currently running operation. Pausing the “scheduler” should still be available.
We’d have to revisit the pause code and it’s assumptions. The state of the filesystem/machine might be different when the operation is resumed. Suspending while paused is interesting, and hibernating/reboot could be a larger problem.
My main motivation is to try and limit the number of ways in which a user can end up in a situation where the database needs to be repaired.
root@gilsvr:/software/Duplicati/duplicati-master
$ cat /etc/redhat-release
CentOS Linux release 7.8.2003 (Core)
root@gilsvr:/software/Duplicati/duplicati-master
$ uname -a
Linux gilsvr 3.10.0-1127.13.1.el7.x86_64 #1 SMP Tue Jun 23 15:46:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
For E.g. when you’re uploading TBs of backups (or smaller, but need to leave the house now), which will take several days and you need to shut down or sleep the computer.
Sleep seems hugely safe. It might error a transfer in progress, but it retries number-of-retries times.
There was a time when I deliberately slept my computer in the middle of backups to test things out.
How does Duplicati Resume After Interruption? is what should happen on more severe interruption.
Not only should it give you a synthetic backup “version” of what is done, but it will (AFAIK) continue interrupted backup from the point of interruption (not from start). Have you seen an actual problem?
There are a few open issues where things get confused, Duplicati says to Repair, and Repair works.