Skip to main content

Automatic unplanned failover not triggered on Site B

Contributors netapp-ahibbard netapp-lenida
PDFs
Issue:

A failure on Site A does not trigger an unplanned failover on Site B.

Possible cause #1:

The ONTAP Mediator is not configured. To determine if this is the cause, issue the snapmirror mediator show command on the Site B cluster.

Example:
Cluster2::*> snapmirror mediator show
This table is currently empty.

This example indicates that ONTAP Mediator is not configured on Site B.

Solution:

Ensure that ONTAP Mediator is configured on both clusters, that the status is connected, and quorum is set to True.

Possible cause #2:

SnapMirror consistency group is out of sync. To determine if this is the cause, view the event log to view if the consistency group was in sync during the time at which the Site A failure occurred.

Example:
cluster::*> event log show -event *out.of.sync*

Time                Node             Severity      Event
------------------- ---------------- ------------- ---------------------------
10/1/2020 23:26:12  sti42-vsim-ucs511w ERROR       sms.status.out.of.sync: Source volume "vs0:zrto_cg_556844_511u_RW1" and destination volume "vs1:zrto_cg_556881_511w_DP1" with relationship UUID "55ab7942-03e5-11eb-ba5a-005056a7dc14" is in "out-of-sync" status due to the following reason: "Transfer failed."
Solution:

Complete the following steps to perform a forced failover on Site B.

  1. Unmap all LUNs belonging to the consistency group from Site B.

  2. Delete the SnapMirror consistency group relationship using the force option.

  3. Enter the snapmirror break command on the consistency group constituent volumes to convert volumes from DP to R/W, to enable I/O from Site B.

  4. Boot up the Site A nodes to create a zero RTO relationship from Site B to Site A.

  5. Release the consistency group with relationship-info-only on Site A to retain common Snapshot copy and unmap the LUNs belonging to the consistency group.

  6. Convert volumes on Site A from R/W to DP by setting up a volume level relationship using either the Sync policy or Async policy.

  7. Issue the snapmirror resync to synchronize the relationships.

  8. Delete the SnapMirror relationships with the Sync policy on Site A.

  9. Release the SnapMirror relationships with Sync policy using relationship-info-only true on Site B.

  10. Create a consistency group relationship from Site B to Site A.

  11. Perform a consistency group resync from Site A, and then verify that the consistency group is in sync.

  12. Rescan host LUN I/O paths to restore all paths to the LUNs.