N-central Troubleshooting
Backup Exec Job Codes
Last Modified
Thu Oct 25 14:22 GMT 2018
Description
- List of Backup Exec Job Codes that are reported
Environment
- N-able N-central All Versions
Solution
Backup Exec Job Status Codes
You can view the return values for the associated job status on the status screen for the Backup Exec service. These values represent specific critical issues.
1 | Job is terminal due to cancellation. |
2 | Job has been completed by the engine and is waiting on final disposition. |
3 | Job is terminal with success but there are some exceptions. |
4 | Job has been sent for execution. |
5 | Job is in a hold state. |
6 | Job is terminal with an error. |
7 | The schedule for the task is invalid. |
8 | The time window is mutually exclusive thus job will never run. |
9 | Job is eligible for dispatch and is late. |
10 | Date of job makes it eligible to run, but time is not in window. |
11 | DEPRECATE: Set as sub-status on READY job now. |
12 | The job needs to be dispositioned to an actual state. |
13 | The system forced recovery of the job. |
14 | Job has been disabled in the system. |
15 | The job will be restarted with checkpoint restart enabled, this value is only set in job history summary. |
16 | Job is currently running on server. |
17 | Job is eligible for dispatch. |
18 | The job has a due date in the future. |
19 | Job is terminal with success. |
20 | Job is ready, but another higher precedence task is eligible to run. |
21 | The job was aborted due to AbortThreshold timeout. |
22 | The job needs to have the due date calculated. |
23 | The job is linked to another job so will not start until main job is finished. |
24 | The job failed somewhere between RunJob() and before it was inserted on remote machine. |
25 | The job's scheduled start time has passed but a dependant job has not yet completed. |