Failures that do not require disaster recovery

There are some failures that do not require any disaster recovery such as, a failure of the interconnect, failure of cables and so on. If you can reestablish the MetroCluster connection after fixing the problem, you should not perform the disaster recovery procedure.

You should not perform the disaster recovery procedure for the following failures:

  • A failure of the HA interconnect between the two sites, which can be caused by the following:
    • Failure of the interconnect cable
    • Failure of one of the FC-VI adapters
    • If using switches, a failure of the SFP connecting a node to the switch

    With this type of failure, both nodes remain running. Automatic takeover is disabled because Data ONTAP cannot synchronize the NVRAM logs. After you fix the problem and reestablish the connection, the nodes resynchronize their NVRAM logs and the MetroCluster configuration returns to normal operation.

  • The storage from one site (site A) is not accessible to the node at the other site (site B), which can be caused by the following:
    • Failure of any of the cables connecting the storage at one site to the node at the other site or switch
    • If using switches, failure of any of the SFPs connecting the storage to the switch or the node to the switch
    • Failure of the Fibre Channel adapter on the node
    • Failure of a storage disk shelf (disk shelf module; power; access to disk shelves; and so on)

    With this type of failure, you see a mailbox disk invalid message on the console of the storage system that cannot see the storage. After you fix the problem and reestablish the connection, the MetroCluster configuration returns to normal operation.

  • If you are using switches, the inter-switch link between each pair of switches fails.

    With this type of failure, both nodes remain running. You see a mailbox disk invalid message because a storage system at one site cannot see the storage system at the other site. You also see a message because the two nodes cannot communicate with each other. After you fix the problem and reestablish the connection, the nodes resynchronize their NVRAM logs and the MetroCluster configuration returns to normal operation.

  • If you are using FibreBridge 6500N bridge, a failure of the FibreBridge 6500N bridge.