Troubleshooting guide

Status Codes
104 NetBackup Troubleshooting Guide - UNIX
◆ On PC clients, increase the debug or log level as explained in the activity log
topics in Chapter 3.
4. Retry the operation and examine the resulting logs.
5. On UNIX systems, use the UNIX sum command to check for corrupt binaries.
6. On SGI IRIX 6.2/6.4 systems, clients may be missing the libdbm.so shared library.
Refer to the SGI/IRIX install CD-ROM for the eoe.sw.dmi package.
Status Code: 50
Message: client process aborted
Explanation: The client backup aborted. One instance when this code appears is if a
NetBackup master or media server is shut down or rebooted when a backup or restore is
in process.
Recommended Action:
1. Enable detailed activity logging:
◆ Create a bpbkar activity log directory (UNIX or Windows NT/2000 only).
◆ Create a bpcd activity log directory (this log is created automatically on
Macintosh clients.)
◆ On UNIX clients, add the VERBOSE option to the
/usr/openv/netbackup/bp.conf file.
◆ On PC clients, increase the debug or log level as explained in the activity log
topics in Chapter 3.
2. Retry the operation and examine the resulting logs.
3. On UNIX clients, check for core files in the / directory.
4. On UNIX clients, check the system log (/usr/adm/messages on Solaris) for system
problems.
5. This problem can sometimes be due to a corrupt binary.
On UNIX clients, use the UNIX sum command to check the bpcd, bpbkar, and tar
binaries, located in /usr/openv/netbackup/bin on the client. Reinstall them if
they are not the same as in the client directory under
/usr/openv/netbackup/client on the server.