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
Fixed retention type for SLP operations
The Fixed retention indicates that the data on the storage is retained for the specified length of time, after which the backups or snapshots are expired.
An image copy with a Fixed retention is eligible for expiration when all of the following criteria are met:
The Fixed retention period for the copy has expired.
All child copies have been created.
All child copies that are mirror copies are eligible for expiration.
The Fixed retention period is always marked from the original backup time of the image. For example, if a tape device is down, causing a 2-day delay in creating a duplicate tape copy, the expiration time of the duplicate copy is not different due to the 2-day delay. The expiration time of the duplicate copy is still x days from the time that the original backup was completed. It does not matter when the copy was created.