Creating a vault relationship from a source SVM

You can use System Manager to create a vault relationship from the source storage virtual machine (SVM), and to assign a vault policy to the vault relationship to create a backup vault. In the event of data loss or corruption on a system, backed-up data can be restored from the backup vault destination.

Before you begin

The SnapVault license or SnapMirror license must be enabled on both the source cluster and the destination cluster.
Note:
- For some platforms, it is not mandatory for the source cluster to have the SnapVault license or the SnapMirror license enabled if the destination cluster has the SnapVault license or the SnapMirror license, and DPO license enabled.
- After the DPO license is enabled on the destination cluster, you must refresh the browser of the source cluster to enable the Protect option.
The source cluster and destination cluster, and the source SVM and destination SVM must be in a healthy peer relationship.
The destination aggregate must have space available.
The source aggregate and the destination aggregate must be 64-bit aggregates.
A vault (XDP) policy must exist.
If a vault policy does not exist, you must create a vault policy or accept the default vault policy (named XDPDefault) that is automatically assigned.
FlexVol volumes must be online and read/write.
The SnapLock aggregate type must be the same.
A maximum of 25 volumes can be protected in one selection.
If you are connecting from a cluster running ONTAP 9.2 or earlier to a remote cluster on which Security Assertion Markup Language (SAML) authentication is enabled, password-based authentication must be enabled on the remote cluster.

About this task

System Manager does not support a cascade relationship.
For example, a destination volume in a relationship cannot be the source volume in another relationship.
You can create a lock-vault relationship only between a non-SnapLock (primary) volume and a Snaplock destination (secondary) volume.
If encryption is enabled on the source volume and the destination cluster is running a version of ONTAP software earlier than ONTAP 9.3, then encryption is disabled on the destination volume by default.

Steps

Click Storage > Volumes.
From the Volumes on SVM list, select All SVMs.
Select the volumes for which you want to create vault relationships, and then click More Actions > Protect.
The Protect option is available only for a read/write volume.
Select Vault from the Volume relationship Type list.
Specify the cluster and the SVM, and then enter a name suffix for the destination volume.
If the specified cluster is running a version of ONTAP software earlier than ONTAP 9.3, then only peered SVMs are listed. If the specified cluster is running ONTAP 9.3 or later, peered SVMs and permitted SVMs are listed.
Optional: Click , update the protection policy and protection schedule, enable SnapLock properties on the destination volume, select a FabricPool-enabled aggregate, and then initialize the protection relationship.
Click Save.