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
Directory names for legacy debug logs for servers
NetBackup creates certain directories for legacy logging for servers. Each directory corresponds to a process. Unless it is noted, each directory should be created under the following directory.
Windows | install_path\NetBackup\logs |
UNIX | /usr/openv/netbackup/logs |
On UNIX systems, also refer to the README file in the /usr/openv/netbackup/logs directory.
Table: Directory names for legacy debug logs describes the directories you need to create to support legacy debug logs for servers.
Table: Directory names for legacy debug logs
Directory | Associated process |
|---|---|
admin | Administrative commands |
bpbrm | NetBackup backup and restore manager |
bpcd | NetBackup client daemon or manager. The NetBackup Client service starts this process. |
bpjobd | NetBackup jobs database manager program |
bpdm | NetBackup disk manager |
bpdbm | NetBackup Database Manager. This process runs only on primary servers. On Windows systems, it is the NetBackup Database Manager service. |
bpjava-msvc | The NetBackup Java application server authentication service that is started when the NetBackup interface applications start. On UNIX servers, inetd starts it. On Windows servers, the Client Services service starts it. This program authenticates the user that started the application. |
bpjava-susvc | The NetBackup program that bpjava-msvc starts upon successful logon through the logon dialog box that is presented when a NetBackup interface starts. This program services all requests from the Java user interfaces on the NetBackup primary or media server host where the bpjava-msvc program runs (all Windows platforms). |
bprd | NetBackup Request Daemon. On Windows systems, this process is called the NetBackup Request Manager service. |
bpsynth | The NetBackup process for synthetic backup. nbjm starts bpsynth. bpsynth runs on the primary server. |
bptm | NetBackup tape management process |
nbatd | Authentication daemon (UNIX and Linux) or service (Windows). nbatd authenticates access to interfaces of NetBackup services or daemons. |
nbazd | Authorization daemon (UNIX and Linux) or service (Windows). nbazd authorizes access to interfaces of NetBackup services or daemons. |
syslogs | System log You must enable system logging to troubleshoot ltid or robotic software. See the syslogd man page. |
user_ops | The user_ops directory is created during the install of NetBackup on all servers and clients. NetBackup interface programs use it for the following: temporary files and for job and progress log files that the Backup, Archive, and Restore program (jbpSA) generates. This directory must exist for successful operation of any of the Java programs and must have public read, write, and execute permissions. user_ops contains a directory for every user that uses the Java programs. The NetBackup Java interface log files are written in the nbjlogs subdirectory. All files in the user_ops directory hierarchy are removed according to the setting of the KEEP_LOGS_DAYS configuration option. |
vnetd | The Veritas network daemon, used to create firewall-friendly socket connections. Started by the inetd(1M) process. Note: Logging occurs in either the /usr/openv/logs directory or the /usr/openv/netbackup/logs if the vnetd directory exists there. If the vnetd directory exists in both locations, logging occurs only in /usr/openv/netbackup/logs/vnetd. |