#1 Global Leader in Data Protection & Ransomware Recovery

Job's Next Run Date Doesn't Match Schedule

KB ID: 1994
Product: Veeam Backup & Replication | 6.5 | 7.0 | 8.0 | 9.0 | 9.5 | 10 | 11 | 12 | 12.1
Published: 2015-01-29
Last Modified: 2023-07-31
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

The 'Next Run' date shown for a job does not match the settings selected in the Schedule tab of the job.

For example, a job configured to run Monthly on the last Saturday displays a 'Next Run' date of the upcoming Saturday, which is not the last Saturday of the month.

Example

Cause

This occurs when periodic Synthetic or Active fulls have been enabled, and their schedule does not match the Schedule tab.

When either periodic Full option is enabled, they operate on a sub-scheduler to meet the requested operational outcome. As long as a Schedule has been enabled, they will automatically run on the selected schedule to ensure the requested full is created on the date configured.

For the example shown in the Challenge section, the following settings are selected within the Storage > Advanced Settings:
The option for Synthetic fulls was enabled and set to occur weekly on Saturdays.

Synthetic full schedule

Solution

To resolve this issue, ensure that the periodic Full schedule matches the schedule specified on the Schedule tab of the job.

Solution

As an alternative solution, the option for periodic fulls may be disabled, forcing the job to operate in "Forever Forward Incremental" mode.

However, for jobs with large gaps between runs, the change to Forever Forward Incremental should only be made after understanding how this will impact the restore points and their interdependencies. For example, a Job configured to run monthly and create a full restore point for each month will use more space, but each month's full restore point is independent of the other months. Conversely, that same monthly job using Forever Forward Incremental would create an incremental each month., capturing only the changes since the last run. This means that each month's increment would be dependent upon each previous month's incremental restore point.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.