Veritas NetBackup™ Troubleshooting Guide
- Introduction
- Troubleshooting procedures- About troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting installation problems
- Troubleshooting configuration problems
- Device configuration problem resolution
- Testing the master server and clients
- Testing the media server and clients
- Resolving network communication problems with UNIX clients
- Resolving network communication problems with Windows clients
- Troubleshooting vnetd proxy connections- vnetd proxy connection requirements
- Where to begin to troubleshoot vnetd proxy connections
- Verify that the vnetd process and proxies are active
- Verify that the host connections are proxied
- Test the vnetd proxy connections
- Examine the log files of the connecting and accepting processes
- Viewing the vnetd proxy log files
 
- Troubleshooting security certificate revocation- How a host's CRL affects certificate revocation troubleshooting
- NetBackup job fails because of revoked certificate
- NetBackup job fails because of apparent network error
- NetBackup job fails because of unavailable resource
- Master server security certificate is revoked
- Determining a NetBackup host's certificate state
 
- About troubleshooting networks and host names
- Verifying host name and service entries in NetBackup- Example of host name and service entries on UNIX master server and client
- Example of host name and service entries on UNIX master server and media server
- Example of host name and service entries on UNIX PC clients
- Example of host name and service entries on UNIX server that connects to multiple networks
 
- About the bpclntcmd utility
- Using the Host Properties window to access configuration settings
- Resolving full disk problems
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Troubleshooting problems with the NetBackup web server certificate
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- About troubleshooting Auto Image Replication
- Troubleshooting network interface card performance
- About SERVER entries in the bp.conf file
- About unavailable storage unit problems
- Resolving a NetBackup Administration operations failure on Windows
- Resolving garbled text displayed in NetBackup Administration Console on a UNIX computer
 
- Using NetBackup utilities- About NetBackup troubleshooting utilities
- About the analysis utilities for NetBackup debug logs
- About network troubleshooting utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the NetBackup consistency check repair (NBCCR) utility
- About the nbcplogs utility
- About the robotic test utilities
 
- Disaster recovery- About disaster recovery
- About disaster recovery requirements
- Disaster recovery packages
- About disaster recovery settings
- Recommended backup practices
- 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
- Generating a certificate on a clustered master server after disaster recovery installation
- About restoring disaster recovery package
- Restoring disaster recovery package on Windows
- Restoring disaster recovery package on UNIX
- About recovering the NetBackup catalog- About NetBackup catalog recovery on Windows computers
- About NetBackup catalog recovery from disk devices
- About NetBackup catalog recovery and symbolic links
- About NetBackup catalog recovery and OpsCenter
- NetBackup disaster recovery email example
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup relational database
- Recovering the NetBackup catalog when NetBackup Access Control is configured
- Recovering the NetBackup catalog from a nonprimary copy of a catalog backup
- Recovering the NetBackup catalog without the disaster recovery file
- Recovering a NetBackup user-directed online catalog backup from the command line
- Restoring files from a NetBackup online catalog backup
- Unfreezing the NetBackup online catalog recovery media
- Steps to carry out when you see exit status 5988 during catalog recovery
 
 
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 
 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 %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.