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
- Snapshot technologies
- Locating logs
- acsssi logging
- bpbackup logging
- bpbkar logging
- bpbrm logging
- bpcd logging
- bpcompatd logging
- bpdbm logging
- bpjobd logging
- bprd logging
- bprestore 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
Backup process
Understanding how the backup process works is a helpful first step in deciding which processes to review for troubleshooting purposes.
Figure: Basic backup process flow illustrates the backup procedure and the process flow during a scheduled backup.
- The (1) NetBackup Policy Execution Manager (nbpem) initiates a backup when the job becomes due. To determine when the job is due, nbpem uses the proxy service nbproxy to get the backup policy information from the (2) NetBackup Database Manager (bpdbm).
In the case of a user-initiated backup, the backup is started when nbpem receives a request from the (3) NetBackup request daemon (bprd).
- When the job is due, nbpem issues a request to the (4) NetBackup Job Manager (nbjm) to submit the backup and get a jobid.
- The nbjm service communicates with (5) bpjobd, and the job is added to the job list in the jobs database. The job is now visible in the Activity Monitor, in a queued state.
- Once the job has been added to the jobs database, nbjm checks for resources through the (6) NetBackup Resource Broker (nbrb).
- The nbrb process secures the required resources from the (7) Enterprise Media Manager (nbemm) and notifies nbjm that resources have been allocated.
- After resource allocation, nbjm makes a call to the images database to create the image files in a temporary location. The required entries in the backup header tables are also created at this time. The job is now seen as "Active" in the Activity Monitor.
- Once the job is active, nbjm uses (8) bpcompatd to open a connection to the (9) client service (bpcd) on the media server. The bpcompatd service creates the connection through Private Branch Exchange (PBX) and the NetBackup Legacy Network Service (vnetd).
- The bpcd service starts the (10) NetBackup backup and restore manager (bpbrm).
- The bpbrm service communicates with (11) bpcd on the client server (through PBX and vnetd) to start the (12) backup and archive manager (bpbkar). The bpbrm service also starts the (13) tape management process (bptm).
- In the case of a tape backup, bptm reserves the drives and issues a mount request to the (14) logical tape interface daemon (ltid). The ltid service calls on the (15) robotic drive daemon (txxd, where xx varies based on the type of robot being used). The txxd daemon communicates the mount request to the (16) robotic control daemon (txxcd), which mounts the media.
In the case of a disk backup, bptm communicates directly with the disk.
- The bpbkar service sends the backup data through bptm to be written to the media storage or the disk storage.
- When the backup is completed, nbjm is notified and sends a message to bpjobd. The job now appears as "Done" in the Activity Monitor. The nbjm service also reports the job exit status to nbpem, which recalculates the next due time of the job.
Each of the processes that is involved in a backup has an accompanying log file. These logs can be consulted to diagnose any issues that you encounter with your backups.
Some additional logs that are not included in the backup process flow but that can be of use in resolving backup problems include: bpbackup, reqlib, daemon, robots, and acsssi.