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
- NetBackup secure communication logging
- NetBackup proxy helper logging
- NetBackup proxy tunnel logging
- Snapshot technologies
- Locating logs
- Java-based administration console logging
Automatic Image Replication (A.I.R.) process flow logging
For A.I.R. replications, only MSDP or OST disk-based storage units are used. The tape storage units and the advanced disk storage units cannot be used with A.I.R. The basic disk storage units are not supported with SLP.
The Automatic Image Replication (A.I.R.) process flow is as follows:
The SLP-controlled backup finishes. The backup image includes information about what SLP policy it will use for its secondary operation; for example, a replication or a duplication.
nbstserv on a regular interval (SLP parameter - Image Processing Interval) works to batch up images for the replication. The SLP manager (nbstserv) checks if the SLP window is open to submit replication jobs.
Next, nbstserv submits the batch to nbpem. nbpem passes the job to nbjm, which checks for resources from nbrb and nbemm. If the SLP window is open, nbpem passes the job to nbjm.
nbjm starts nbreplicate (nbreplicate appears in the admin log) and passes nbreplicate to bpdm.
bpdm makes the physical resource requests to nbjm.
The replication checks are run and the replication starts. bpdm lets the source storage server know when to initiate the replication. The source and target storage servers then communicate to perform the actual replication of data.
For replications, one bpdm process controls the operation.
A replication event is sent to the remote or target storage server.
The replication finishes and the image copy records are updated.