Transitioning HA pairs in a SnapMirror relationship in a staggered configuration

You can transition the secondary HA pair first, set up a staggered SnapMirror relationship between the 7-Mode primary volumes and ONTAP secondary volumes, and then transition the primary HA pair later.

Before you begin

You must have prepared the source and destination clusters for transitioning the SnapMirror relationships.

Preparing the cluster for transitioning volume SnapMirror relationships

Procedure

  1. From the 7-Mode Transition Tool, perform a copy-free transition of the HA pair that contain the secondary volumes of the 7-Mode volume SnapMirror relationships.
    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.

    Transitioning 7-Mode aggregates using copy-free transition

  2. During the precommit testing phase of the secondary HA pair, create a disaster recovery relationship between the 7-Mode primary volume and ONTAP secondary volume:
    1. From the secondary destination cluster, use the vserver peer transition create command to create an SVM peer relationship between the 7-Mode primary volume and the ONTAP secondary volume.
    2. Use the job schedule cron create command to create a job schedule that matches the schedule configured for the 7-Mode SnapMirror relationship.
    3. Use the snapmirror create command to create a SnapMirror relationship of type TDP between the 7-Mode primary volume and the ONTAP secondary volume.
    4. Use the snapmirror resync command to resynchronize the ONTAP secondary volume.
      For successful resynchronization, a common 7-Mode Snapshot copy must exist between the 7-Mode primary volume and the ONTAP secondary volume.
  3. Perform the required testing of the transitioned aggregates and volumes.
  4. From the 7-Mode Transition Tool, commit the transition of the project for the secondary HA pair.
  5. Perform a copy-free transition of the HA pair that contains the primary volumes of the 7-Mode volume SnapMirror relationships.
  6. During the precommit testing phase of the primary HA pair, create a SnapMirror relationship between the transitioned secondary and primary volumes.
    1. From the destination cluster, create an intercluster SVM peer relationship between the SVMs that contain the transitioned primary and secondary volumes.
    2. Use the snapmirror delete command to delete the TDP SnapMirror relationship between the 7-Mode primary volume and the ONTAP secondary volume that was created in Step 2.c.
    3. Optional: Delete the cron job schedule that was created in Step 2.b: job schedule cron delete
    4. Create a volume SnapMirror relationship between the transitioned primary and secondary volumes.
    5. On the destination volume, resynchronize the source volume and destination volume of the SnapMirror relationship: snapmirror resync
      Important: 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-version parameter with the volume snapshot show command in the advanced privilege level to view the release in which the Snapshot copy is created. If this issue occurs, break the SnapMirror relationship and then perform the resynchronization.
    6. Monitor the status of the SnapMirror data transfers: snapmirror show
      Important: 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.
  7. Commit the transition of the primary project.