Does setting a shorter pause avoid this, or at least make it less consistent?
My preliminary testing with on-the-10-minute-mark test backup is like what I get with manual Pause.
Setting a 15 minute
Pause after startup or hibernation skipped two potential backups while Windows was awake, and running Duplicati in paused mode. Sleep 8:16, wake 8:17, got two 8:32s.
Setting a 5 minute pause, Windows sleep, and Windows wake in time for a single backup slot to be missed resulted in a single backup. This is a somewhat different behavior than the 60 minute pause causing a repeat of the every-87-minutes backup because I don’t see how one could miss two slots.
One interesting possibly relevant (or possibly misleading) thing to watch is what the status bar says about the next backup time. Often I see this jump to the next slot when a slot is missed (even when Duplicati Pause is in effect, but sometimes it’s delayed, e.g. I just had one delay 1:46 after the miss.
For even more fun, look at About --> System info at the bottom where it shows a not-human-friendly
- proposedSchedule : (which shows the plan for future backups in UTC time, subject to delays)
- schedulerQueueIds : (which seems to get an entry when the missed backup is finally noticed)
- pauseTimeRemain : (which seems to be in milliseconds)
This testing was on 184.108.40.206 Canary, but I suspect nobody’s been messing in the scheduler lately…