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
- 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
- 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
- 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
- Index
Troubleshooting issues with the NetBackup Messaging Broker (or nbmqbroker) service
Do the following:
Ensure that the service is configured and started on the master server. To configure the service, run the configureMQ command.
Refer to the NetBackup Commands Reference Guide.
Reasons:
Ports that are configured for the service is in use by some other process.
The configuration file is corrupted.
Do the following:
Check the configureMQ command logs for failure.
Check the nbmqbroker service logs for failure.
Run the configureMQ command.
Refer to the NetBackup Commands Reference Guide.
Reasons:
The port configured for the service is not available for use.
Connection fails with some SSL exception.
The nbmqbroker service is not restarted after the configureWebServerCerts command is run on the master server.
Do the following:
Ensure that the port configured for the nbmqbroker service is available for use and accessible by NetBackup hosts.
Check the connectivity between the master server and the NAT client using the nbcertcmd -ping command.
If the command is not successfully executed, refer to the troubleshooting section for the NetBackup web service.
If the command is successfully executed, run configureMQ command to configure the nbmqbroker service.
Restart the nbmqbroker service.
Reasons:
The JSON web token (JWT) for the NAT client cannot be refreshed.
The security certificate of the NAT client is revoked.
The NetBackup Web Management Console (or nbwmc) service is not running.
Do the following:
Refer to the subscriber troubleshooting steps.
If the client's security certificate is revoked, reissue the certificate.
Start the nbwmc service.
Reasons:
The disaster recovery package is lost.
The configureMQ command is not run after the disaster recovery (DR) installation.
Do the following:
Run the configureMQ or configureMQ -defaultPorts command.
Refer to the NetBackup Commands Reference Guide.
To check if the installation root folder has the 8dot3 file name setting enabled, run the following command from your folder:
>dir /x
Example: The 'Program Files' directory has the 8dot3 file name setting enabled, therefore the short name 'PROGRA~1' is generated.
But it differs for the 'not8 Dot3' directory.
C:\>dir /x
The volume in drive C has no label.
The Volume Serial Number is FE21-2F8E
Directory of C:\
-5.6.3
12/06/2019 02:24 PM <DIR> not8 Dot3
12/02/2019 06:35 AM <DIR> PROGRA~1 Program Files
12/02/2019 10:44 AM <DIR> PROGRA~2 Program Files (x86)
Do the following to resolve the issue:
- Enable 8dot3 name file setting for the NetBackup installation root folder using the fsutil command.
Refer to the following article: Fsutil 8dot3name
- If the problem persists, contact Technical Support.