Table of ContentsView in Frames

Creating a data protection mirror copy for FlexVol volumes

You can protect data by replicating it to data protection mirror copies. You can use data protection mirror copies to recover data when a disaster occurs.

Before you begin

About this task

You can create data protection mirror copies in a cluster using FlexVol volumes only.

Steps

  1. Create a destination volume on the destination SVM that will become the data protection mirror copy by using the volume create command.
    Example
    The following command creates a data protection mirror volume named dept_eng_dr_mirror1 on SVM vs1.example.com. The destination volume is located on an aggregate named aggr3. The destination volume is also on SVM vs1.example.com.
    vs1::> vol create -volume dept_eng_dr_mirror1 -aggregate aggr3 -size 20MB -type DP
    If you are creating a data protection mirror copy on an SVM peer, the destination volume is created on the SVM peer:
    vs2::> volume create -volume dept_eng_dr_mirror1 
    -aggregate aggr3 -size 20MB -type DP
  2. Create a data protection mirror relationship by using the snapmirror create command.
    Example
    The following command creates a data protection relation with the destination volume named dept_eng_dp_mirror2 of the source volume named dept_eng. The SVM is named vs1.
    vs1::> snapmirror create -destination-path vs1.example.com:dept_eng_dp_mirror2 
    -source-path vs1.example.com:dept_eng -type DP -schedule 5min

    If you are creating the data protection mirror relationship with the destination volume on an SVM peer, you create the data protection mirror relationship from the SVM that contains the destination volume. For example, if the destination volume were on the SVM peer named vs2, the command to create the data protection mirror relationship is as follows:

    vs2::> snapmirror create -destination-path vs2.example.com:dept_eng_dp_mirror2 
    -source-path vs1.example.com:dept_eng -type DP -schedule 5min
    
    Data ONTAP creates the data protection mirror relationship, but the relationship is left in an uninitialized state.
  3. Initialize the data protection mirror copy by using the snapmirror initialize command.
    Example
    The following command initializes a data protection mirror copy named dept_eng_dp_mirror2 of a source volume named dept_eng. The source volume and the data protection mirror copy are on the same SVM named vs1.example.com.
    vs1::> snapmirror initialize -destination-path vs1.example.com:dept_eng_dp_mirror2

    If you are initializing the data protection mirror relationship with the destination volume on an SVM peer, you must initialize the data protection mirror relationship from the SVM that contains the destination volume. For example, if the destination volume of the single SVM example were on an SVM peer named vs2.example.com, the command to create the data protection mirror relationship is as follows:

    vs2::> snapmirror initialize -destination-path vs2.example.com:dept_eng_dp_mirror2