Performing a failback when source volume still exists

You can resynchronize the original source volume and fail back using the NetApp Element UI. This procedure applies to scenarios where the original source volume still exists.

Steps

  1. In the Element UI, find the relationship that you broke to perform the failover.
  2. Click the Actions icon and click Reverse Resync.
  3. Confirm the action.
    Note: The Reverse Resync operation creates a new relationship in which the roles of the original source and destination volumes are reversed (this results in two relationships as the original relationship persists). Any new data from the original destination volume is transferred to the original source volume as part of the reverse resync operation. You can continue to access and write data to the active volume on the destination side, but you will need to disconnect all hosts to the source volume and perform a SnapMirror update before redirecting back to the original primary.
  4. Click the Actions icon of the inverse relationship that you just created and click Update.

    Now that you have completed the reverse resync and ensured that there are no active sessions connected to the volume on the destination side and that the latest data is on the original primary volume, you can perform the following steps to complete the failback and reactivate the original primary volume:

  5. Click the Actions icon of the inverse relationship and click Break.
  6. Click the Actions icon of the original relationship and click Resync.
    Note: The original primary volume can now be mounted to resume production workloads on the original primary volume. The original SnapMirror replication resumes based on the policy and schedule configured for the relationship.
  7. After you confirm that the original relationship status is "snapmirrored", click the Actions icon of the inverse relationship and click Delete.