About retention mapping overview

Retention mapping lets you assign a retention level to a duplicate image that is based on the retention level of the original image. For example, if the retention of an original image is two weeks, you can configure the mapping so that the duplicate image that is transferred off-site has a retention level of seven years.

You configure retention mappings in the following places:

By default, each retention level maps to itself (that is, retention level 0 maps to 0, 1 maps to 1, and so on).

To use the retention mappings, you must specify Use Mappings for the retention level during duplication. You can specify normal retention calculation for some duplication rules and alternative retention mappings for other duplication rules. Vault uses the retention mappings in specific-to-global order. If vault-specific retention mappings do not exist, Vault uses the global retention mappings.

The retention level for a duplicate image is based on the retention level of the primary backup image. The retention period begins on the date the primary backup image was created, not on the date the duplicate image was created.

If the backup policy that created the primary backup image no longer exists, duplication of that image fails and the job continues but reports a status 306 (vault duplication partially succeeded).

Retention mapping applies to duplication only; it does not apply if you vault original NetBackup images.