Veritas NetBackup™ 8.0 Troubleshooting Guide
- Introduction
- Troubleshooting procedures
- Troubleshooting NetBackup problems
- Verifying host name and service entries in NetBackup
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Resolving PBX problems
- About troubleshooting Auto Image Replication
- Using NetBackup utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the robotic test utilities
- Disaster recovery
- About disk recovery procedures for UNIX and Linux
- About clustered NetBackup server recovery for UNIX and Linux
- About disk recovery procedures for Windows
- About clustered NetBackup server recovery for Windows
- About recovering the NetBackup catalog
- About NetBackup catalog recovery and OpsCenter
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup relational database
Resolving network communication problems with Windows clients
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 Windows 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
Before you retry the failed operation, do the following:
Increase the logging level on the client (see the NetBackup Administrator's Guide, Volume I, under "Client Settings properties").
On the NetBackup master server, create a bprd debug log directory and on the clients create a bpcd debug log.
On the NetBackup server, set the Verbose level to 1.
See the NetBackup Logging Reference Guide for help changing the logging level.
- If this client is new, verify the client and the server names in your NetBackup configuration.
- Verify network connectivity between client and server by pinging from the server to the client and vice versa. Use the following command:
# ping hostname
Where hostname is the name of the host as configured in the following:
NetBackup policy configuration
WINS
DNS (if applicable).
hosts file in system directory %SystemRoot%\system32\drivers \etc\hosts (Windows 2003 or 2008)
If ping succeeds in all instances, it verifies connectivity between the server and client.
If ping fails, 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 on. A workstation that is not turned on is a common source of connection problems with workstations.
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 the bpcd debug logs for problems or errors. See the NetBackup Logging Reference Guide on how to enable and use these logs.
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:
Windows
Check the NetBackup client service port number.
Start the Backup, Archive, and Restore interface on the client. On the File menu, click NetBackup Client Properties. In the NetBackup Client Properties dialog box on the Network tab, check the NetBackup client service port number.
Verify that the setting on the Network tab matches the one in the services file. The services file is located in:
%SystemRoot%\system32\drivers\etc\services (Windows)
The values on the Network tab are written to the services file when the NetBackup client service starts.
UNIX NetBackup servers
The bpcd port number is in the /etc/services file. On Windows NetBackup servers, see the Client Properties dialog box in the Host Properties window.
See Using the Host Properties window to access configuration settings.
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.
- Verify that the NetBackup Request Service (bprd) port number on Microsoft Windows is the same as on the server (by default, 13720). Do one of the following:
Windows clients
Check the NetBackup client service port number.
Start the Backup, Archive, and Restore interface on the client. On the File menu, click NetBackup Client Properties. In the NetBackup Client Properties dialog box on the Network tab, check the NetBackup client service port number.
Verify that the setting on the Network tab matches the one in the services file. The services file is located in:
%SystemRoot%\system32\drivers\etc\services (Windows)
The values on the Network tab are written to the services file when the NetBackup client service starts.
UNIX NetBackup servers
The bprd port number is in the /etc/services file.
See Using the Host Properties window to access configuration settings.
Windows NetBackup servers
Set these numbers in the Client Properties dialog box in the Host Properties window.
See Using the Host Properties window to access configuration settings.
- Verify that the hosts file or its equivalent contains the NetBackup server name. The hosts files are the following:
Windows 2003
%SystemRoot%\system32\drivers\etc\hosts
UNIX
/etc/hosts
- Verify client-to-server connectability by means of ping or its equivalent from the client (step 3 verified the server-to-client connection).
- If the client's TCP/IP transport allows telnet and ftp from the server, try these services as additional connectivity checks.
- Use the bpclntcmd utility to verify client to master server communications. When the -pn and -sv options run on a client, they initiate inquiries to the master server (configured in the server list on the client). The master server then returns information to the requesting client.
- Use the bptestbpcd utility to try to establish a connection from a NetBackup server to the bpcd daemon on another NetBackup system. If successful, it reports information about the sockets that are established.
- Verify that the client operating system is one of those supported by the client software.