Veritas NetBackup™ Logging Reference Guide
- Using logs
- About unified logging
- About legacy logging
- About global logging levels
- 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
- Java-based administration console logging
Snapshot backup and Windows open file backups
Figure: Snapshot backup and Windows open file backup using multiple data streams shows the overall snapshot backup process. PBX (not shown in the diagram) must be running for NetBackup to operate.
A separate parent job creates all snapshots, then a child job backs up the snapshot.
The NetBackup master server or primary client initiates the backup. This action causes the NetBackup request daemon bprd to submit a backup request to the Policy Execution Manager nbpem. nbpem processes the policy configurations.
When bpfis is finished, it sends snapshot information and completion status to bpbrm and exits. bpbrm, in turn, reports the snapshot information and status to nbjm and exits. nbjm relays the information and status to nbpem.
nbpem submits a child job for the backup to nbjm, with a file list derived from the snapshot information. nbjm starts bpbrm to back up the snapshot.
bpbrm starts the process bptm (parent) on the media server.
The next step depends on the following: Whether the media server backs up itself (bptm and bpbkar on the same host), or the media server backs up a client on a different host. If the media server backs up itself, bpbkar stores the snapshot-based image block by block in shared memory on the media server. If the media server backs up a client that resides on a different host, bptm on the server creates a child process of itself. The child receives the snapshot-based image from the client by means of socket communications and then stores the image block-by-block in shared memory.
The original bptm process then takes the backup image from shared memory and sends it to the storage device (disk or tape).
Information is available on how the tape request is issued.
See "Media and device management process" in the NetBackup Troubleshooting Guide.
bptm sends backup completion status to bpbrm, which passes it to nbjm.
When nbpem receives backup completion status from nbjm, nbpem tells nbjm to delete the snapshot. nbjm starts a new instance of bpbrm on the media server, and bpbrm starts a new instance of bpfis on the client. bpfis deletes the snapshot on the client, unless the snapshot is of the Instant Recovery type, in which case it is not automatically deleted. bpfis and bpbrm report their status and exit.
For more information, see the NetBackup Snapshot Client Administrator's Guide.
Note that Windows open file backups do not require Snapshot Client.