Backup Jobs get missed and alerts are displayed in Backup Exec 2012


Missed Job alerts of Job warning category, are displayed in Backup Exec Active Alerts. This issue is seen if job schedule is configured in a way that it does not apply to the actual time of job run.

Error Message

The scheduling options selected for this job do not allow it to start later than <time window start time>. It will be considered missed and rescheduled. Check the scheduling options to ensure that they allow enough time for the job to finish running before it is rescheduled.


Backup Exec Scheduler allows users to configure a time window within which a particular job should be run. Users can configure Backup Jobs to run on a specified time window. If a device or a system is not available during that time, the job is reported as missed and the error is displayed as above.


Due consideration should be taken when configuring devices and schedule in order to overcome the situation. Following are some points which user needs to keep in mind when configuring schedule for backup jobs:

Schedule modifications
a.       Increasing the length of scheduling window. In Backup Exec 2012, the schedule window is expressed as a relative duration with respect to start time. Please refer to the image below for the setting. The default value of this setting is 240 hours (10 days). This value should be increased depending on number of jobs, available devices, and time taken by each job to run to completion.
b.      Configuring cancel duration on the job – For jobs that are expected to run unpredictably longer durations, holding on to device(s), and hence not allowing other jobs to acquire devices, users may want to configure the auto-cancel duration as shown below. This will ensure that other jobs waiting on a device should not go missed.
c.      Backup Exec allows users to configure repeat interval for jobs. This should be configured sufficiently long to avoid jobs going missed. For instance, if there is a job set to restart every 5 minutes and it takes much longer than 5 minutes to run, then subsequent iteration of the job would report missed. Also, if the there is a duplicate job configured to follow, and it takes a long time, the parent backup job will continue to go missed. This is because the next backup job cannot be dispatched until the previous directly linked duplicate job has completed.

Staggering the jobs

  If there are fewer backup devices, then the user may want to stagger the jobs such that their schedule windows have minimal overlaps. For example, if there are 5 systems to be backed up in 12 hours and there is just one device available, scheduling needs to be done in a way that each backup job has a device available when needed. If all 5 jobs try to start at the same time, there is a possibility one or more jobs will not be able to acquire the device in within the designated time window and hence causing the job to go missed.

Increasing concurrency of the devices
 If Disk is being used as a device, Backup Exec allows users to increase the concurrency in order to allow multiple jobs to run to the same and hence increasing the probability of a job being able to acquire a device. This would reduce the risk of jobs going missed. A decision to increase the concurrency needs to be taken based on requirement and also the fact that this may impact disk performance due to high activity.

Notifications for Missed Jobs

Backup Exec allows users to configure automatic alerts notification to be sent if jobs are missed. This is available as a "Job Warning" alert category. For more details refer to related articles section.

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)