[SOLVED] Scheduled time of Backups

[ProxiumMoxium]

Hey everybody,

im trying to make a backup on 12:29 and 22:30.

But when i set the schedule to "12:29,22:30" there is only a backup for 12:29.

The exampe given in the dropdown field is "2,22:30" and is working well.
Whats the different with "12:29,22:30"?

systemd-analyze calendar "12:29,22:30"

Output:

  Original form: 12:29,22:30
Normalized form: *-*-* 12:22,29:30
    Next elapse: Wed 2022-04-27 12:22:30 CEST
       (in UTC): Wed 2022-04-27 10:22:30 UTC
       From now: 3h 49min left

Here you see the scheduler will do next on 12:22. But in real the backup is done on 12:30.

1. Why 12:30, when scheduler says 12:29?
2. Why does the analyze says 12:22 and in real it is done on 12:30?
3. What is the correct schedule to do a backup on 12:29 and 22:29 (or in realtime 12:30 and 22:30)?

Thank you verymuch vor clarification

 

[fiona]

Hi,

Hey everybody,

im trying to make a backup on 12:29 and 22:30.

But when i set the schedule to "12:29,22:30" there is only a backup for 12:29.

The exampe given in the dropdown field is "2,22:30" and is working well.
Whats the different with "12:29,22:30"?

If you use two colons, the values will be for hours: 12, mintues: 29 and 22, seconds: 30. The comma is only for separating things of the same unit (in this case minutes).

systemd-analyze calendar "12:29,22:30"

Output:

  Original form: 12:29,22:30
Normalized form: *-*-* 12:22,29:30
    Next elapse: Wed 2022-04-27 12:22:30 CEST
       (in UTC): Wed 2022-04-27 10:22:30 UTC
       From now: 3h 49min left

There also is a schedule simulator in the backup jobs UI, where you can see the next few runs like Proxmox VE calculates them (we try to be compatible with systemd, but no guarantees).

Here you see the scheduler will do next on 12:22. But in real the backup is done on 12:30.

1. Why 12:30, when scheduler says 12:29?

Because backups run at the minute boundary and you added 30 seconds

1. Why does the analyze says 12:22 and in real it is done on 12:30?

Tested with 09:8,7:00 right now and it started the job at 09:07:00 (and then a minute later again), so not sure why it doesn't work for you.

1. What is the correct schedule to do a backup on 12:29 and 22:29 (or in realtime 12:30 and 22:30)?

You can use 12,22:30 instead.

Thank you verymuch vor clarification

 

[ProxiumMoxium]

Thank you for your answers.

i need to run the backup at 12:30 and 22:30 because at 12 there are running other jobs wich cannot be run at the same moment.

So what is the solution for this? :-D

 

[fiona]

Thank you for your answers.

i need to run the backup at 12:30 and 22:30 because at 12 there are running other jobs wich cannot be run at the same moment.

So what is the solution for this? :-D

As I wrote, you can use 12,22:30 instead. 12 and 22 are the hours, then the colon means that the next value(s), 30 in this case, will be for minutes.

 

[ProxiumMoxium]

Ah ok. Thank you very much.

But - just to understand - in case of someone wants to do a backup at 12:00 and 22:30.
What would the value here?

 

[fiona]

Ah ok. Thank you very much.

But - just to understand - in case of someone wants to do a backup at 12:00 and 22:30.
What would the value here?

I don't think that's possible with a single schedule, but am happy to be corrected if I'm wrong.