Transitioning primary and secondary systems in a SnapMirror relationship in parallel
Contributors Download PDF of this page
You can transition the primary and secondary HA pairs that contain the volumes of a 7-Mode SnapMirror relationship in parallel. You must then manually set up the volume SnapMirror relationship in clustered Data ONTAP after transition. The SnapMirror relationship is retained after transition without requiring a rebaseline.
You must have prepared the source and destination clusters for transitioning the SnapMirror relationships.
You must transition both the secondary and primary HA pairs in the same cutover window.
From the 7-Mode Transition Tool, perform a copy-free transition of the two HA pairs that contain the primary and secondary volumes of the 7-Mode volume SnapMirror relationship.
Before transitioning the 7-Mode HA pair that contains the secondary volumes, no manual intervention is required for the 7-Mode SnapMirror relationships. This ensures that the 7-Mode secondary volumes are transitioned as read-only volumes to ONTAP.
Create an intercluster SVM peer relationship between the SVMs that contain the transitioned primary and secondary volumes.
Create a volume SnapMirror relationship between the transitioned primary and secondary volumes.
On the destination volume, resynchronize the source volume and destination volume of the SnapMirror relationship:
At least one common Snapshot copy must exist between the source and destination volumes.
Troubleshooting: SnapMirror resynchronization fails if the common Snapshot copy was created in a Data ONTAP release earlier than 8.1. You can use the
-fs-versionparameter with the
volume snapshot showcommand in the advanced privilege level to view the release in which the Snapshot copy was created. If you encounter this issue, break the SnapMirror relationship and then perform the resynchronization.
Monitor the status of the SnapMirror data transfers:
You must not perform any operation, such as volume move or SnapMirror break, on the source and destination volumes until the resynchronization is completed successfully. Ensure that the resynchronization does not get aborted and completes successfully; otherwise, the volumes can go to an inconsistent state.
Commit the transition of the secondary project, followed by the primary project.