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 NetBackup jobs that are enabled for data-in-transit encryption
The given NetBackup job can be of type backup, restore, duplication, replication, import, verify and so on. The job is enabled for data-in-transit encryption (DTE) through the global DTE setting or the client DTE mode.
For more details on DTE, see the NetBackup Security and Encryption Guide.
The given operation can be backup, restore, import, verify, duplication, synthetic backup ans so on. The failure is in determining the DTE mode for the given operation. This is due to failure in fetching the global DTE mode as it is not refreshed in the bpcd process.
The following error is seen in bpcd:
The global data-in-transit encryption setting cannot be fetched (8304).
Table: Logs to be checked
Operation | Logs |
|---|---|
Backup or archive | Primary server - nbjm, bpcd, nbwebservice |
Restore | Primary server - admin (catalog recovery), bprd, bpcd, nbwebservice |
Duplication, verify, synthetic backup, replication | Primary server - admin, bpcd, nbwebservice |
Import | Primary server - admin, bpcd, nbwebservice Media server - bpdm or bptm |
Logs for UNIX:
Legacy logs: /usr/openv/netbackup/logs
VxUL logs: /usr/openv/logs
Logs for Windows: install_path\NetBackup\logs
The NetBackup web service took more time to restart as a result of which the global DTE cache of bpcd is not refreshed. It results into a failure of the given operation while determining the DTE mode.
Retry the operation after 2 minutes of the service restart so that the global DTE mode is successfully refreshed by the web service in the next iteration.
The failure is during determining the DTE mode for the given operation. This is because the media server DTE mode cannot be retrieved.
Table: Logs to be checked
Operation | Logs |
|---|---|
Backup or archive | Primary Server - nbjm, nbemm |
Restore | Primary Server - bprd, nbemm |
Duplication, verify, synthetic backup, replication | Primary Server - admin, nbemm |
Import | Primary Server - admin, nbemm Media Server - bpdm or bptm |
Logs for UNIX:
Legacy logs: /usr/openv/netbackup/logs
VxUL logs: /usr/openv/logs
Logs for Windows: install_path\NetBackup\logs
Failure in retrieving the media server DTE setting from EMM, resulting in failure of the operation.
Retry the operation to successfully retrieve the media server DTE mode.
Table: Logs to be checked
Operation | Logs |
|---|---|
Backup or archive | Client - bpbkar or dbclient, vnetd, bpclntcmd Media server - bptm, bpclntcmd, vnetd |
Restore | Client - tar or dbclient, vnetd, bpclntcmd Media server - bpbrm, bptm, bpclntcmd, vnetd |
Duplication | Both media servers - bptm or bpdm, vnetd, bpclntcmd |
Logs for UNIX: /usr/openv/netbackup/logs
Logs for Windows: install_path\NetBackup\logs
There is a failure while retrieving the pre-shared key that is required for TLS handshake between hosts. This is because of either of the following issues in bpclntcmd such as:
storing the pre-shared key in bpclntcmd failed
bpclntcmd failed to provide the pre-shared key
As a result of this issue, multiple NetBackup operations such as backup, restore or duplication fail.
Stop the existing bpclntcmd -store process and retry the operation.
Table: Logs to be checked
Operation | Logs |
|---|---|
Duplication | Target media server - bptm or bpdm, vnetd |
Logs for UNIX: /usr/openv/netbackup/logs
Logs for Windows: install_path\NetBackup\logs
Error in job details:
Jan 19, 2022 8:49:36 PM - Error bpdm (pid=18607) cannot connect to the writing side process for duplication, Success Jan 19, 2022 9:37:02 PM - Error bptm (pid=1028) listen protocol error - couldn't accept from data socket, The operation completed successfully. Jan 19, 2022 9:37:03 PM - Info bptm (pid=1028) EXITING with status 25 <----------
When data-in-transit encryption (DTE) is enabled, vnetd process is responsible for setting up the pre-requisites required for DTE TLS handshake. On a busy machine, if vnetd spends more time doing this, bptm times out before vnetd forwards the connection. As a result of this, duplication fails.
On the target host, increase the timeout for accepting connection from vnetd. Use the nbgetconfig and nbsetconfig commands to increase the timeout of the VNET_OPTIONS configuration option.
For example, to change the timeout from 120 seconds to 300 run the following commands:
nbgetconfig VNET_OPTIONS VNET_OPTIONS = 120 3600 200 40 3 1 30 10 1793 32 0 0
nbsetconfig nbsetconfig> VNET_OPTIONS = 300 3600 200 40 3 1 30 10 1793 32 0 0
Only the first value is changed to '300'.