Understanding a Job Log Completion Status

  • Modified Date:
  • Article ID:000027860


Understanding a Job Log Completion Status


In Backup Exec (tm), there are nine possible job completion statuses for jobs that were processed. These are as mentioned below:
1)Successful:  The job completed without errors.

2)Completed with exceptions:  If a file in use skipped, or a corrupted file was encountered during the operation, then the user will receive this job status.

3)Failed over: The job ran in a cluster environment and was active on one machine and then the cluster performed a failover and the job was restarted on another server in the cluster. There are two separate sets of job history when a job is failed over. The first job history will have the "Failed over" status and the second job history will have the status that is appropriate for the completed job.

4)Resumed: The status is the same as the failed over status, however the Apply CheckPoint Restart option was selected.

5)Canceled: If the Administrator terminates an active job

6)Canceled, timed out: The Enable automatic cancellation feature in the Frequency - Schedule property was enabled and the job was not completed within the specified timeframe.

7)Failed: The operation took place, but one or more significant errors occurred. The job log should indicate what caused the errors to be able to determine if the job needs to be run again.  For example, if a job failure occurred due to a lost connection during job processing, resubmit the job once the connection issue has been resolved.

If a drive loses power during a backup operation to tape, restart the backup job using a different tape. The data written to the tape can be restored  up to the point of the power loss, but the tape should not be reused for subsequent backup operations.  A failed job will have an error message in the Errors section of the job log with a navigable link to the Symantec Software Support Services web site.

8)Recovered: The job was active when the status of the managed media server changed from Communication Stalled to No Communication.The custom error-handling rule for Recovered Jobs was applied to the job.

9)Missed: The job did not run during the scheduled time window. The job by default will be rescheduled to run based on the time window specified.

Some reasons a job may fail are:

1. Devices specified by the job were not available when the job was run.

2. The logon account information used in the backup job is incorrect.  Verify the logon account information is valid for the resource being backed up.

3. There was a problem with the storage device when the job was run.

4. The computer being backed up was shut down before or during the backup job.



Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)