Troubleshooting guide

Chapter 4, Status Codes and Messages 99
Status Codes
◆ The bpbkar client process is not hung, but due to the files and directories it is
scanning, it has not replied to the server within CLIENT_READ_TIMEOUT or
CLIENT_CONNECT_TIMEOUT. This has been seen to occur during backups when
directories have thousands of unmodified files; it has also been seen when
backing up file systems or directories that reside on optical disk, which is
considerably slower than magnetic disk.
For this case, try adding or modifying the CLIENT_READ_TIMEOUT and
CLIENT_CONNECT_TIMEOUT values in the server’s
/usr/openv/netbackup/bp.conf file. The default for the
CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT is 300 seconds if
unspecified.
Use your system’s ps command and monitor CPU utilization to help decide which of
the above conditions exist.
When you are through investigating the problem, delete the
/usr/openv/netbackup/logs/bpbkar directory, since the log files can become
quite large and are not deleted automatically. Also delete
/usr/openv/netbackup/bpbkar_path_tr so you do not generate larger log files
than needed the next time you create directory
/usr/openv/netbackup/logs/bpbkar.
2. On Windows NT/2000 systems, try the following:
◆ Disable the following file:
install_path\Veritas\NetBackup\bin\admincmd\tracker.exe
◆ Repair hard drive fragmentation. You could try an application called Diskeeper
Lite, which is part of the Windows NT Resource Kit.
◆ Make sure there is enough space available in \temp.
3. If the server cannot connect to the client, create bpcd or bpbkar (UNIX and Windows
NT/2000 only) activity log directories on the client, retry the operation, and check the
resulting logs. If these logs do not provide a clue, create a bpbrm activity log on the
server, retry the operation again, and check the resulting activity log.
If the bpbrm log has entries similar to the following:
bpbrm hookup_timeout: timed out waiting during the client hookup
bpbrm Exit: client backup EXIT STATUS 41: network connection timed out
then the problem is in the routing configuration on the server.
Verify that the client IP address is correct in the name service that is being used. On
UNIX, if both NIS and DNS files are used, verify that they match.
Also, see “Resolving Network Communication Problems” on page 24.