Possible statuses for scheduled jobs are listed in the following table:
Table: Scheduled job statuses
Scheduled job status |
Description |
---|---|
Blocked by template rule |
The scheduled job cannot run because it was created by a policy that contains a job template with the following template rule: < Template A> must complete at least once before any other templates will be allowed to start The job designated as <Template A> in the policy must run before this scheduled job can run. |
Invalid Schedule |
The scheduled job will not run because of one of the following:
See Setting priority and availability windows for selection lists. |
Not in Time Window |
The job was ready to be sent for processing, but the time window for the job closed. This probably occurred because appropriate destination devices were not available during the common time between the job’s time window and the selection list’s availability window. See Setting priority and availability windows for selection lists. |
On Hold |
The job has been placed on hold. |
Queued |
A temporary state that displays when Backup Exec is applying an error-handling rule that is enabled to retry the job. |
Ready |
The job is ready to run, but cannot for one of the following reasons:
|
Scheduled |
The job is scheduled to run in the future. Scheduled jobs that are linked to another job, such as a job to duplicate backup sets, will not display a scheduled job status. |
Server Paused |
The job is ready, but the Backup Exec media server has been paused. No jobs are dispatched while the media server is paused. |
Superseded by job x |
The scheduled job cannot run because it was created by a policy that contains a job template with the following template rule: If start times conflict, <Template A> supersedes <Template B>. The <Template B> job will run according to the schedule set for it, after the <Template A> job completes. |
To Be Scheduled |
A state that the scheduled job transitions through as it is being sent for processing. |