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
NDMP backup logging
The following shows an NDMP backup process.
The basic processing steps for an NDMP backup operation are the following:
- The NetBackup administrator runs the bpbackup command to start the backup job. Or, a scheduled policy that is created on the NetBackup Administration Console can initiate the job.
- The bpbackup process connects to the master server and creates the backup request. The NetBackup Request Manager (bprd) sends the backup request to the Policy Execution Manager (nbpem), who submits the job to the Job Manager (nbjm).
- nbjm requests resources from the Resource Broker (nbrb) that are required to run the job. nbrb accesses the Media and Device Selection (MDS) of the Enterprise Media Management (nbemm) to evaluate the resources request. MDS queries the EMM database to identify the resources to use for this job.
- MDS provides nbrb with a list of resources for the job, and nbrb passes it on to nbjm.
- nbjm initiates communication with the media server that is associated with this backup job. It goes through the client service (bpcd) to start the Backup and Restore Manager (bpbrm) on the media server.
- bpbrm starts the Tape Manager (bptm) on the media server. Eventually, the parent bptm process makes a request to ltid to mount the tape to be used for the backup job.
- On the NetBackup for NDMP server, one of the following occurs: sends the necessary NDMP SCSI robotic commands to mount the requested tape on the storage device.
The NDMP agent service (ndmpagent) connects to the filer that issues the NDMP commands to mount the tape that is directly attached.
ltid on the media server issues the necessary NDMP SCSI robotic commands to mount the requested tape on the storage device.
- One of the following occurs, depending on the type of NDMP backup:
Local backup. NetBackup sends the NDMP commands to have the NDMP server application perform the backup to tape. The data travels between the local disk and the tape drives on the NDMP host without crossing the LAN.
Three-way backup (not shown in the process flow diagram). NetBackup sends NDMP commands to the NDMP server application to perform the backup. The media server establishes NDMP communications with both NDMP servers. The data travels over the network from the NDMP server that houses the data to be backed up to the NDMP server that writes the backup to its tape storage.
Remote backup (not shown in the process flow diagram). The device that is used to write the backup is associated with a NetBackup storage unit. bptm on the NetBackup media server mounts a tape on a tape drive. NetBackup sends the NDMP commands to the NDMP server to initiate the backup to the non-NDMP media manager storage unit. The data travels over the network from the NDMP host to the NetBackup media server, which writes the data to the selected storage unit.
- Throughout the backup operation and at its completion, the NDMP server sends status about the backup operation to the NetBackup for NDMP server. Several NetBackup processes send information about the job to bpjobd, that uses this information to update the job status that you can view in the NetBackup Activity Monitor.
Status, catalog, and other job information movement is shown in dashed lines in the process flow diagram.