Veritas NetBackup™ Logging Reference Guide
- Using logs
- About logs
- About UNIX system logs
- About log retention in NetBackup
- About limiting the size of unified and legacy logs
- 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
- About query strings used with the vxlogview command
- Examples of using vxlogview to view unified logs
- Examples of using vxlogmgr to manage unified logs
- Examples of using vxlogcfg to configure 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
- About limiting the size and the retention of legacy logs
- Configuring the legacy log rotation
- About global logging levels
- Setting retention limits for logs on clients
- Logging options with the Windows Event Viewer
- Troubleshooting error messages in the NetBackup Administration Console
- 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
- 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 web services logging
- NetBackup web server certificate logging
- PBX logging
- reqlib logging
- robots logging
- tar logging
- txxd and txxcd logging
- vnetd logging
- Java-based administration console logging
- About the Java-based administration console logging
- Java-based administration console logging process flow
- Setting up a secure channel between the Java-based administration console and bpjava-*
- Setting up a secure channel between the Java-based administration console and either nbsl or nbvault
- Java-based administration console logging configuration on NetBackup servers and clients
- Java-based remote administration console logging on a Windows computer where NetBackup is not installed
- Configuring and gathering logs when troubleshooting Java GUI issues
- Undo logging
About NetBackup secure communication logging
This section provides information about the logs that are used for secure communication logging with the NetBackup hosts. The NetBackup 8.1 and later hosts will securely communicate with each other for all control-type functions. The control-type functions include command execution and the starting of various processes that are required to initiate a backup or restore. Currently, this does not include the bpbkar or tar data transfer. The NetBackup 8.1 and later hosts must have a Certificate Authority (CA) certificate and a host ID-based certificate for successful communication. NetBackup uses the Transport Layer Security (TLS) protocol for host communication where each host needs to present its security certificate and validate the peer host's certificate against the Certificate Authority (CA) certificate.
In NetBackup 8.0 and later versions, the master server acts as the CA. The master server depends on the correct installation and configuration of services, such as pbx, nbatd and nbwmc, to deploy the certificates.
In NetBackup 8.1, all of the media and client servers have certificates deployed to them when they are upgraded. If the certificate deployment fails, the media or client server cannot run the backups or restores. Backups and restores will not function if the host did not successfully retrieve both the CA certificate and host ID-based certificate from the master server during the installation or upgrade to NetBackup version 8.1 or later. If the master server pbx, nbatd, or nbwmc processes are not running, the certificate deployment will not function. In NetBackup 8.1 and later, the backups or restores also will not function.
When you diagnose issues with secure communication and the certificate generation and deployment, the services or processes that run on the master server are typically involved. After verifying that the services are running and are at the expected NetBackup version, the log files described in this section are critical to help determine the issue.
For more details about NetBackup secure communications, see the Read This First for Secure Communications document at the following URL:
https://www.veritas.com/docs/DOC5332
Note:
If you have NetBackup 8.0 or earlier hosts in your environment, you can enable insecure communication by navigating to the NetBackup Administration Console, then to the tab. On this tab, select the option.