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
UNIX client restore
Before you start a restore, use the bplist program on the client to do the following: browse the file catalog to list the files available in the backup images, and select the desired files. You can start bplist directly from the command line, and the NetBackup user interface programs can use it.
To retrieve the file list, bplist sends a query to the request daemon (bprd) on the master server (see Figure: List operation - UNIX client). The request daemon then queries bpdbm for the information and transmits it to bplist on the client.
The following are the processing steps in a restore (in the order presented):
When the user starts a restore, NetBackup invokes the client's bprestore program which sends a request to the request daemon, bprd. This request identifies the files and client. The request daemon then uses bpcd (client daemon) to start the backup and restore manager (bpbrm).
Note:
To restore Backup Exec images, bpbrm initiates mtfrd instead of nbtar on the clients. The server processes are the same as those used for NetBackup restores.
If the disk device or tape device on which the data resides attaches to the master server, the following occurs: bprd starts the backup and restore manager on the master server. If the disk unit or tape unit connects to a media server, bprd starts the backup and restore manager on the media server.
The backup and restore manager starts bptm and uses the client daemon (bpcd) to establish a connection between NetBackup nbtar on the client and bptm on the server.
For tape: The bptm process identifies which media is needed for the restore, based on the image catalog. bptm then requests the allocation of the required media from nbrb through nbjm. nbjm then asks mds (part of nbemm)for the resources. nbemm allocates the media and selects and allocates an appropriate drive (for tape media).
bptm asks ltid to mount the tape in the drive.
For disk: bptm does not need to ask nbrb for an allocation, because disk inherently supports concurrent access. bptm uses the file path in a read request to the system disk manager.
bptm directs the image to the client in one of two ways. If the server restores itself (server and client are on the same host), nbtar reads the data directly from shared memory. If the server restores a client that resides on a different host, it creates a child bptm process which transmits the data to nbtar on the client.
Note:
Only the part of the image that is required to satisfy the restore request is sent to the client, not necessarily the entire backup image.
The NetBackup nbtar program writes the data on the client disk.
Note:
PBX must be running for NetBackup to operate (PBX is not shown in the next diagram). See the NetBackup Troubleshooting Guide for more information on how to resolve PBX problems.