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
- 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
- Troubleshooting error messages in the NetBackup Administration Console
- Extra disk space required for logs and temporary files for the NetBackup Administration Console
- 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 or NAT servers
- Troubleshooting issues with the NetBackup Messaging Broker (or nbmqbroker) service
- Issues with email notifications for Windows systems
- Issues with KMS configuration
- Issues with initiating the NetBackup CA migration because of large key size
- Issues with the non-privileged user (service user) account
- Issues with group name format in the auth.conf file
- Troubleshooting the VxUpdate add package process
- Issues with FIPS mode
- Issues with malware scanning
- Issues with NetBackup jobs that are enabled for data-in-transit encryption
- Issues with Unstructured Data Instant Access
 
- 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
- About the NetBackup Smart Diagnosis (nbsmartdiag) utility
 
- 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
- NetBackup disaster recovery email example
- About recovering the entire NetBackup catalog
- Establishing a connection with NAT media server before catalog recovery
- 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
 
 
- Index
Issues with KMS configuration
NetBackup supports NetBackup Key Management Service (NetBackup KMS) and external key management service (external KMS).
This section provides procedures to resolve the backup failure issue in the following scenarios:
- When NetBackup KMS is configured 
- When external KMS is configured 
See the NetBackup Security and Encryption Guide for more information about KMS configurations.
To resolve backup failure issue in a setup where NetBackup KMS is configured
-      If a NetBackup policy is configured to use tape, AdvanceDisk or cloud storage, check job details.  If you see any errors, refer to the  NetBackup Status Codes Reference Guide.     For example in case of tape storage type, you may see the following error in the job details tab: Mar 27, 2020 5:20:40 PM - Error bptm (pid=11143) KMS failed with error status: Error details : Error Code : 1298, Error Message : Cannot communicate with one or more key management servers., Server - example.master.com:0, Error code - 25, . Mar 27, 2020 5:20:40 PM - Info bptm (pid=11143) EXITING with status 83 <---------- Mar 27, 2020 5:20:43 PM - Info bpbkar (pid=11132) done. status: 83: media open error 
- Run the following command on the master server to verify whether NetBackup KMS is configured or not:Install_Path/bin/nbkmscmd -listKMSConfig -name nbkms If NetBackup KMS configuration is not listed, check if the nbkms service is running or not. - If the nbkms service is running, run the following command to add the nbkms service configuration: - Install_Path/bin/nbkmscmd -discoverNBkms 
- If nbkms service is not running check nbkms logs at the following location: - On UNIX - /usr/openv/logs/nbkms - On Windows - Install_Path\NetBackup\logs\nbkms - Check if a key is created on the KMS server with the required key group. 
 
- Validate the NetBackup KMS configuration using the following command:Install_Path/bin/nbkmscmd -validateKMSConfig -name KMS_configuration_name 
-     Check if at least one active key is listed using the following  command:Install_Path/bin/nbkmscmd -listKeys -name KMS_configuration_name -keyGroupName key_group_name 
- If key is not listed, create a key with the required key group and clear the cache on the media server. Run the following command:Install_Path/bin/bpclntcmd -clear_host_cache 
- Check the following logs for further details:In case of tape, AdvanceDisk, and cloud storage: Install_Path/netbackup/logs/bptm In case of MSDP storage: MSDP_config_path/log/spoold/spoold.log For web service logs on the master server: Install_path/logs/nbwebservice/<51216-495-***-***-***.log> For nbkmiputil logs for NetBackup KMS: Install_Path/logs/nbkms 
To resolve backup failure issue in a setup where external KMS is configured
- If a NetBackup policy is configured to use tape, AdvanceDisk or cloud storage, check job details. If you see any errors, refer to the NetBackup Status Codes Reference Guide.
-  Run the following command on the master server to verify whether external KMS is configured or not:Install_Path/bin/nbkmscmd -listKMSConfig -name KMS_configuration_name If configuration is not listed, configure external KMS server. 
- Validate the external KMS configuration using the following command:Install_Path/bin/nbkmscmd -validateKMSConfig -name KMS_configuration_name 
- Run the following command  if certificate files exist on the master server.Install_Path/netbackup/bin/goodies/nbkmiputil -validate -kmsServer kms_server_name -port 5696 -certPath certificate_file_path -privateKeyPath private_key__file_path -trustStorePath ca_file_path The output is in a JSON format. 
- Check if key is created on external KMS server with the required key group.
-         Check if at least one active key is listed using the following  command:Install_Path/bin/nbkmscmd -listKeys -name KMS_configuration_name -keyGroupName key_group_name If key is not listed, create a key with the required key group and clear the cache on the media server. Run the following command: Install_Path/bin/bpclntcmd -clear_host_cache 
- Check the following logs for further details:In case of tape, AdvanceDisk, and cloud storage: Install_Path/netbackup/logs/bptm In case of MSDP storage: PDDE_Install_Path/log/spoold/spoold.log For web service logs on the master server: Install_Path/logs/nbwebservice/<51216-495-***-***-***.log> For nbkmiputil logs for external KMS:Install_Path/netbackup/logs/nbkmiputil 
Use the following procedure to resolve the restore failure issue in case of a storage that is KMS enabled:
To resolve restore failure issue
- In case of tape, AdvanceDisk, and cloud storage, check job details.
- Validate the KMS configuration using the following commands:Install_Path/bin/nbkmscmd -validateKMSConfig -name KMS_configuration_name 
- Run the following command if certificate files exist on master server,    Install_Path/netbackup/bin/goodies/nbkmiputil -validate -kmsServer KMS_server_name -port 5696 -certPath certificate_file_path -privateKeyPath private_key__file_path -trustStorePath ca_file_pathThe output is displayed in the JSON format. 
- Ensure that the key with which backup is  encrypted is still active on the KMS server.See the following error in nbwebservice logs to get the key tag that is required for restore. See the following log statements in the web service logs on the master server: Install_path/logs/nbwebservice/<51216-495-***-***-***.log> Here are the log snippets: [Debug] NB 51216 nbwebapi 495 PID:10984 TID:149 File ID:495 [No context] 5 [com.netbackup.config.PeerInfoPopulatorFilter] Request URL : https://<Master-Server>:1556/netbackup/security/key-management-services/keys Connection Info :ConnectionInfo [Debug] NB 51216 nbwebapi 495 PID:10984 TID:149 File ID:495 [No context] 5 [com.netbackup.security.kms.resource.KMSConfigResource] HTTP GET filter query string is : KeyId eq 'bdc3492b015d4a9ab25426465b12adac6a834dfc6b4449c490922d6155719958' and kadlen eq 32 [Debug] NB 51216 nbwebapi 495 PID:10984 TID:149 File ID:495 [No context] 5 [com.netbackup.security.kms.resource.KMSConfigResource] com.netbackup.security.kms.resource.KMSConfigResource getKeys() - NBKMSRecordNotFoundException occured due to missing KMS record.com.netbackup.nbkms.exception.NBKMSRecordNotFoundException: security.error.kms.KeyRecordNotFound 
-      Check the following logs for further details:For tape, AdvanceDisk, and cloud storage: Install_Path/netbackup/logs/bptm For MSDP storage: PDDE_Install_Path/log/spoold/spoold.log For web service logs on master server: Install_Path/logs/nbwebservice/<51216-495-***-***-***.log> For nbkmiputil logs: - For NetBackup KMS,Install_Path/logs/nbkms 
- For external KMS,Install_Path/netbackup/logs/nbkmiputil