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
- Creating disk pools for snapshot replication
- Updating disk pools after volumes are added, are deleted, or are changed
- Updating an OpenStorage disk pool to reflect plug-in updates
- How to resolve snapshot disk volume changes
- 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
- About configuring storage lifecycle policies for snapshots and snapshot replication
- Creating a storage lifecycle policy for snapshots and snapshot replication
- Operation types in a storage lifecycle policy
- Snapshot operation in an SLP
- Primary snapshot storage unit
- Primary + Replication source snapshot storage unit
- Replication source + Replication target snapshot storage unit
- Replication target snapshot storage unit
- Replication source + Replication target + Mirror snapshot storage unit
- Replication target + Mirror snapshot storage unit
- Replication operation in an SLP
- Index From Snapshot operation in an SLP
- Backup From Snapshot operation in an SLP
- Duplication 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 configuring a backup policy for Replication Director
- Configuring an NDMP policy to protect a NAS host
- Configuring a Standard or MS-Windows policy to protect clients using NDMP with Data Mover
- Configuring a Standard or MS-Windows policy to protect NAS volumes or SAN-connected devices
- About NDMP support for Replication Director
- Restoring from a snapshot
- About restores from array-based snapshots
- Restoring files and folders from an array-based snapshot
- About restores from array-based snapshots of virtual machines
- Using OpsCenter to restore from array-based snapshots
- How NetApp performs a volume-level rollback restore
- Restoring (rolling back) from an array-based snapshot
- OpsCenter reporting
- Using NetApp disk arrays with Replication Director
- Using NetApp disk arrays with Replication Director
- Supported NetApp topologies
- Using NetApp Data ONTAP 7-mode with Replication Director
- Configuration overview: NetApp 7-Mode with Replication Director
- Licenses required for NetApp Data ONTAP 7-Mode with Replication Director
- Software required to use NetApp Data ONTAP 7-Mode with Replication Director
- About using NetApp SAN-connected storage with Replication Director
- If the OnCommand Unified Manager root or administrator password has changed
- Considerations when configuring an OnCommand Unified Manager as a NetBackup storage server
- Importing existing NetApp relationships for NetBackup control
- Enabling Unicode and language settings on NetApp disk arrays
- Using NetApp Clustered Data ONTAP with Replication Director
- Configuration overview: NetApp Clustered Data ONTAP with Replication Director
- Licenses required for NetApp Clustered Data ONTAP with Replication Director
- Software required to use NetApp Clustered Data ONTAP with Replication Director
- Configuring Replication Director to work with Clustered Data ONTAP
- About creating backup policies for Clustered Data ONTAP with Replication Director
- Protecting volumes with nested junctions for Clustered Data ONTAP
- Limitations to using Clustered Data ONTAP with Replication Director
- Using Oracle with Replication Director
- Using Virtual Machines with Replication Director
- Terminology
- Index
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.
It is not recommended that you 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.