ONTAP 9.14

to Japanese version

Protect with SnapMirror Business Continuity

Configuring protection using SnapMirror Business Continuity involves selecting LUNs on the ONTAP source cluster and adding them to a consistency group.

Before you begin
  • You must have a SnapMirror Synchronous license.

  • You must be a cluster or storage VM administrator.

  • All constituent volumes in a consistency group must be in a single storage VM (SVM).

    • LUNs can reside on different volumes.

  • The source and destination cluster cannot be the same.

  • You cannot establish SM-BC consistency group relationships across ASA clusters and non-ASA clusters.

  • The default IPspace is required by SM-BC for cluster peer relationships. Custom IPspace is not supported.

  • The name of the consistency group must be unique.

  • The volumes on the secondary (destination) cluster must be type DP.

  • The primary and the secondary SVMs must be in a peered relationship.


You can configure a consistency group using the ONTAP CLI or ONTAP System Manager.

Beginning in ONTAP 9.10.1, ONTAP offers a consistency group endpoint and menu in ONTAP System Manager, offering additional management utilities. If you are using ONTAP 9.10.1 or later, see Configure a consistency group then configure protection to create an SM-BC relationship.

ONTAP System Manager
  1. On the primary cluster, navigate to Protection > Overview > Protect for Business Continuity > Protect LUNs.

  2. Select the LUNs you want to protect and add them to a protection group.

  3. Select the destination cluster and SVM.

  4. Initialize relationship is selected by default. Click Save to begin protection.

  5. Go to Dashboard > Performance to verify IOPS activity for the LUNs.

  6. On the destination cluster, use ONTAP System Manager to verify that the protection for business continuity relationship is in sync: Protection > Relationships.

  1. Create a consistency group relationship from the destination cluster.
    destination::> snapmirror create -source-path source-path -destination-path destination-path -cg-item-mappings volume-paths -policy policy-name

    You can map up to 12 constituent volumes using the cg-item-mappings parameter on the snapmirror create command.

    The following example creates two consistency groups: cg_src on the source with vol1 and vol2 and a mirrored destination consistency group, cg_dst.

    destination::> snapmirror create -source-path vs1_src:/cg/cg_src -destination-path vs1_dst:/cg/cg_dst -cg-item-mappings vol_src1:@vol_dst1,vol_src2:@vol_dst2 -policy AutomatedFailOver

  2. From the destination cluster, initialize the consistency group.

    destination::>snapmirror initialize -destination-path destination-consistency-group

  3. Confirm that the initialization operation completed successfully. The status should be InSync.

    snapmirror show

  4. On each cluster, create an igroup so you can map LUNs to the initiator on the application host.
    lun igroup create -igroup name -protocol fcp|iscsi -ostype os -initiator initiator_name

  5. On each cluster, map LUNs to the igroup:

    lun map -path path_name -igroup igroup_name

  6. Verify the LUN mapping completed successfully with the lun map command. Then, you can discover the new LUNs on the application host.

Top of Page