Skip to main content

Creating a mirror relationship from a destination SVM

You can use ONTAP Storage Manager to create a mirror relationship from the destination storage virtual machine (SVM) and to assign a policy and schedule to the mirror relationship. The mirror copy enables quick availability of data if the data on the source volume is corrupted or lost.

Before you begin

  • The source cluster must be running ONTAP 9.4 or later.

  • The SnapMirror license must be enabled on the source cluster and destination cluster.

    Note
    For some platforms, it is not mandatory for the source cluster to have the SnapMirror license enabled if the destination cluster has the SnapMirror license and Data Protection Optimization (DPO) license enabled.

  • While mirroring a volume, if you select a SnapLock volume as the source, then the SnapMirror license and SnapLock license must be installed on the destination cluster.

  • The source cluster and destination cluster must be in a healthy peer relationship.

  • The destination SVM must have space available.

  • A source volume of type read/write (rw) must exist.

  • The FlexVol volumes must be online and must be of type read/write.

  • The SnapLock aggregate type must be of the same type.

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 relationship between a sync-source SVM and a sync-destination SVM in a MetroCluster configuration.

  • You can create a mirror relationship between sync-source SVMs in a MetroCluster configuration.

  • You can create a mirror relationship from a volume on a sync-source SVM to a volume on a data-serving SVM.

  • You can create a mirror relationship from a volume on a data-serving SVM to a data protection (DP) volume on a sync-source SVM.

  • You can create a mirror relationship between SnapLock volumes of the same type only.

    For example, if the source volume is a SnapLock Enterprise volume, then the destination volume must also be a SnapLock Enterprise volume. You must ensure that the destination SVM has aggregates of the same SnapLock type available.

  • The destination volume that is created for a mirror relationship is not thin provisioned.

  • A maximum of 25 volumes can be protected in one selection.

  • You cannot create a mirror relationship between SnapLock volumes if the destination cluster is running a version of ONTAP that is older than the ONTAP version that the source cluster is running.

  1. Click Protection > Relationships.
  2. Click Protect > Volumes.
  3. In the Source area, select the cluster to use, the SVM to mirror, and the source volume.
  4. In the Destination Settings, specify the destination SVM.

    You can also change the volume source and destination name if required.

  5. Click Save.

Result

If you chose to create a destination volume, a destination volume of type dp is created, with the language attribute set to match the language attribute of the source volume.

A mirror relationship is created between the source volume and the destination volume. The base Snapshot copy is transferred to the destination volume if you have opted to initialize the relationship.

Related reference