Jobs runs without schedule (bug?)

[tfloor]

Hello,

I don't understand this issue.
I have created 4 jobs to backup vm's from vmware to a datadomain.
The jobs are scheduled from monday till friday. with on friday synthetic full. No active fulls for the rest.
Scheduled at 23:56

So i want to see the job starting at monday in the evening till friday at 23:56
What i've seen today (it's monday today), that the jobs was running on 12 februari (yesterday sunday 23:56)
I cannot see why it was running? I've not schedule it for that day....

Could someone tell me where to find more information about this?
Weird brainbreaker!

Regards,

Tristan.

[tfloor]

Using latest version of veeam (6 patch1)

[foggy]

Tristan, hard to guess what went wrong with your schedule. Debug logs will definitely tell the reason, please open a support case on this. Thanks.

[DI_MAB]

I saw this after upgrading from 5.0.2 to 6. My schedule (was set to "These days only", but was defined as weekdays only, suddenly started running on weekends. I've found changing the schedule to something different and then setting it back to what you want will overwrite this in the db settings and it'll start working. Seems like a bug to me, but was a quick fix.

[foggy]

Just checked with our QC team, this issue is confirmed and will be addressed in one of the following product updates. Currently you can schedule your jobs at any time before 23:45 to workaround.

[tfloor]

Good to hear. Is there a fix available ? I have exact the same schedule.
I have to schedule the jobs exactly at the end of the day because of time stamps for backup exec.
In practice the job must be finished after 00:01 so that there is a correct datestamp.
Incrementals run very fast.

Any workaround.?

[foggy]

The only possible workaround I can think of is to use some post job script that will touch the files and modify the time stamps.

[tfloor]

Can someone from veeam confirm that this is also a workaround?

" I've found changing the schedule to something different and then setting it back to what you want will overwrite this in the db settings and it'll start working. Seems like a bug to me, but was a quick fix."

[foggy]

This doesn't work in our lab and it actually shouldn't due to the nature of the issue (the issue is in the scheduling logic, not in storing wrong data in the database or something). Might be just a coincidence in Mark's case.

[tfloor]

Thanks.
I have to deal with the issue and let it go
I cant schedule earlier because of the duration of the job
I Will live with an extra restorepoint in the weekend for some time

I hope the fix will soon

Tristan

[tfloor]

Is this fixed in patch 3?
If not, how long do we normally have to wait for a fix (new with veeam)

[foggy]

No, this is not fixed in patch 3. Most likely will be in the next update (no timeline, unfortunately).

[tfloor]

Thanks,

I will wait for the next patch. In the meanwhile i found a way to reorganize our jobs to get a good timestamp result.

Regards,
Tristan.