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
Output from the NetBackup support utility (nbsu)
By default, the nbsu command creates the output as a compressed file in the same directory where the nbsu executable is located. The format of the command output is:
NBSU_hostname_role_mmddyyyy_timestamp.extension
For example:
UNIX/Linux: NBSU_mylinuxvm_master_11072017_152100.tgz
Windows: NBSU_mywindowsvm_master_11072017_152100.cab
The NetBackup environment where nbsu runs determines the particular files that nbsu creates. nbsu runs only those diagnostic commands that are appropriate to the operating system and the NetBackup version and configuration. For each diagnostic command that it runs, nbsu writes the command output to a separate file. As a rule, the name of each output file reflects the command that nbsu ran to obtain the output. For example, nbsu created the NBU_bpplclients.txt by running the NetBackup bpplclients command and created the OS_set.txt file by running the operating system's set command.
Each output file begins with a header that identifies the commands that nbsu ran. If output from more than one command was included in the file, the header identifies the output as an "internal procedure."
The following is an example of part of the nbsu output file for the bpgetconfig command. The STDERR is shown as the output of the command and is captured in the output file. Exit status is outputted into the output file as follows: Exit status: <exit status code>
#######Command used: /usr/openv/netbackup/bin/admincmd/bpgetconfig -g sivbl17.domain.com -L####### Client/Master = Master NetBackup Client Platform = Linux, RedHat2.6.18 NetBackup Client Protocol Level = 8.1.0 Product = NetBackup Version Name = 8.1 Version Number = 810000 NetBackup Installation Path = /usr/openv/netbackup/bin Client OS/Release = Linux 3.10.0-229.el7.x86_64 Exit status: 0 #######Command used: /usr/openv/netbackup/bin/admincmd/bpgetconfig####### SERVER = sivbl17.domain.com WEB_SERVER_CONNECTION_TIMEOUT = 30 WEB_SERVER_TUNNEL_USE = AUTO WEB_SERVER_TUNNEL_ENABLED = YES WEB_SERVER_TUNNEL TRUSTED_MASTER KNOWN_MASTER MASTER_OF_MASTERS USEMAIL = BPBACKUP_POLICY = any BPBACKUP_SCHED = any Exit status: 0
If a supported archive program is available on the host where nbsu runs, nbsu bundles its output files into an archive file. If a supported compression utility is available, nbsu compresses the archive file. Otherwise, the individual output files remain unarchived and uncompressed.
An example of a compressed archive file that nbsu created is as follows:
/usr/openv/netbackup/bin/support/NBSU_host1_master_01172018_220505.tgz
where host1 is the name of the host on which nbsu ran, and master indicates that the host is a NetBackup master server. The date is embedded in the file name in the mmddyyyy format.
nbsu supports tar for archive and gzip for compression.
A complete description of nbsu is in the NetBackup Commands Reference Guide.