V10 Scheduled jobs not starting

[mlottcpap]

We have about 30 replica jobs scheduled. Some of these fire every hour throughout the day only using a time window. Since upgrading to v10 earlier today, none of these jobs are starting at their scheduled time. No error in the console - just no activity.

[mlottcpap]

There is an issue when checking the permitted/denied settings. Disabling the scheduling window seems to allow the jobs to run.

[Trelor]

I am having the exact same issue; what is your solution actually?

[Dima P.]

mlottcpap,

There is an issue when checking the permitted/denied settings. Disabling the scheduling window seems to allow the jobs to run.

Can you please elaborate? Are you saying that replication task was sitting in the idle state until you changed the schedule? Do you have a case ID to share? Thank you in advance!

[Trelor]

The issue that I am having different than the OP. I am having an issue with a periodic job starting that is scheduled to do a backup every 15 minutes. The job flat out does not run, there is no attempt to have the job run it just does nothing. In addition to this Veeam One just stopped working after an upgrade to 10 too.

[Gostev]

Guys, please share the support case ID, as requested when you click New Topic. Please understand that we cannot action any potential bug report without support case ID, simply because first thing developers will ask us for is... right, support case ID to get debug logs from

[Trelor]

@Gostev, #04012085

[mlottcpap]

We schedule a job to run every hour. Additionally, we set permitted/denied to allow the job to run only between 6AM and 10PM. Before version 10, this worked. Now, the job does not run at all until I allow ALL hours in the schedule.

[Trelor]

Mine was set to run every 15 minutes and allowed to run all day every day but after the upgrade it stopped working and will not schedule so it appears we are having a similar issue from different settings, but both related to every x number of minutes / hours.

[mlottcpap]

Case number 04011923.

[Trelor]

FYI as of 7:01:18 PM all my backups started working I have done nothing but wait. This is strange.

[Dima P.]

Thanks for sharing the details and for your support cases. Passed to the responsible RnD team, stay tuned!

[Gostev]

FYI as of 7:01:18 PM all my backups started working I have done nothing but wait.

Just wanted to add that I saw the same exact report on Reddit as well last night, so you're not alone.

And also that after quick re-test of the corresponding functionality, QC could not confirm any issues with periodic job scheduling internally. Could be some one-time thing due to an upgrade? So, thanks a lot to everyone who opened support cases and provided debug logs we can look at. This will help us to get to the bottom of this.

[Gostev]

We have found the root cause, and it's awesome!
v10 stores time in new format (UTC), and following the upgrade those in GMT-negative time zones end up in the past for a few hours
No action is needed, the issue will fix itself after a few hours, once you "catch up" with time.

[Trelor]

Thanks Gostev.

[mlottcpap]

I figured GMT figured in somehow Thanks for the update. All of my jobs appear to be running just fine today.

[Rumple]

Thats awesome..NOT.

By few hours you mean 8+ hours..which means my jobs which run every 15 minutes for replica's and every hour for backups are effectively screwed for 7 hours (or 6).
Thats great for DR and SLA's now isn't it....
That should have been an easy fix without WAITING...

[Gostev]

Sorry, I failed to mention that our customer support will of course be able to fix this for you with a configuration database edit, so that you don't have to wait for 8+ hours.