Create an SVM disaster recovery relationship for FlexGroup volumes
Suggest changes
PDFs
Beginning with ONTAP 9.9.1, you can create SVM disaster recovery (SVM DR) relationships using FlexGroup volumes. An SVM DR relationship provides redundancy and the ability to recover FlexGroups in the event of a disaster by synchronizing and replicating the SVM configuration and its data. A SnapMirror license is required for SVM DR.
You cannot create a FlexGroup SVM DR relationship with the following applies.
-
A FlexClone FlexGroup configuration exists
-
The FlexGroup volume is part of a cascading relationship
-
The FlexGroup volume is part of a fanout relationship, and your cluster is running an ONTAP version earlier than ONTAP 9.12.1. (Beginning with ONTAP 9.13.1, fanout relationships are supported.)
-
All nodes in both clusters must be running the same ONTAP version as the node on which SVM DR support was added (ONTAP 9.9.1 or later).
-
The SVM DR relationship between the primary and secondary sites should be healthy and should have enough space on both the primary and secondary SVMs to support the FlexGroup volumes.
-
Beginning with ONTAP 9.12.1, FabricPool, FlexGroup, and SVM DR can work in conjunction. In releases earlier than ONTAP 9.12.1, any two of these features worked together, but not all three in conjunction.
-
When you create a FlexGroup SVM DR relationship in which the FlexGroup volume is part of a fanout relationship, you should be aware of the following requirements:
-
The source and destination cluster must be running ONTAP 9.13.1 or later.
-
SVM DR with FlexGroup volumes supports SnapMirror fanout relationships to eight sites.
-
For information about creating an SVM DR relationship, see Manage SnapMirror SVM replication.
-
Create an SVM DR relationship, or use an existing relationship.
-
Create a FlexGroup volume on the primary site with the required number of constituents.
Wait until FlexGroup and all of its constituents are created before proceeding.
-
To replicate the FlexGroup volume, update the SVM at the secondary site:
snapmirror update -destination-path destination_svm_name: -source-path source_svm_name:You can also check if a scheduled SnapMirror update already exists by entering
snapmirror show -fields schedule -
From the secondary site, verify that the SnapMirror relationship is healthy:
snapmirror showcluster2::> snapmirror show Progress Source Destination Mirror Relationship Total Last Path Type Path State Status Progress Healthy Updated ----------- ---- ------------ ------- -------------- --------- ------- -------- vs1: XDP vs1_dst: Snapmirrored Idle - true - -
From the secondary site, verify that the new FlexGroup volume and its constituents exist:
snapmirror show -expandcluster2::> snapmirror show -expand Progress Source Destination Mirror Relationship Total Last Path Type Path State Status Progress Healthy Updated ----------- ---- ------------ ------- -------------- --------- ------- -------- vs1: XDP vs1_dst: Snapmirrored Idle - true - vs1:fg_src XDP vs1_dst:fg_src Snapmirrored Idle - true - vs1:fg_src__0001 XDP vs1_dst:fg_src__0001 Snapmirrored Idle - true - vs1:fg_src__0002 XDP vs1_dst:fg_src__0002 Snapmirrored Idle - true - vs1:fg_src__0003 XDP vs1_dst:fg_src__0003 Snapmirrored Idle - true - vs1:fg_src__0004 XDP vs1_dst:fg_src__0004 Snapmirrored Idle - true - 6 entries were displayed.