Backup3G/User Guide/Appendix B - Checking Job Status Codes
From Documentation
< Backup3G | User GuideRevision as of 07:27, 21 April 2006; view current revision
←Older revision | Newer revision→
←Older revision | Newer revision→
To check the status of all backup jobs on a host:
- Log in to the host and start backup3G
- Select Monitor (GUI version) or Monitor backup jobs & maintain logfiles (CUI version).
The Backup Monitor is a dynamic display showing the status of all scheduled and running backups, and all completed backups that have not yet been acknowledged.
To help diagnose a problem you can get more information by highlighting the backup then selecting Logfiles > Display.
This appendix lists suggested actions to be taken for each status code.
- Note
- Your operating system or drives may return other status codes not known to backup3G.
Contents |
Status of Active Backup and Recovery Jobs
This table lists status codes for jobs that are currently active—that is, they have been scheduled or started but not yet completed.
| Status | Meaning | Action |
|---|---|---|
| Scd: <time> | The job is scheduled to start at <time> | None |
| Waiting for drive | The job is queued and is waiting for a drive to become available. | None |
| Run: PID #M Step #N | The job currently running step #N of a multipart backup. | None |
| Attn: Change media (drive is manually-loaded) | The job is waiting for an operator to load the next scratch volume. | Unload the volume that was just written and load a new scratch volume. (From the Backup Monitor: Jobs > Change volume). |
| Attn: Change media (drive has an auto-loading device) | The job can’t find a valid scratch volume in the stacker/media library. | Allocate more scratch volumes to the stacker/media library location. (From the Stacker option: Maintain > Media > Move > Alloc scratch). |
| Attn: Load #volume (drive is manually-loaded) | A recovery job is waiting for an operator to load the next backup volume. | Load the requested backup volume. (From the Backup Monitor: Jobs > Change volume). |
| Attn: Load #volume (drive has an auto-loading device) | A recovery job can’t find the volume containing the next file(s) to be recovered in the stacker/media library. | Load the requested volume into the stacker/media library. (From the Stacker option: Maintain > Media > Move > Alloc active). |
Status of Completed Backup and Recovery Jobs.
| Status | Meaning | Action |
| Cancelled | The job was cancelled by an operator before it started. | Check why the job was cancelled. |
| End: Killed | The job was cancelled by an operator while it was running. | Check why the job was killed. |
| End: Successful | The job completed without errors. | None |
| Backup command failed, probably due to a usage error. | Check the backup log for other error messages. Use ‘Show steps’ to check that the command run by this backup step is correct. If you filled in the Options field for this backup item, check that the options are recognized by the backup command. | |
| End: Status 80 | ‘Device open’ error. | Check that the drive is online, clean, and operating correctly. |
| End: Status 81 | The media change failed. | Add new volumes of this media type, or scratch some existing backup volumes. |
| End: Status 82 | Child process killed—no child exit status. Probably means that the process running the backup method was killed by a user from the command line. | Check why the process was killed and rerun the backup job. |
| End: Status 83 | Not enough data read into input buffer. | Probably indicates a system problem—can’t be fixed within backup3G. |
| End: Status 90 | Error reading data from or writing to device. Usually indicates unexpected endof-tape or media error. | Check the tape. If writing a backup, try another volume. If recovering data from a backup, try another drive. |
| End: Status 91—94 | Various other device I/O errors. | Check the drive. |
| End: Status 95—98 | Various stdio I/O errors. | May indicate a system problem—possibly low swap space. |
| End: Status 99 | Job failed or was cancelled by an operator, e.g. during volume change. | Check the backup log for other error messages. |