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
- Troubleshooting cloud provider's revoked SSL certificate issues
- Troubleshooting cloud provider's CRL download issues
- How a host's CRL affects certificate revocation troubleshooting
- NetBackup job fails because of revoked certificate or unavailability of CRLs
- 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
- Troubleshooting issues with external CA-signed certificate revocation
- 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
- Unable to logon to the NetBackup Administration Console after external CA configuration
- Troubleshooting file-based external certificate issues
- Troubleshooting Windows certificate store issues
- Troubleshooting backup failures
- Troubleshooting backup failure issues with NAT clients
- Troubleshooting issues with the NetBackup Messaging Broker (or nbmqbroker) service
- Using NetBackup utilities
- About NetBackup troubleshooting utilities
- About the analysis utilities for NetBackup debug logs
- About the Logging Assistant
- 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
- About the DR_PKG_MARKER_FILE environment variable
- 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
About the bpclntcmd utility
The bpclntcmd utility resolves IP addresses into host names and host names into IP addresses. It uses the same system calls as the NetBackup application modules.
With the - pn option, bpclntcmd connects to the master server and returns how the master server sees the connecting host: source IP address and port number, host name to which the IP resolves, and policy client for that host name. Add the - verbose option to see additional connection details including the host certificates that NetBackup uses to authenticate the hosts.
The following directory contains the command that starts the utility:
Windows | install_path\NetBackup\bin |
UNIX | /usr/openv/netbackup/bin |
On Windows, run this bpclntcmd command in an MS-DOS command window so you can see the results.
The bpclntcmd options that are useful for testing the functionality of the host name and IP address resolution are -ip, -hn, -sv, and -pn. The following topics explain each of these options:
-ip | bpclntcmd -ip IP_Address The -ip option lets you specify an IP address. bpclntcmd uses gethostbyaddr() on the NetBackup node and gethostbyaddr() returns the host name with the IP address as defined in the following: the node's DNS, WINS, NIS, or local hosts file entries. No connection is established with the NetBackup server. |
-hn | bpclntcmd -hn Hostname The -hn option specifies a host name. bpclntcmd uses gethostbyname() on the NetBackup node to obtain the IP address that is associated with the host name defined in the following: the node's DNS, WINS, NIS, or local hosts file entries. No connection is established with the NetBackup server. |
-sv | bpclntcmd -sv The -sv option displays the NetBackup version number on the master server. |
-pn | When the -pn option is run on a NetBackup client, it initiates an inquiry to the NetBackup master server. The server then returns information to the requesting client. First, the server is the first server in the server list. Then it displays the information that the server returns. The information the server returns is from the perspective of the master server and describes how the master server sees the connecting client. For example: bpclntcmd -pn expecting response from server rabbit.friendlyanimals.com dove.friendlyanimals.com dove 123.145.167.3 57141 The following is true of this command example:
|
-verbose | Use with the -pn option to display more details about the connection and the host certificates used. The following is an example of the output: $ bpclntcmd -pn -verbose expecting response from server rabbit.friendlyanimals.com 127.0.0.1:34923 -> 127.0.0.1:50464 PROXY 123.145.167.3:27082 -> 192.168.0.15:1556 LOCAL_CERT_ISSUER_NAME = /CN=broker/OU=root@ rabbit.friendlyanimals.com /O=vx LOCAL_CERT_SUBJECT_COMMON_NAME = fad46a25-1fe2-4143-a62b-2dc0642d8c45 PEER_CERT_ISSUER_NAME = /CN=broker/OU=root@ rabbit.friendlyanimals.com /O=vx PEER_CERT_SUBJECT_COMMON_NAME = 3ca8ab18-8eb3-4c8e-825d-faee9f9320d1 PEER_IP = 123.145.167.3 PEER_PORT = 27082 PEER_NAME = dove.friendlyanimals.com POLICY_CLIENT = dove |
Use -ip and -hn to verify the ability of a NetBackup node to resolve the IP addresses and host names of other NetBackup nodes.
For example, to verify that a NetBackup server can connect to a client, do the following:
On the NetBackup server, use bpclntcmd -hn to verify the following: The operating system can resolve the host name of the NetBackup client (as configured in the client list for the policy) to an IP address. The IP address is then used in the node's routing tables to route a network message from the NetBackup server.
On the NetBackup client, use bpclntcmd -ip to verify that the operating system can resolve the IP address of the NetBackup server. (The IP address is in the message that arrives at the client's network interface.)
Note:
The bpclntcmd command logs messages to the usr/openv/netbackup/logs/bpclntcmd directory (UNIX) or the install_path\NetBackup\logs\bpclntcmd (Windows). For earlier versions of NetBackup, bpclntcmd logs are sent to the bplist directory, not the bpclntcmd directory.