Creating a mirror and vault relationship from a destination SVM
You can use Storage Manager to create a mirror and vault relationship from the destination storage virtual machine (SVM) . Creating this relationship enables you to better protect your data by periodically transferring data from the source volume to the destination volume. It also enables you to retain data for long periods by creating backups of the source volume.
Before you begin
The destination cluster must be running ONTAP 8.3.2 or later.
SnapMirror license must be enabled on the source cluster and destination cluster.
NoteFor some platforms, it is not mandatory for the source cluster to have the SnapMirror license enabled if the destination cluster has the SnapMirror license enabled.The source cluster and destination cluster must be in a healthy peer relationship.
The destination SVM must have space available.
The source aggregate and destination aggregate must be 64-bit aggregates.
A source volume of type read/write (rw) must already exist.
The SnapLock aggregate type must be the same.
If you are connecting from a cluster running ONTAP 9.2 or earlier to a remote cluster on which SAML authentication is enabled, password-based authentication must be enabled on the remote cluster.
About this task
- Storage Manager does not support a cascade relationship.
For example, a destination volume in a relationship cannot be the source volume in another relationship.
You cannot create a mirror and vault relationship between a sync-source SVM and a sync-destination SVM in a MetroCluster configuration.
You can create a mirror and vault relationship between sync-source SVMs in a MetroCluster configuration.
You can create a mirror and vault relationship from a volume on a sync-source SVM to a volume of a data-serving SVM.
You can create a mirror and vault relationship from a volume on a data-serving SVM to a DP volume on a sync-source SVM.
A maximum of 25 volumes can be protected in one selection.