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
- About 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
About the nbcplogs utility
When you troubleshoot a problem, you must gather and copy the correct logs to debug the issue. The log types (legacy, vxul, vm, pbx,...) may be in many places. The process of getting the logs to Veritas technical support can be difficult and time consuming.
By default, nbcplogs now runs the nbsu utility and collects nbsu information for the host system. This capability saves time and keystrokes in gathering information. The utility also gathers additional log information for clusters and pack history information.
If you have a case ID provided by 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:
This utility supports the following types of search algorithms as options on the nbcplogs command.
--filecopy. File copy is the default condition. It copies the entire log file. File copy with compression is usually enough to get the job done.
--fast. Fast search uses a binary search to strip out the lines that are outside the time frame of the file. This mechanism is useful for copying large log files such as bpdbm. This option is seldom needed and should be used with caution.
The default condition is the file copy, which copies the entire log file. A fast search algorithm uses a binary search to strip out the lines that are outside the time frame of the file. This mechanism is useful for copying large log files such as bpdbm.
The nbcplogs utility is intended to simplify the process of copying logs by specifying the following options:
A time frame for the logs.
The log types that you want to collect.
Bundling and in-transit data compression.
In addition, you can preview the amount of log data to be copied.