Veritas NetBackup™ Replication Director Solutions Guide
- Introduction
- Additional configuration topics
- Creating a NetBackup storage server for snapshot replication
- Configuring disk pools for snapshot and replication
- About disk pools for snapshots and snapshot replication
- Using bpstsinfo to view the replication topology of a device
- Configuring storage units and storage unit groups for snapshots and snapshot replication
- Configuring storage lifecycle policies for snapshots and snapshot replication
- Operation types in a storage lifecycle policy
- Snapshot operation in an SLP
- Index From Snapshot operation in an SLP
- Snapshot operation in an SLP
- Retention types for storage lifecycle policy operations
- Configuring backup policies for snapshots and snapshot replication
- About NDMP support for Replication Director
- Restoring from a snapshot
- About restores from array-based snapshots of virtual machines
- OpsCenter reporting
- Using NetApp disk arrays with Replication Director
- Supported NetApp topologies
- Using NetApp Data ONTAP 7-mode with Replication Director
- About using NetApp SAN-connected storage with Replication Director
- Using NetApp Clustered Data ONTAP with Replication Director
- Using Oracle with Replication Director
- Using Virtual Machines with Replication Director
- Terminology
Expire after copy retention type for SLP operations
The Expire after copy retention indicates that after all direct (child) copies of an image are successfully duplicated to other storage, the data on this storage is expired. The last operation in the SLP cannot use the Expire after copy retention type because no subsequent copy is configured. Therefore, an operation with this retention type must have a child.
Veritas recommends that you not enable Expire after copy retention for any storage units that are to be used with SLPs with either of the following: Accelerator or synthetic backups. The Expire after copy retention can cause images to expire while the backup runs. To synthesize a new full backup, the SLP backup needs the previous backup image. If the previous image expires during the backup, the backup fails.
Note:
If a policy is configured to use an SLP for the backup, the retention that is indicated in the SLP is the value that is used. The Retention attribute in the schedule is not used.
An image copy with an Expire after copy retention is expired as soon as all of its direct child copies have been successfully created. Any mirrored children must also be eligible for expiration.