Backup job for one hour keeps running every minute

[Asim]

I have one backup job configured to run per hour but it keeps running every minute (see screenshot / link)
There is no other backup job on the server
The server is a fresh install running Proxmox VE 7.2-7

What could be the issue and how to resolve this?

https://capture.dropbox.com/XaxTY8ONREaF81Pv

 

[Neobin]

Afaiu the schedule for hourly should be: *:00.

 

[Asim]

Afaiu the schedule for hourly should be: *:00.

It still runs every minute
https://capture.dropbox.com/p5MzOO4yyblieFjo

Although the job mentions next run at 22:00 hours but it keeps running every min
https://capture.dropbox.com/5VpKvxEQLtXwXeLg

 

[leesteken]

The jobs shows that next run is on the hour. Are you sure there is not another jobs running every minute? Maybe scheduled via crontab instead of the web GUI? I guess you can test this by disabling the hourly job. Does that stop the every minute backups? Maybe you thought about this and checked it already, I'm just making sure because I can't think of anything else that could cause this.

 

[Asim]

The jobs shows that next run is on the hour. Are you sure there is not another jobs running every minute? Maybe scheduled via crontab instead of the web GUI? I guess you can test this by disabling the hourly job. Does that stop the every minute backups? Maybe you thought about this and checked it already, I'm just making sure because I can't think of anything else that could cause this.

I just gave the entire proxmox a reboot (without changing the ONLY backupJOb as shown in the screenshot above) and it seems to have stopped the per-minute backup

I am observing this for the next few hours

 

[Asim]

The reboot actually fixed the issue, weird but that's what it is

 

[jdw]

Hello from the future!

I had/have a very similar issue. A proxmox backup job runs constantly. It finishes, and a minute later, it starts again. This happened on only one host out of seven in the cluster. Our one backup job's schedule is 2,14:30.

I eventually determined that the affected host previously had the wrong time zone (local time, whereas everyone else in the cluster was UTC). This problem started at the next backup after we fixed that. Disabling, waiting, and re-enabling the backup job did not fix it. As in the case described here, a reboot does seem to have done the job.

Hope this helps someone!