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
Steps to carry out when you see exit status 5988 during catalog recovery
Use this procedure when you come across exit status 5988 during catalog backup.
To resolve the issue
- Run the following command:
UNIX: /usr/openv/netbackup/bin/nbcertcmd -ping
Windows: install_path\NetBackup\bin\nbcertcmd -ping
If it is executed successfully, proceed to the next step.
If it fails with status 8509 (The specified server name was not found in the web service certificate), follow the steps in this article:
https://www.veritas.com/support/en_US/article.000126751
Proceed to the next step.
- Perform the user logon on the master server. Use the following command:
install_path\netbackup\bin\bpnbat -login -loginType WEB
For example:
install_path\netbackup\bin\bpnbat -login -loginType WEB
Authentication Broker [abc.example.com is default]: Authentication port [0 is default]: Authentication type (NIS, NISPLUS, WINDOWS, vx, unixpwd, ldap) [WINDOWS is default]: Domain [abc.example.com is default]: Login Name [administrator is default]: Password: Operation completed successfully.
- Note the value of key Client_Name for the master server. For a clustered master server, note the value of key Cluster_Name.
This value can be found at:
UNIX: /usr/openv/netbackup/bp.conf
Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config
This value can be either a FQDN or a short name.
For example:
abc.example.com
- Note the host ID of the master server. You can obtain its value by running the following command:
install_path\netbackup\bin\nbcertcmd -listCertDetails
For a clustered master server, run the following command:
install_path\netbackup\bin\nbcertcmd -listCertDetails -cluster
This command can return multiple records (if only one record is returned, select the host ID provided in that record).
Example:
install_path\netbackup\bin\nbcertcmd -listCertDetails
Master Server : abc Host ID : 78f9eed4-xxxx-4c6a-bb40-xxxxxxxxx Issued By : /CN=broker/OU=root@abc/O=vx Serial Number : 0x62e108c90000000c Expiry Date : Aug 21 08:42:54 2018 GMT SHA1 Fingerprint : 50:89:AE:66:12:9A:29:4A:66:E9:DB:71:37:C7: EA:94:8C:C6:0C:A0 Master Server : xyz Host ID : 5a8dde7b-xxxx-4252-xxxx-d3bedee63e0a Issued By : /CN=broker/OU=root@xyz.example.com/O=vx Serial Number : 0x6ede87a70000000a Expiry Date : Aug 21 09:52:13 2018 GMT SHA1 Fingerprint : FE:08:C2:09:AC:5D:82:57:7A:96:5C:C1:4A:E6: EC:CA:CC:99:09:D2 Operation completed successfully.
Here, two records are fetched.
For the first record, the issuer name in the "Issued By" field matches the short name of the client_name obtained in step 3.
Hence select the host ID that is provided in the record.
- Add host ID-to-host name mapping for the master server. Map the host ID obtained in step 4 with the host name obtained in step 3.
Use the following command:
install_path\netbackup\bin\admincmd\nbhostmgmt -a -i host ID -hm hostname
install_path\netbackup\bin\admincmd\nbhostmgmt -a -i 78f9eed4-xxxx-4c6a-bb40-xxxxxxxxx -hm abc.example.com abc.example.com is successfully mapped to 78f9eed4-xxxx-4c6a-bb40-xxxxxxxxx.
Alternately, you can also add this host-ID-to-host name mapping using the NetBackup Administration Console. Use the Security Management > Host Management > Hosts tab.
- Renew the host ID-based certificate of the master server. Use the following command:
install_path\netbackup\bin\nbcertcmd -renewCertificate
For a clustered master server, run the following command:
install_path\netbackup\bin\nbcertcmd -renewCertificate -cluster