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
About the NetBackup support utility (nbsu)
The NetBackup support utility (nbsu) is a command line tool. It queries the host and gathers appropriate diagnostic information about NetBackup and the operating system. nbsu provides a wide range of control over the types of diagnostic information gathered. For instance, you can obtain information about NetBackup configuration settings, about specific troubleshooting areas, or about NetBackup or media management job status codes.
The NetBackup support utility (nbsu) resides in the following location:
Note:
The NetBackup support utility (nbsu) has been updated in NetBackup 8.1.1. The previous version of nbsu (renamed old_nbsu) is deprecated and will be removed in a future NetBackup release. Veritas recommends use of the newer version (nbsu).
Veritas recommends that you run the NetBackup support utility (nbsu) in the following circumstances:
To obtain baseline data on your NetBackup installation. If you encounter problems later, this data can be useful.
To document changes in your NetBackup or operating system environment. Run nbsu periodically to keep your baseline data up to date.
To help isolate a NetBackup or operating system issue.
To report issues to Veritas technical support.
The following suggestions can help you run the nbsu utility more effectively:
For a complete description of nbsu including examples and how to gather diagnostic information to send to Veritas Technical Support, see the NetBackup Commands Reference Guide.
If you have a case ID from Technical Support of the form
########, rename the log files with the case ID number. Then manually upload the files to the Veritas Evidence Server. For additional assistance, see:For troubleshooting, run nbsu when the system is in the same state as when the problem occurred. For example, do not stop and restart the NetBackup processes after the error occurs or make a change to the server or network. If you do, nbsu may not be able to gather key information about the problem.
If a NetBackup component is not operational (for example, bpgetconfig does not return information), nbsu may be unable to properly report on the system. For these cases, use the -g command line option to collect only OS and NET commands.
If nbsu does not perform as expected, try the following:
By default, nbsu sends error messages to standard error (STDERR) and also includes the messages in its output files. Note the following alternate ways to view nbsu error messages:
To redirect the nbsu error messages to standard output (STDOUT)
Enter the following:
Windows
install_path\NetBackup\bin\support\nbsu.exe 2>&1
UNIX
/usr/openv/netbackup/bin/support/nbsu 2>&1
To send all nbsu screen output including error messages to a file
Enter the following:
nbsu 2>&1 > file_name
Where 2>&1 directs standard error into standard output, and file_name directs standard output into the designated file.
To generate the debug messages that relate to nbsu, enter the following:
# nbsu -debug
The messages are written to the STDOUT.
The nbsu_info.txt file provides an overview of the environment where nbsu is run. It contains the following:
The general flow of the nbsu program
A list of diagnostics that were run
A list of diagnostics that returned a non-zero status
The information in nbsu_info.txt may indicate why nbsu returned particular values, or why it did not run certain commands.
If nbsu does not produce adequate information or if it seems to perform incorrectly, run nbsu with the -debug option. This option includes additional debug messages in the nbsu_info.txt file.
A complete description of nbsu is in the NetBackup Commands Reference Guide.