Veritas NetBackup™ Troubleshooting Guide
- Troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting vnetd proxy connections
- Troubleshooting security certificate revocation
- Verifying host name and service entries in NetBackup
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- Troubleshooting Auto Image Replication
- Using NetBackup utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the robotic test utilities
- Disaster recovery
- 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
- About recovering the NetBackup catalog
- About NetBackup catalog recovery and OpsCenter
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup relational database
Output from the NetBackup support utility (nbsu)
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:
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
nbsu supports tar for archive and gzip for compression.
A complete description of nbsu is in the NetBackup Commands Reference Guide.