Troubleshooting guide

General Test and Troubleshooting Procedures
28 NetBackup Troubleshooting Guide - UNIX
Note We suggest that you not change the port number for bpcd or other NetBackup
services. Do so only if there is no alternative; and then, remember that all
NetBackup servers and clients in the configuration must use this new port
assignment.
◆ If there is a process other than bpcd using the port, try rebooting the client to clear
the problem. If the problem is still not fixed, it might be necessary to change one
of the service numbers (preferably for the other service). You do this by modifying
the /etc/services files then sending SIGHUP signals to the inetd processes
on your clients.
/bin/ps -ef | grep inetd
kill -HUP the_inetd_pid
or
/bin/ps -aux | grep inetd
kill -HUP the_inetd_pid
Note On a Hewlett-Packard platform, use inetd -c to send a SIGHUP to inetd.
Also make applicable NIS or DNS updates.
If the problem is with an AIX client, and you make changes to
/etc/inetd.conf and /etc/services information, use SMIT to verify that
the InetServ object class has been updated as explained in step 4.
6. To verify basic client to master server communications, use the bpclntcmd utility.
When run on a NetBackup client, the -pn and -sv options initiate inquiries to the
NetBackup master server (as configured in the bp.conf file on the client). The master
server then returns information to the requesting client. For more information, see
“Using bpclntcmd” on page 35.
PC Clients
1. Before retrying the failed operation:
◆ Increase the logging level on the client (see the user’s guide for the client).
◆ On the NetBackup server, create a bprd activity log directory and on the clients
create a bpcd activity log.
◆ On a Windows NT/2000 NetBackup server, set the Verbose level to 1 on the
General tab of the properties dialog box in the Configure - NetBackup window
(see “Using the Configure - NetBackup Window” on page 57).
◆ On a UNIX NetBackup server, add the VERBOSE option to the bp.conf file.