Troubleshooting guide

Status Codes
100 NetBackup Troubleshooting Guide - UNIX
4. If you are using an AIX token ring adapter and the routed daemon is running, the
timeout can occur because the token ring adapter creates dynamic routes, causing the
routed daemon to crash.
5. For a FlashBackup client, this can happen if the file system being backed up is very
large and has a very large number of files. It can also occur if a large number of
concurrent data streams are active at the same time. The corrective action is to add
CLIENT_READ_TIMEOUT to the /usr/openv/netbackup/bp.conf file and set it
to increase the timeout interval.
6. Make sure all recommended NetBackup patches have been installed. Check the
VERITAS support web site for current patch information. (Go to
www.support.veritas.com, then select “NetBackup” followed by “files and updates”.)
7. Add the CLIENT_READ_TIMEOUT values to the master server, media server and
client when a NetBackup database extension product is installed. The values should
all be the same for each server. The value set is dependent on the size of the database
being backed up. See the NetBackup System Administrator’s Guide for more information
on CLIENT_READ_TIMEOUT.
Status Code: 42
Message: network read failed
Explanation: An attempt to read data from a socket failed.
Recommended Action:
1. Verify that both the client and the server are operational.
2. Perform “Resolving Network Communication Problems” on page 24.
3. Check the Problems report for clues.
Status Code: 43
Message: unexpected message received
Explanation: The client and server handshaking was not correct.
Recommended Action:
1. Verify that the correct version of software is running on the client and the server.
2. Enable detailed activity logging:
◆ On the server, create a bpbrm activity log directory.