About recovering failed jobs in CAS
The Backup Exec error-handling rule named Recovered Jobs is a custom error-handling rule that is used by CAS to recover the jobs that failed because of issues with internal job communications. This rule is created when Backup Exec is installed and is enabled by default.
The retry options for this rule are to retry the job twice, with an interval of five minutes between the retry attempts. During the first retry attempt, CAS attempts to re-delegate the jobs to another available managed Backup Exec server.
If this attempt fails, CAS makes a second attempt at finding another available managed Backup Exec server to process the jobs. If no managed Backup Exec servers are available, the final job disposition is to place the job on hold until you have fixed the error condition.
Note: If the checkpoint restart error-handling rule is enabled, then recovered jobs are not resubmitted to a Backup Exec server pool to be run on a different server. The checkpoint restart error-handling rule reschedules the job to run on the original server when that server comes online. To enable a recovered job to be resubmitted to a Backup Exec server pool, you must disable the checkpoint restart error-handling rule. Note: If you target a job to a Backup Exec server pool that contains multiple managed Backup Exec servers and a job failure occurs, the recovery process uses only the managed Backup Exec servers in the Backup Exec server pool. Managed Backup Exec servers that are not in the Backup Exec server pool are not used for job recovery.
When you open the job history entry for a recovered job, the reason for the failure is listed as Job Errors, with an explanation of the type of internal communication error that occurred. The job history entry also indicates that the job was recovered.
Note: Job logs are not created for the jobs that are recovered.
The following table describes the CAS error codes that are selected by default for the Recovered Jobs custom error-handling rule:
Table: Error codes for Recovered Jobs custom error-handling rule
| Error code | Description |
|---|---|
| 0xE000881B JOBDISPATCH | The displayed message is: Job failed while being dispatched. The job will be recovered. |
| 0xE000881D JOB_CASO_QUEUE | The displayed message is: The job could not be delegated to the destination managed Backup Exec server. The managed Backup Exec server may not be online, or there may be a communications failure. The job will be recovered. |
| FAILURE | |
| 0xE000881E JOB_CASO_REMOTEMMS_STARTFAILURE | The displayed message is: The job failed to start on the destination managed Backup Exec server, possibly because a database error occurred. The job will be recovered. |
More Information
Related information