Long running job - scheduled backups build up?

[JonMikelV]

@drwtsn32

I notice that when I add a large folder to back up that takes say 24 hours, after it completes several more backups will run in immediate succession, one after another.

As I understand it you should got no more than one “immediate succession” of a particular job. Of course if you have 4 different jobs all of which missed their scheduled start time you’d likely see 4 “immediate succession” runs…

Here’s a description of how the schedule works with the most salient line being "Duplicati will first check if it is already in the queue, and if so, just not put it in there". Please let us know if you’re not seeing this in action.

Scheduling strategy for backups

The scheduler is fairly simple, but schedulers are always confusing When you create the backup, and set a time to run, Duplicati records the “next time” it should run. Once that time comes, it will send the backup into the queue of tasks to run, and update the “next time” it will run. If the scheduler is restarted (e.g. by a reboot) it will look at all the “next time” values and send items into the queue. When sending an item into the queue, Duplicati will first check if it is…