NetBackup™ Logging Reference Guide
- Using logs
- About logging
- Logging levels
- Log retention and log size
- Changing the logging levels
- About unified logging
- Gathering unified logs for NetBackup
- Types of unified logging messages
- File name format for unified logging
- Originator IDs for the entities that use unified logging
- About changing the location of unified log files
- About rolling over unified log files
- About recycling unified log files
- About using the vxlogview command to view unified logs
- Examples of using vxlogview to view unified logs
- Examples of using vxlogmgr to manage unified logs
- Examples of using vxlogcfg to configure unified logs
- Accessibility of the unified logs
- About legacy logging
- UNIX client processes that use legacy logging
- PC client processes that use legacy logging
- File name format for legacy logging
- Directory names for legacy debug logs for servers
- Directory names for legacy debug logs for media and device management
- How to control the amount of information written to legacy logging files
- Limit the size and retention of legacy logs
- Accessibility of the legacy logs
- Setting retention limits for logs on clients
- UNIX logging with syslogd
- Logging options with the Windows Event Viewer
- Backup process and logging
- Media and device processes and logging
- Restore process and logging
- Advanced backup and restore features
- Storage logging
- NetBackup Deduplication logging
- OpenStorage Technology (OST) logging
- Storage lifecycle policy (SLP) and Auto Image Replication (A.I.R.) logging
- NetBackup secure communication logging
- About NetBackup secure communication logging
- Tomcat logging
- NetBackup web services logging
- Command-line logging
- NetBackup cURL logging
- Java logging
- Embeddable Authentication Client (EAT) logging
- Authentication Services (AT) logging
- vssat logging
- NetBackup proxy helper logging
- NetBackup proxy tunnel logging
- PBX logging
- Sending secure communication logs to Veritas Technical Support
- Snapshot technologies
- Locating logs
- Overview of NetBackup log locations and processes
- acsssi logging
- bpbackup logging
- bpbkar logging
- bpbrm logging
- bpcd logging
- bpcompatd logging
- bpdbm logging
- bpjobd logging
- bprd logging
- bprestore logging
- bptestnetconn logging
- bptm logging
- daemon logging
- ltid logging
- nbemm logging
- nbjm logging
- nbpem logging
- nbproxy logging
- nbrb logging
- NetBackup Vault logging
- NetBackup web services logging
- NetBackup web server certificate logging
- PBX logging
- reqlib logging
- Robots logging
- tar logging
- txxd and txxcd logging
- vnetd logging
- NetBackup Administration Console logging
- NetBackup Administration Console logging process flow
- Enabling detailed debug logging for the NetBackup Administration Console
- Setting up a secure channel between the NetBackup Administration Console and bpjava-*
- Setting up a secure channel between the NetBackup Administration Console and either nbsl or nbvault
- NetBackup Administration Console logging configuration on NetBackup servers and clients
- Logging Java operations for the NetBackup Remote Administration Console
- Configuring and gathering logs when troubleshooting NetBackup Administration Console issues
- Undo logging
- Using the Logging Assistant
About the Logging Assistant
The Logging Assistant is a helpful tool that can shorten the time that is required to set up and collect debug logs and other information. Because Logging Assistant automatically performs a number of functions, you can avoid the problems that are associated with manually logging into NetBackup hosts, creating log directories, and changing logging levels.
Note:
Use the Logging Assistant under the guidance of Veritas Support.
The Logging Assistant uses a series of wizards to help quickly troubleshoot a problem. Depending on the category of NetBackup problem, the tool suggests the possible hosts that may be involved in the problem and the logs that should be enabled on those hosts.
Note:
While collecting NetBackup logs using Logging Assistant, the total NetBackup log size may increase. If you have enabled the property on the dialog box and the total NetBackup log size reaches its high water mark, logs are deleted. Logs that you want to retain may also be deleted. To avoid the deletion of logs that you want to retain, you need to disable the property while you collect logs using the Logging Assistant. Alternatively, you can set the property to a value higher than the current value, so that the important logs are not deleted before the log collection is complete.
No special licensing is required. However, you must have root permissions for UNIX and administrator privileges for Windows to use the Logging Assistant.
Table: Logging Assistant operations shows a summary of the main Logging Assistant operations.
Table: Logging Assistant operations
Operation | Description |
|---|---|
Add a new Logging Assistant record. | Add a Logging Assistant record that you use throughout the process of troubleshooting a NetBackup problem. Typically, you associate the record that you create with a failed job that appears in the Activity Monitor. A list of records appears when you select the Logging Assistant node in the right pane of the NetBackup Administration Console. |
View details. | View the details for the selected record. |
Delete a Logging Assistant record. | After the failed job runs successfully, you can delete the Logging Assistant record. |
Enable debug logging. | Use the Setup Debug Logging Wizard to enable selected NetBackup debug logs and other processes that Technical Support uses to troubleshoot NetBackup problems. Logging Assistant automatically creates the necessary log folders and sets the log levels of the debug logs to the highest verbosity. (The highest log level of many of the debug logs is 5). |
Set minimum debug logging. | Use the Set Minimum Debug Logging Wizard to set the specified process log levels (verbosity) to a minimum value. This setting still allows info, warning, error, and critical messages (legacy logging), and application logs, diagnostic logs, and some debug logs (unified logging). You may want to set the debug logging to minimum values after you resolve the job failure problem for the selected Logging Assistant record. |
Disable debug logging. | Use the Disable Debug Logging Wizard to disable the debug logging after you resolve the job failure problem for the selected Logging Assistant record. The only logs that NetBackup continues to generate are application logs and diagnostic logs. |
Collect nbsu output. | Use the Collect nbsu Output Wizard to gather the nbsu diagnostic information onto the primary server. |
Cancel operation. | After you complete collection, you can cancel the operation if it is currently in progress (for example, if the data is too large and the operation is time-consuming). Check that the progress field of this record displays In progress, then right-click the Logging Assistant record and select Cancel Operation. |