PVE Backup Schedule does not meet Next Run Time

oldgoodname

New Member
Jan 24, 2024
16
0
1
Hey Guys,

I have a PVE Cluster consisting of two PVE nodes and a quorum VM for voting only. I also have a PBS for creating backups. I create backups of the VMs daily. The backup schedule is configured in the datacenter overview under the Backup configuration of the PVE cluster. The storage of the PBS is mounted on the PVE cluster as well. So far, this should be best practice.

I configured two backup jobs, one for cluster-member-1 and one for cluster-member-2. They are scheduled for 1am and 4am, but the run times show 11pm and 2am. So two hours earlier as expected. I think this is to the use of my local timezone for the schedule, but the next runtime interprets it as UTC. I double checked the two PVE node as well as the PBS node and all seem to be correctly configured to my local time zone.

I totally understand why the backups are named with the UTC timezone for several reasons, but I think the runtime itself should interpret the time as local time and not UTC, right? The backup runtime also changes when my local time switches from standard time to daylight saving time and vice versa, which is not ideal as well.

Here is a screenshot of timedatectl, which shows exactyl the same output on both PVE nodes and the PBS node (I just removed the city).

Code:
               Local time: Wed 2025-05-28 10:24:56 CEST
           Universal time: Wed 2025-05-28 08:24:56 UTC
                 RTC time: Wed 2025-05-28 08:24:56
                Time zone: Europe (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

Any suggestions, why the backup does not run at the local time, but on the UTC time?
 
Last edited: