Configuration variations for stretch MetroCluster configurations

Stretch MetroCluster configurations have asymmetrical and active/passive variations.

The following list describes some common configuration variations that are supported for stretch MetroCluster configurations:

  • Asymmetrical mirroring

    You can add storage to one or both nodes that is not mirrored by the other node.

    Attention: Any data contained in the unmirrored storage could be lost if that site experiences a disaster.
    Note: Multiple disk failures in an unmirrored aggregate (three or more disk failures in a RAID-DP aggregate, two or more disk failures in a RAID4 aggregate) or failure of a single array LUN in a RAID 0 aggregate cause the node to panic, resulting in a temporary data service outage while the node reboots, a takeover occurs, or disaster recovery is performed.

    You must mirror the root volumes to enable successful takeover.

    Note: You must connect the unmirrored storage to both nodes, just as for mirrored storage. You cannot have storage that is connected to only one node in an HA pair .
  • Active/passive MetroCluster configurations

    In this configuration, the remote (passive) node does not serve data unless it has taken over for the local (active) node. Mirroring the passive node’s root volume is optional. However, both nodes must have all licenses for a MetroCluster configuration installed so that remote takeover is possible.