Creating the SnapMirror relationship (starting with ONTAP 9.3)

You must create a SnapMirror relationship between the source volume on one cluster and the destination volume on the peered cluster for replicating data for disaster recovery.

Before you begin

About this task

You must perform this task from the source cluster.

Steps

  1. Click Storage > Volumes.
  2. Select the volume for which you want to create a mirror relationship, and then click Actions > Protect.
  3. In the Relationship Type section, select Mirror from the Relationship Type drop-down list.
  4. In the Volumes: Protect Volumes page, provide the following information:
    1. Select Mirror as the relationship type.
    2. Select the destination cluster, destination SVM, and the suffix for the name of the destination volume.
      Only peered SVMs and allowed SVMs are listed under destination SVMs.
    3. Click .
    4. In the Advanced Options dialog box, verify that MirrorAllSnapshots is set as the protection policy.
      DPDefault and MirrorLatest are the other default protection policies that are available for SnapMirror relationships.
    5. Select a protection schedule.
      By default, the hourly schedule is selected.
    6. Verify that Yes is selected for initializing the SnapVault relationship.
      All of the data protection relationships are initialized by default. Initializing the SnapMirror relationship ensures that the destination volume has a baseline to start protecting the source volume.
    7. Click Apply to save the changes.


  5. Click Save to create the SnapMirror relationship.
  6. Verify that the relationship status of the SnapMirror relationship is in the Snapmirrored state.
    1. Navigate to the Volumes window, and then select the volume that the volume for which you created the SnapMirror relationship.
    2. Double-click the volume to view the volume details, and then click PROTECTION to view the data protection status of the volume.


After you finish

You must make a note of the settings for the source volume such as thin provisioning, deduplication, compression, and autogrow. You can use this information to verify the destination volume settings when you break the SnapMirror relationship.