Troubleshooting guide

Status Codes
80 NetBackup Troubleshooting Guide - UNIX
Recommended Action:
1. Ensure that the client’s server list contains entries for the master server and for any
media servers that could be used during a backup or restore.
2. Examine the progress log on the client for messages on why the restore failed. Also,
check the All Log Entries report on the server.
3. On Windows NT/2000 and UNIX, check ownership and permission on directories
where files will be restored.
4. Correct problems that you find and retry the restore.
Status Code: 6
Message: the backup failed to back up the requested files
Explanation: Errors caused the user backup to fail.
Recommended Action:
1. Verify that you have read access to the files. Check the progress log on the client for
messages on why the backup failed. Correct problems and retry the backup.
2. On Windows NT/2000 clients, verify that the account used to start the NetBackup
Client service has read access to the files.
3. On Macintosh clients, this code can be due to multiple backups being attempted
simultaneously on the same client. Some possible solutions are:
◆ Adjust the backup schedules.
◆ If the client is only in one class, set the class attribute, Limit jobs per class, to 1.
◆ Set the NetBackup global attribute, Maximum jobs per client, to 1 (note that this
limits all clients in all classes).
4. For a UNIX database extension client (for example, NetBackup for Oracle), this can
mean a problem with the script that is controlling the backup.
Check the progress report on the client for a message such as “Script exited
with status code = number” (the number will vary). The progress log also
usually names the script.
Check the script for problems. Also, check the troubleshooting logs created by the
database extension. See the NetBackup guide that came with the database extension
for information on the scripts and troubleshooting logs.