SnapVault is often used to protect a volume SnapMirror
destination. You can perform SnapVault transfers from
the volume SnapMirror destination when you want to retain the data for a longer time.
In this deployment scenario, data from various primary storage systems are replicated to a remote site for disaster recovery purpose. Volume SnapMirror
ensures identical data at the source and destination storage systems. If long-term retention (that is, 90 days and more) is required at the disaster recovery
site, you can use SnapVault
to back up data from the SnapMirror
destination.
When using
SnapVault
to back up a
SnapMirror destination volume or qtree, ensure the following:
- SnapMirror
primary has a SnapMirror
license installed. SnapMirror
destination (and SnapVault
primary) have both SnapMirror
and SnapVault
primary licenses installed. SnapVault
secondary has SnapVault
secondary license installed.
- The SnapVault
operation occurs between SnapMirror scheduled updates. Otherwise, SnapMirror updates fail if a SnapVault
operation is in progress or initiated.
You configure only the schedule on the SnapVault secondary
storage system.
SnapVault
source
selects the most recent
Snapshot copy
of the volume
SnapMirror
as the
Snapshot copy
to transfer
(similar to a volume
SnapMirror
cascade). You cannot specify a
Snapshot copy as a source
Snapshot copy
for
SnapVault
transfer when the
SnapVault
source volume is a
SnapMirror destination volume. Here,
Data ONTAP uses the
SnapMirror-generated
Snapshot copy as the
SnapVault
baseline
Snapshot copy.
For more information about long-term backup of primary or disaster recovery data, see the SnapMirror Async Overview and Best Practices Guide.
