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
Restore process
Understanding how the restore process works is a helpful first step in deciding which logs to gather for a particular issue. The restore process differs depending on whether you restore an image from tape or from disk.
Figure: Restore from tape process flow illustrates a restore from tape.
Restore procedure from tape
- The (1) NetBackup Request Daemon (bprd) receives a restore request. This request can be initiated from the Backup, Archive, and Restore user interface or from the (2) command line (bprestore).
- The bprd process launches two child processes: MAIN bprd and MPX-MAIN-bprd. The MAIN bprd process is used to identify images and media, while the MPX-MAIN-bprd process manages the restore operation. For simplicity's sake, these three processes are all referred to here as bprd.
- The bprd service communicates with the (3) NetBackup Database Manager program (bpdbm) to get the information that is required to restore the files that have been requested.
- Once it has the information it needs, bprd communicates with (4) bpjobd, and the job is added to the job list in the jobs database. The job is now visible in the Activity Monitor. It may show as "Active" even before resources are acquired.
- The bprd service goes through Private Branch Exchange (PBX) and the NetBackup Legacy Network (vnetd) to start the (5) NetBackup backup and restore manager (bpbrm).
- The bpbrm service starts the (6) tape management process (bptm) and provides the media information that is required for the restore. It also starts the (7) Tape Archive program (tar) on the client (through PBX and vnetd) and creates a connection between tar and bptm.
- The bptm process sends a resource request to the (8) NetBackup Job Manager (nbjm) through PBX and vnetd.
- The nbjm process sends the resource request to the (9) NetBackup Resource Broker (nbrb), which queries the (10) Enterprise Media Manager (nbemm). Once the resources have been allocated, nbrb notifies nbjm, which notifies bptm.
- The bptm process makes a mount request to the (11) logical tape interface daemon (ltid). The ltid service calls on the (12) robotic drive daemon (txxd, where xx varies based on the type of robot being used). The txxd daemon communicates the mount request to the (13) robotic control daemon (txxcd), which mounts the media.
- The bptm process reads the data to be restored from the media and delivers it to tar.
- The tar process writes the data to the client disk.
- When the restore is completed, bptm unmounts the media and notifies nbjm. The job now appears as "Done" in the Activity Monitor.
Some additional logs that are not included in the restore process flows but that can be of use in resolving restore problems include: reqlib, daemon, robots, and acsssi.
Figure: Restore from disk process flow illustrates a restore from disk.
Restore procedure from disk
- The (1) NetBackup Request Daemon (bprd) receives a restore request. This request can be initiated from the Backup, Archive, and Restore user interface or from the (2) command line (bprestore).
- The bprd service communicates with the (3) NetBackup Database Manager program (bpdbm) to get the information that is required to restore the files that have been requested.
- The bprd process initiates a (4) child bprd process. The child bprd process makes a call to the (5) Enterprise Media Manager (nbemm) to verify that the disk storage unit is available.
- The child bprd process communicates with (6) bpjobd to allocate a jobid. The restore job is now visible in the Activity Monitor.
- The bprd process starts the (7) NetBackup backup and restore manager (bpbrm) on the media server, through Private Branch Exchange (PBX) and the NetBackup Legacy Network Service (vnetd).
- The bpbrm service uses PBX and vnetd to establish a connection with the (8) Tape Archive program (tar) on the client system. It also starts the (9) tape management process (bptm).
- The bptm process makes a call to bpdbm (through PBX and vnetd) to get the fragment information and then mounts the disk.
- The bptm process reads the backup image from the disk and streams the requested data to tar.
- The tar process commits the data to the storage destination.
Each of the processes that is involved in a restore has an accompanying log file. These logs can be consulted to diagnose any issues that you encounter with your restore.