Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Logging Reference Guide
  3. Storage lifecycle policy (SLP) and Auto Image Replication (A.I.R.) logging
  4. Automatic Image Replication (A.I.R.) process flow logging
Veritas NetBackup™ Logging Reference Guide

Automatic Image Replication (A.I.R.) process flow logging

The following figure shows the Automatic Image Replication (A.I.R.) process flow.

Figure: Automatic Image Replication (A.I.R.) process flow

Automatic Image Replication (A.I.R.) process flow

Note:

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:

  1. 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.

  2. 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.

  3. 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.

  4. nbjm starts nbreplicate (nbreplicate appears in the admin log) and passes nbreplicate to bpdm.

  5. bpdm makes the physical resource requests to nbjm.

  6. 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.

    Note:

    For replications, one bpdm process controls the operation.

  7. A replication event is sent to the remote or target storage server.

  8. The replication finishes and the image copy records are updated.

Feedback

Was this page helpful?
Previous

Storage lifecycle policy (SLP) duplication process flow

Next

Import process flow

Feedback

Was this page helpful?