Troubleshooting guide

Status Codes
98 NetBackup Troubleshooting Guide - UNIX
◆ On Windows NT/2000, 98, and 95 systems, the master server is designated on the
Servers tab in the Master Server Properties dialog. To display this dialog, see
“Using the Configure - NetBackup Window” on page 57.
◆ On UNIX, and Macintosh systems, the master server is the first SERVER entry in
the bp.conf file.
◆ On NetWare target and OS/2 clients the master server name is the first SERVER
entry in the bp.ini file.
If you change the server list on a UNIX master server, you must stop and then restart
the NetBackup Request daemon (bprd) and NetBackup database manager daemon
(bpdbm) for the changes to take effect. On Windows NT/2000, stop and restart the
NetBackup Request Manager and NetBackup Database Manager services.
3. Status code 40 can also be due to the operator denying a mount request.
Status Code: 41
Message: network connection timed out
Explanation: The server did not receive any information from the client for too long a
period of time.
Recommended Action:
1. On a UNIX or Windows NT/2000 clients, check for the following problems with the
bpbkar client process.
◆ The bpbkar client process is hung on a file that has mandatory locking set. For
this case, add the following to the client’s bp.conf file:
VERBOSE
and as root on the client execute:
touch /usr/openv/netbackup/bpbkar_path_tr
mkdir /usr/openv/netbackup/logs/bpbkar
Then retry the operation. The names of the files are logged in the activity log file
in the /usr/openv/netbackup/logs/bpbkar directory before bpbkar
processes them. The last file in the log will be the file that is causing problems.
Note Also, use the above procedure for other, “unknown” bpbkar hangs.
If the problem is due to mandatory file locking, you can have NetBackup skip the
locked files by setting LOCKED_FILE_ACTION to SKIP in the
/usr/openv/netbackup/bp.conf file on the client.