Backup Job not working PVE -> PBS

cave

Well-Known Member
Feb 18, 2016
50
7
48
Vienna
Hi,

I have 2 Backup Jobs planned in my Cluster. They are basically identical, just different PBS Backend und some time Shifts.
Yesterday i checked both PBS Servers, and found the last Backup was saved at 22.03. So no backup on 5 consecutive days: 23.24.25.26.27 .... just found out by ... hmmm ... luck.

Also it happened already a few days before CET-Summer/Winter Time changes... so this one is also not related.


Yesterday i did a reboot of all Cluster Nodes, one by one. Just in Case, and waited for today 00:30 and 02:05 when the next Backup should run.
But the Backup Run for the job today did not happen.

So i Just started it now manually, to have a backup and to see if the backup-job itself works.

PBS1
1679915014189.png

PBS3
1679915249746.png
So the manual triggered run was working. both PBS Systems work fine. Backups are stored and soon get verified with the next planned verify job.

Still, i do not know why the Job is not working as expected. Both Backup Job Details look fine to me.
1679915369760.png 1679915413479.png

In the Tasklist i went back in history, to find the latest working Backup Runs and checked for failed jobs, i could not find the missing jobs. Looks like the jobs just did not start at all.

Latest run and also successful run i could find:
1679915815201.png
1679916283300.png 1679916316323.png
Matches the backups and timestamps on both PBS Systems.

Tomorrow i'll check if the backup job did run at "Next Run" or did get skipped again.

Next i'll go check date and dpkg-reconfigure tzdata on all nodes and all pbs. but i remember i set all correctly and all show same UTC and CET timestamps.
Re-Scheduling Backups to 03:00-06:00 to get away from possible date changes.


Any idea why my Backup Jobs get skipped?
Which logs to check?
Cron issue?
Which obvious piece do i miss to look at?

Related to the Upgrade to 7.4? The Timestamps match, as i upgraded on Thursday evening. (23.03.) and the next job did not start. at least it seems.
 
Last edited:
@fabian thx, hmm, reads similar, i'll check my libev-perl version
All Nodes in the cluster are initially installed with 7.3-x. That fact does not match the bug description.

root@pve2:~# dpkg -s libev-perl
Package: libev-perl
Status: install ok installed
and
root@pve2:~# dpkg -s libpve-common-perl
Package: libpve-common-perl
Status: install ok installed

These nodes are all Debian Bullseye/11.6 to PVE 7.3 Installations (Install Proxmox VE on Debian 11 Bullseye).
 
Hello,

Same happening here. All scheduled backup jobs stopped working since the upgrade from pve-manager/7.3-6 to 7.4-3

Just upgraded to libpve-common-perl 7.3-4 from pve-no-subscription repo and restarted pvescheduler service. Now waiting for the next scheduled backup job to run to confirm it is fixed.
 
  • Like
Reactions: Gilles and joshin

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!