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
- 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
NDMP restore logging
The basic processing steps for an NDMP restore operation are as follows:
- An administrator at the NetBackup Administration Console on a NetBackup master server or media server initiates a restore job by browsing the images catalog and by selecting the files to be restored from the NDMP images. This process is similar to selecting files to be restored from standard backup images. The NetBackup master server identifies the specific media that is required to perform the restore. In this diagram, the media is a tape volume.
- After the master server identifies the data to be restored and the media required, it submits a restore job. The Job Manager (nbjm) then requests the required resources. This resource request causes the allocation of the media that contains the data to be restored. In this example, a tape drive is used during the restore operation.
- The master server contacts the media server that participates in the restore job, and starts the Restore Manager (bpbrm) process to manage the restore job. bpbrm starts the Tape Manager process (bptm), that queries nbjm for the tape volume. Then, bptm requests that the logical tape interface daemon (ltid) mounts the tape.
- On the NetBackup for NDMP server, the NDMP agent (ndmpagent) connects to the filer and issues NDMP commands to mount the tape that is directly attached, and ltid sends NDMP commands to mount the requested tape on the storage device. Or, the media server itself issues tape mount requests much like a regular media manager storage unit.
- One of the following occurs, depending on the type of NDMP restore operation:
Local restore. NetBackup sends the NDMP commands to the NDMP server to initiate the restore operation from a tape drive to a local disk. The restore data travels from a tape drive to a local disk on the NDMP host without traversing the LAN.
Three-way restore. The NetBackup media server establishes NDMP communications with both of the NDMP servers that are involved in the restore. To initiate the restore of data from tape on one NDMP server to disk storage on the other NDMP server, the media server sends NDMP commands to both NDMP servers. The restore data travels over the network between the NDMP hosts.
Remote restore. NetBackup sends the NDMP commands to the NDMP server to prepare the server for the restore. bptm on the media server reads the restore data from tape and sends it over the network to the NDMP host where the data is written to disk storage.
- The NDMP server sends status information about the restore operation to the NetBackup for NDMP server. Various NetBackup processes (nbjm, bpbrm, bptm, and others) send job status information to the master server. The Jobs Database Manager (bpjobd) process on the master server updates the restore job status in the jobs database. You can view this status in the Activity Monitor.