Daylight saving switch changes job start time

[JerrySeltzer]

With the recent annual end of daylight saving time in the US, I noticed an annoying issue with my Veeam O365 backups starting an hour earlier. Backup jobs that were set to run at end of day at 6PM are now running at 5PM instead, missing the last hour of work. It also interferes with monitoring software that looks for the email reports between 6PM and 9AM.
The earlier starting job now sends emails outside the window and are detected as failures.

I'm guessing the schedule converts to UTC, but I need my jobs based off local time zones. Could an option be added to choose UTC or local based start times?

[Polina]

Hi Jerry,

Your guessing is correct - the time is converted to UTC (which fits the needs of distributed deployments) and after the daylight change job schedules have to be adjusted manually.

[Bjoern_ch]

Hi there,
ran into the same issue (like everyone else i assume).
I`m a bit confused about it. Daylight saving time should not make such a mess! Changing the schedule can have an huge impact!
We have a lot of jobs because we backup more than one orga. Manually changing all jobs is quite some work. This is not convenient.
From my point of view veeam should not ask the customers to change every job schedule every six months. veeam just works, but not in winter i guess...
Please fix this. Thanks.
Bjoern

[FlorianM]

Since we started with VBO some years ago we have the issue after the clock change twice a year.
The Job start time and also the Backup Window was changed automatically during the time change/clock change.
For this I like to request to work on it for the new Versions of VBO. That should be fixed from Veeam.

[Mildur]

Hi Florian

Welcome to the forum. I moved your post to this topic.
Currently the time is stored in UTC. That's the reason why the jobs change their start time twice a year.
We count yours and Bjoerns comment as a +1 for a fix in a future version.

Thanks
Fabian

[Bjoern_ch]

This weekend time changed again.
So, thanks again, for changing all schedules as well...
Is there any news, when this will be fixed?
Thanks.

[Mildur]

Hi Bjoern

We have it on our roadmap.
But the request last November was to late to be included in V7.
It will be fixed in a future version of Veeam.

Best,
Fabian

[toma1269]

I agree, this needs to be resolved asap. Apparently has been an issue for at least 3 yrs now.

[Gerald]

Continues to be an issue in 2026. Just noticed today my O365 backups had not run since winter time started in late October 2025 - my VM for the backups starts at 23:50 and the backup is scheduled for 00:05 the next day. Now the backup time had magically changed to 23:05, 45 minutes before the the VM had even started so the backup never ran. It clearly is my fault for noticing this so late - but it's still not great if you cannot rely on a specific time you set for a job! It really makes no sense that the time a backup job runs should be different in winter/summer.

Veeam Backup for O365 v8.2.0.2202 P20251031

[AlexL]

Yeah, I second that, fairly annoying indeed.
I created a script to "fix" this in bulk for our customers but how is this still an issue after many years?
This is not some low prio feature request, this a bug, plain and simple in my opinion. Never bothered to raise an issue about it though.
What other product of Veeam has this behaviour? Only MS365 backup, either fix this or also do the utc thing with VBR, VBA etc for consistent behaviour across products