Activating a backup job that has not yet arrived causes the backup to be executed at that moment

[Alireza]

Why does a backup job that was deactivated and then reactivated execute immediately, even though its scheduled time hasn't arrived yet? For example, if a backup job is scheduled for Thursday, and we activate it on Wednesday, it runs immediately. However, we expect it to run on Thursday.
Thanks in Advance

 

[Azunai333]

This sounds like the function "Repeat missed" In the backup job: Did you tick "Advanced > Repeat missed"?
Never used it, though.

Just curious: Why would you disable and enable the backup jobs? If you forget to enable it no backup would run.

 

[Alireza]

This sounds like the function "Repeat missed" In the backup job: Did you tick "Advanced > Repeat missed"?
Never used it, though.

Just curious: Why would you disable and enable the backup jobs? If you forget to enable it no backup would run.

Thank you for the answer. I temporarily disabled the backup job because the backup server had a problem and I had to install another backup server. It seems that in my cluster version (7.2) the "Repeat" option is missing. It seems that this option is enabled by default in my cluster. On the other hand, disabling and enabling a backup job should not cause that job to run, where it runs correctly after saving at the right time.

 

[Azunai333]

It seems that in my cluster version (7.2) the "Repeat" option is missing. It seems that this option is enabled by default in my cluster.

Yes. Seems like this option was introduced in 7.3 [1]:

Added option repeat-missed, allowing one to opt-out from the default behavior of running missed jobs on a new boot

Maybe this could be a reason (btw: 7.x is EOL, you haven't got any security updates in a long time) to upgrade to the latest 8.3 version?

[1] https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.3