Availability for the Always-On Enterprise
Post Reply
hyvokar
Service Provider
Posts: 304
Liked: 18 times
Joined: Nov 21, 2014 10:05 pm
Contact:

bug / unexpected behavior

Post by hyvokar » Feb 14, 2017 2:08 pm

Hi!

Just run in to this one.
If you have a backup sheduled to start daily at 05:00 and allowed backup window set to 05:00-06:00 and you when change your backup to start at 04:00 ; your backup will never run. Expected behaviour would start the backup at 05:00. However, in this case the "next run" value is changed to 1.1.0001 0:00:00, when it should be current/next.day 05:00:00
Bed?! Beds for sleepy people! Lets get a kebab and go to a disco!
MS MCSA, MCITP, MCTS, MCP
VMWare VCP5-DCV
Veeam VMCE

foggy
Veeam Software
Posts: 16691
Liked: 1343 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: bug / unexpected behavior

Post by foggy » Feb 14, 2017 5:38 pm 1 person likes this post

hyvokar wrote:Expected behaviour would start the backup at 05:00.
It is not an expected behavior. You've scheduled the job to start at the time it is not allowed to start, so it will not even attempt to run.
hyvokar wrote:However, in this case the "next run" value is changed to 1.1.0001 0:00:00
This is a bug indeed, it should state "Not scheduled", will be addressed in future versions.

hyvokar
Service Provider
Posts: 304
Liked: 18 times
Joined: Nov 21, 2014 10:05 pm
Contact:

Re: bug / unexpected behavior

Post by hyvokar » Feb 15, 2017 10:00 am

foggy wrote: It is not an expected behavior. You've scheduled the job to start at the time it is not allowed to start, so it will not even attempt to run.
I still dont get it why it wouldn't start at 05:00 . Also, Now when the job is never run, you wont get even an error message telling you that something is wrong.
Bed?! Beds for sleepy people! Lets get a kebab and go to a disco!
MS MCSA, MCITP, MCTS, MCP
VMWare VCP5-DCV
Veeam VMCE

foggy
Veeam Software
Posts: 16691
Liked: 1343 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: bug / unexpected behavior

Post by foggy » Feb 15, 2017 12:44 pm 1 person likes this post

It wouldn't run, since you've specified time it is not allowed to run at. Job start time should be in the allowed time, the job doesn't wait for the allowed time to come.

Gostev
Veeam Software
Posts: 22808
Liked: 2801 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: bug / unexpected behavior

Post by Gostev » Feb 15, 2017 4:11 pm

Moreover, the job will be automatically stopped, should it be started earlier and then get into the time slot where it is not allowed to run.

hyvokar
Service Provider
Posts: 304
Liked: 18 times
Joined: Nov 21, 2014 10:05 pm
Contact:

Re: bug / unexpected behavior

Post by hyvokar » Feb 16, 2017 5:59 pm

foggy wrote:This is a bug indeed, it should state "Not scheduled", will be addressed in future versions.
Make it in bold red font, so even I'll take note of that ;-)
Bed?! Beds for sleepy people! Lets get a kebab and go to a disco!
MS MCSA, MCITP, MCTS, MCP
VMWare VCP5-DCV
Veeam VMCE

Post Reply

Who is online

Users browsing this forum: No registered users and 42 guests