Job Status Descriptions

The current status of the job is in the Status column in the Job Controller window. The following job status levels may appear in the Job Controller window for different jobs:

Job Status	Description
Completed	The job has completed successfully. A job completed is fully restorable. Note that pop-up messages for reporting job completion can be enabled or disabled using the F12 key.
Completed With Warning	The job has completed successfully but with a notification to the user. A job completed with warning is fully restorable.
Completed With One or More Errors	The job has completed with errors. A job completed with errors is partially successful and restorable, excluding any failed items. The following administration conditions will result in the Completed With One or More Errors status level. Disaster Recovery Backup During the operation, Phase 1 failed and Phase 2 completed, or Phase 1 completed and Phase 2 failed. Data Aging During the operation, one or more components failed, for example, subclients failed to be aged or job history failed to be removed. Install Updates During the operation, one or more clients failed to be updated. Offline Content Indexing During the offline content indexing operation, one or more backup data failed to be content indexed. Information Management During an information management operation, if the operation defined in the Automated Content Classification Policy is partially successful. The following iDataAgent-specific conditions will result in the Completed With One or More Errors status level. Exchange Compliance Archiver During a retrieve operation, one or more files failed to be retrieved. Exchange Public Folder Archiver During a recovery operation, one or more files failed to be recovered. Microsoft Windows File System During a system state backup operation, one or more non-critical components failed to be backed up. During a file system restore operation, one or more files failed to restore or were locked. During a system state restore operation, one or more non-critical components failed to be restored. Exchange Database During a backup operation of a storage group assigned to a subclient, one or more databases failed to be backed up. For information, see Exchange Database Agent Backup Troubleshooting. During a restore operation, one or more databases failed to be restored. For information, see Exchange Database Agent Restore Troubleshooting. Exchange Mailbox Agent During a backup operation, if at least one item (mailbox, public folder, or PST) succeeded and at least one failed to be backed up. Message level failures are not considered for the job level status. Informix During a backup operation, one or more files failed to be backed up. For information, see Troubleshooting - Informix iDataAgent. Oracle, Oracle RAC During a backup operation, one or more files failed to be backed up. SAP for Oracle, SAP for MAXDB During a backup operation, one or more files failed to be backed up. For more information about SAP for Oracle, see the "SAP for Oracle" section on this page. SharePoint Server Agent During a backup operation, one or more elements in the subclient content failed to be backed up. During a restore operation, one or more elements in the subclient content failed to be restored. Sybase SYBASE HOME is E:\sybase\syb157 SYBASE_ASE folder is ASE-15_0 SYBASE_OCS folder is OCS-15_0 Verify the following System Path entries E:\sybase\syb157\ASE-15_0\jobscheduler\bin E:\sybase\syb157\ASE-15_0\dll; E:\sybase\syb157\ASE-15_0\bin E:\sybase\syb157\OCS-15_0\lib3p64; E:\sybase\syb157\OCS-15_0\lib3p · E:\sybase\syb157\OCS-15_0\dll E:\sybase\syb157\OCS-15_0\bin · C:\install_path\Base During a backup operation, one or more files failed to be backed up. UNIX File System During a backup operation, one or more files failed to be backed up.
Committed	Jobs that committed during the specified time. For more information about committing jobs, see Committing a Backup Job by Using the Kill Option.
Dangling Cleanup	A job phase was terminated by the job manager, and the job manager is waiting for the completion of associated processes before killing the job phase.
Failed	The job failed due to errors or the job was failed by the job manager. For example, the job manager fails a job if the total running time is exceeded. For information on the total running time, see Setting the Total Running Time for Jobs.
Idle	It is applicable to persistent job. It means that the job has transferred some data, is currently idle, and will switch to running later.
Inactive	This state is for Edge Drive. This indicates that the job is not yet completed and currently not doing anything. The inactive jobs are hidden in the Job Controller and might become active later.
Interrupt Pending	The job manager is waiting for the completion of associated processes before interrupting the job due to resource contention with jobs that have a higher priority, etc.
Kill Pending	The job was terminated by the user using the Kill option, and the job manager is waiting for the completion of associated processes before killing the job.
Killed	The job is terminated by the user using the Kill option.
Pending	The Job Manager suspended the job due to phase failure and will restart it without user intervention.
Queued	The job conflicted with other currently running jobs (such as multiple data protection operations for the same subclient), and the Queue jobs if other conflicting jobs are active option is enabled. The Job Manager automatically resumes the job when the condition that caused the job to queue clears. For information on setting the Queue jobs if other conflicting jobs are active option, see Queuing Jobs. The activity control for the job type is disabled, and the Queue jobs if activity is disabled option is enabled. The Job Manager automatically resumes the job when the condition that caused the job to queue clears. For information on setting the Queue jobs if activity is disabled option, see Queuing Jobs. The Queue Scheduled Jobs option is enabled. Resume the scheduled jobs manually by using the Resume option, or resumed the scheduled jobs automatically by clearing the Queue Scheduled Jobs option. For information on setting the Queue Scheduled Jobs option, see Queuing Jobs. The job started during the operation window. The running job conflicted with the operation window, and the Allow running jobs to complete pass the operation window option was not enabled from the General tab of the Job Management dialog box. (This is only applicable for jobs that can be restarted. See Restarting Jobs for more information.)
Running	The job is active and has access to the resources it needs.
Running (Cannot be verified)	During a running operation, the Job Alive Check failed. See Job Alive Check Interval for more information.
Suspend Pending	A job is suspended by a user using the Suspend option, and the Job Manager is waiting for the completion of associated processes before stopping the job.
Suspended	A running, waiting or pending job was manually stopped by a user using the Suspend option. The job will not complete until it is restarted using the Resume option. A job was started in a suspended state using the Start Suspended or Startup in Suspended State options available from the dialog box of the job that was initiated. Restore jobs from Search Console can be started in the suspended state using the Start End User restores in suspended state and Start Compliance restores in suspended state options in the Browse/Search/Recovery Option Dialog box in the Control Panel.
System Kill Pending	The job has been terminated by the Job Manager, and the Job Manager is waiting for the completion of associated processes before killing the job.
Waiting	The job is active but waiting for resources (like, media or drive) to become available or for internal processes to start.

Changes on Job Status

The status of a job and the preemptibility of the phase of the job in the Job Controller determines the actions (Kill, Suspend, or Resume) that you can perform. Jobs that are pending or have failed, will be killed after being in that state for more than 24 hours. The following table describes the status of a job after an action has been performed on it:

Original Status	Actions Available	New Status
Running	Suspend Kill	Suspended Killed
Waiting	Suspend Kill	Suspended Killed
Interrupt Pending	N/A	N/A
Pending	Suspend Resume Kill	Suspended Returns to original state, resources and other conditions permitting Killed
Suspend Pending	Force Suspend Note: This option is not available for all jobs.	Suspended
Queued	Suspend Resume (Scheduled jobs only) Kill	Suspended Changes into a state of an active job, resources and other conditions permitting Killed
Suspended	Resume Kill	Returns to original state, resources and other conditions permitting Changes into a state of an active job, resources and other conditions permitting
Kill Pending	Force Kill Note: This option is not available for all jobs.	Killed
Dangling Cleanup	N/A	N/A