What means "as soon as possible" for missed backups?

[Eni_Ki]

After my system has been up for about an hour, I still see several jobs indicating “next scheduled run: two days ago” All of them have the option “automatically run backups” enabled, so I expected the jobs to run as soon as the system is up. (Jobs have successfully completed 2 days ago, run time ~1 min, scheduled to run daily around noon, today it’s not noon yet)

What should I exepct when “automatically run backups” is enabled to run as soon as possible ?

[Eni_Ki]

I guess I found out myself: The server had paused and after a resume the missed jobs started running.

It seems the server needs a manual trigger to resume after system comes back from hibernation - but only occasionally. Is there a way for it to automatically and reliably resume?

[kenkendk]

@Eni_Ki

What should I exepct when “automatically run backups” is enabled to run as soon as possible ?

Basically, all backup tasks are queued and then processed from the queue.

So a backup will wait for:

• Tasks before it in the queue
• Queue being processed (Duplicati running and not in a paused state)

If a task is scheduled to run, but Duplicati is not running at that time, it will be queued immediately on the next start.

[Lerrissirrel]

Is it possible your pause got “stuck” due to this issue?

Schedule broken in duplicati 2.2.0.3

Hi @atti_effe, welcome to the forum This seems to be caused by the power-savings mode not working correctly. What happens is that Duplicati will pause itself when the machine is in low-power mode. When leaving low-power mode, Duplicati is supposed to resume itself, but in some cases it does not. It is hard to track, but so far the guess is that something in .NET “forgets” to forward the event, so Duplicati never notices the transition. On the settings page, you should see a se…

[Eni_Ki]

Thanks for the reference to this issue.
I’m not running in server mode, but with tray icon, so I’m not sure if the considerations apply.

Just today some 60 mins after restarting my system (after regular shutdown last night) I find the try icon still indicating “pause” state. The confusing thing is that even after I open the UI, there is no prompt to resume, only when I try to manually trigger a job. So without knowing this, the ingenuous user assumes that after opening the UI the program is “active” (= server up and running) - and wonders why the jobs didn’t run.
BTW in my settings I have a “Pause after startup or hibernation” of 2 mins, so this should be out of the way now. I will play with the “power mode provider” setting to see if it makes a difference.

Note that today this happened after a cold reboot (“quickstart” disabled), so power modes should not matter IMO.

[ts678]

@Eni_Ki

Just today some 60 mins after restarting my system (after regular shutdown last night) I find the try icon still indicating “pause” state.

Note that manual pause (if done) before shutdown will persist after the restart.

@Eni_Ki

BTW in my settings I have a “Pause after startup or hibernation” of 2 mins, so this should be out of the way now.

Given conflicting directions, it looks like manual pause prevents timed resume.

I had to manually resume recently, but am not 100% sure I didn’t pause before.

[Eni_Ki]

@ts678

Note that manual pause (if done) before shutdown will persist after the restart.

This would make sense, but I usually have no reason to ever manually pause the server. Will take a note on pause state before and after next reboot to check.