Scheduled job statuses

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 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.

See Setting template rules.

Invalid Schedule

The scheduled job will not run because of one of the following:

  • An associated record in the database is missing, or

  • The availability window and the schedule for the selection list being backed up by this job do not have a time in common.

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.

See Custom error-handling rule for recovered jobs.

Ready

The job is ready to run, but cannot for one of the following reasons:

  • Internal error. No devices are available, but the cause is unknown.

  • Invalid job. The job type in unknown; there may be an internal error or the database is corrupted.

  • Invalid target. This is a device type that no longer exists.

  • Media server not available.

  • No license for option name. A license must be purchased and installed on the targeted media server.

  • No media servers are available.

  • No media servers available in media server pool.

  • Specified destination cascaded drive pool is empty.

  • Specified destination device pool is empty.

  • Specified destination device is not in media server pool.

  • Specified destination device not on local media server.

  • Specified destination device pool on local media server is empty.

  • The destination device cannot be a cascaded drive pool.

  • The destination device cannot be a device pool.

  • The destination device cannot be a media server.

  • There is another job running in the system that is blocking. execution of this job. This job will run after the other job completes.

  • Invalid input.

  • Incompatible Resumes.

  • No server license available.

  • No multi-server license available.

  • No Windows 2000 license.

  • No Windows 2000 server.

  • No NetWare server.

  • Need local media server.

  • Local server is not a media server.

  • No idle devices are available.

  • No eligible devices within the device pool are available.

  • Blocked by an active, linked Duplicate Backup Sets job.

  • No devices within the cascaded drive pool are available.

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.

See Pausing and resuming storage devices.

Superseded by job x

The scheduled job cannot run because it was created by a policy that contains a job template with the 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.

See Setting template rules.

To Be Scheduled

A state the scheduled job transitions through as it is being sent for processing.

More Information

Active job statuses

Completed job statuses

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.