The following procedure is for resolving NetBackup communications problems, such as those associated with NetBackup status codes 54, 57, and 58. This procedure consists of two variations: one for UNIX clients and another for PC clients.
Note:In all cases, ensure that your network configuration works correctly outside of NetBackup before trying to resolve NetBackup problems.
This procedure helps you resolve network communication problems with PC clients. To resolve network communication problems
1
Before you retry the failed operation, do the following:■ Increase the logging level on the client (see the client’s user guide). ■ On the NetBackup server, create abprddebug log directory and on the
clients create abpcddebug log.
■ On the NetBackup server, set theVerboselevel to 1.
See“Changing the logging level on Windows clients”on page 169.
2
If this client is new, verify the client and the server names in your NetBackupconfiguration.
See“Verifying host name and service entries in NetBackup”on page 53.
3
Verify network connectivity between client and server by pinging from the serverto the client and vice versa. Use the following command:
# ping hostname
Wherehostnameis the name of the host as configured in the following: ■ NetBackup policy configuration
■ WINS
■ DNS (if applicable).
■ hostsfile in system directory%SystemRoot%\system32\drivers \etc\hosts(Windows XP or 2003)
Ifpingsucceeds in all instances, it verifies connectivity between the server
and client.
Ifpingfails, you have a network problem outside of NetBackup that must be resolved before you proceed. As a first step, verify that the workstation is turned
46 Troubleshooting procedures
on. A workstation that is not turned on is a common source of connection problems with PC workstations.
4
On Microsoft Windows clients, ensure that the NetBackup Client service is active by checking the logs. Use the Services application in the Control Panel to verify that the NetBackup Client service is running. Start it if necessary. ■ Check thebpcddebug logs for problems or errors. Instructions are availableon how to enable and use these logs. See“About legacy logging”on page 153.
■ Verify that the same NetBackup client service (bpcd) port number is specified
on both the NetBackup client and server (by default, 13782). Do one of the following:
Check the NetBackup client service port number. Start theBackup, Archive, and Restoreinterface on the client. On theFilemenu, clickNetBackup Client Properties. In theNetBackup Client Propertiesdialog box on theNetworktab, check the NetBackup client service port number.
Verify that the setting on theNetworktab matches the one in the services file. Theservicesfile is located in:
%SystemRoot%\system32\drivers\etc\services
(Windows)
The values on theNetworktab are written to the
servicesfile when the NetBackup client service starts. Windows
Thebpcdport number is in the/etc/servicesfile. On Windows NetBackup servers, see the Client Properties dialog box in theHost Propertieswindow.
See“Using the Host Properties window to access configuration settings”on page 67.
UNIX NetBackup servers
Correct the port number if necessary. Then, on Windows clients and servers, stop and restart the NetBackup Client service.
Do not change NetBackup port assignments unless it is necessary to resolve conflicts with other applications. If you do change them, do so on all NetBackup clients and servers. These numbers must be the same throughout your NetBackup configuration.
47 Troubleshooting procedures
5
Verify that the NetBackup Request Service (bprd) port number on MicrosoftWindows is the same as on the server (by default, 13720). Do one of the following:
Check the NetBackup client service port number. Start theBackup, Archive, and Restoreinterface on the client. On theFilemenu, clickNetBackup Client Properties. In theNetBackup Client Propertiesdialog box on the
Networktab, check the NetBackup client service port number. Verify that the setting on theNetworktab matches the one in the services file. Theservicesfile is located in:
%SystemRoot%\system32\drivers\etc\services
(Windows)
The values on theNetworktab are written to theservices
file when the NetBackup client service starts. Windows clients
Thebprdport number is in the/etc/servicesfile. See“Using the Host Properties window to access configuration settings”on page 67.
UNIX NetBackup servers
Set these numbers in theClient Propertiesdialog box in the Host Properties window.
See“Using the Host Properties window to access configuration settings”on page 67.
Windows NetBackup servers
6
Verify that thehostsfile or its equivalent contains the NetBackup server name. Thehostsfiles are the following:%SystemRoot%\system32\drivers\etc\hosts
Windows XP or 2003
/etc/hosts
UNIX
7
Verify client-to-server connectability by usingpingor its equivalent from theclient (step 3 verified the server-to-client connection).
8
If the client’s TCP/IP transport allowstelnetandftpfrom the server, try these services as additional connectivity checks.48 Troubleshooting procedures
9
Use thebpclntcmdutility to verify client to master server communications.When-pnand-svrun on a client, they initiate inquiries to the master server
(as configured in the server list on the client). The master server then returns information to the requesting client.
See“About the bpclntcmd utility”on page 65.
10
Use thebptestbpcdutility to try to establish a connection from a NetBackupserver to thebpcddaemon on another NetBackup system. If successful, it reports information about the sockets that are established.
See“About the bpclntcmd utility”on page 65.