I just encountered this issue too. The NEXT RUN time was showing a past day and time and would not kick off the job. So I went in and clicked on INCREMENTAL, unchecked the enable full synthetic option and then re-checked my reversed incremental (the one I prefer to use) and the date/time seemed to be properly reflected. We'll see if the jobs actually start tonight. By the way, I am at version 6.0.0.181 64 bit running Veeam in a VM and most jobs running in appliance mode and using a single proxy. The strange thing was that up until this weekend all of these same jobs worked fine so I am puzzled as to what changed--I certainly did not upgrade or change Veeam in any way or even the backup jobs. If this works then it's an annoying yet simple fix. I agree with a couple other posters that this sort of issue should be found during testing as it is a core function of the app. Our environment is nothing special and "plain vanilla" if you will. Hope this helps others.
Mike, this issue was fixed in patch 2 and I cannot imagine how it may "show up" unexpectedly from nowhere when the product code does not change. Would be better if you go through logs with support to find the real reason. Thanks!
NO it was not fixed because I encountered the issue and I am using the latest build for v6. The solution I posted worked in my situation. I don't know what to tell you but it can pop up apparently regardless of whatever 'fix' you say was in patch 2. This is a brand new Veeam VM that I build so it is not as though there would be leftover versions or the instance is not truly updated. Are these patches cumulative? if so, then this issue should have been resolved but still occurred in my case. if not, that would explain why the 'fix' isn't included but I can't imagine you release patches this way (i.e. are not cumulative). Things seem to be working now after I unchecked that box I mentioned and then reset for reverse incrementals.
Yes, the patches are cumulative. We would really appreciate if you give it a shot and send the logs to support. This would help us investigate and maybe define the circumstances under which the fix does not work or find another definite answer to your issue.
I had a similar problem with version 6.0.0.181, where despite setting "on these days" to "Sunday" (and no other days) in a job's schedule, the "Next run" showed up as being the following day.
This, in my case, was due to a setting under "Storage" | "Advanced" button | "Backup" tab. I had an Active full backup set to run "Weekly on selected days": <all days selected>.
So despite the actual schedule being set up to only back up one day of the week, this was being overridden by the setting to perform an active full backup on every day of the week.
Well, it's not really ovverridden; the schedule regarding the backup method you choose is still applied on Sunday, while the active backups are created daily as you requested. The "next run" shows the sum of both schedules.
Luca Dell'Oca Principal EMEA Cloud Architect @ Veeam Software
