Weird scheduling process

[btridon]

Hello to everyone.

I encountered a weird scheduling process with my backup job.

I have a job who's running every 3 hours (+15 minutes).
My "Time Periods" table of this job is : Everyday - 8AM to 12PM

The scenario is that my first daily process of this job run at 8:15AM. Until there, That's ok.
Then, it must be +3 hours, so, in a normal case, 11:15AM but no...
My job restart at 9:15AM and then restart to 12:15PM, 15:15PM, etc.

Why my second job process start 1 hour after the first whereas my job must run after 3 hours...

Regards,

[PTide]

Hi,

Does the first run finish succesfully?

[btridon]

Yes,

it run weird evertime, success or not.

[alanbolte]

I'm not quite sure if this is the issue, but I recall that starting in v8 we shifted some of the 'every x hours' logic to always think from midnight rather than from the first time the job ever started. While in your particular case it would make sense for the logic to start the 'every x' from the first time the job started on the particular day, I don't think our logic ever worked like that, and I can think of a few other customers I've worked with who had different needs.

As a workaround, you might set every 1 hour, and then specify each subsequent start time.

[foggy]

Right, the reference point for every allowed interval is tied to midnight.

[btridon]

@foggy

Thank you, i've missed that i think.
So it takes sense.

Enable : 8AM to 12PM
So if 12PM is the reference, 12+3+3+3 = 9:15AM
This explain why my job is running again at 9:15AM

So, my job start automatically at 8:15AM once.
After that, my job is running at 9:15AM

The only way to have just 1 backup process in this interval is to put the start time of the time period on 9AM ?

[foggy]

Or disable the 9-11 time interval using the backup window setting.