The MetroCluster configuration consists of a disaster recovery (DR) group that includes two HA pairs, each in a separate cluster at physically separated sites. FC switches and long distance Inter-Switch Links (ISLs) provide a backbone connection between the clusters. The clusters are also in a peering relationship, with each cluster's configuration information mirrored to the partner.
The storage controllers are not connected directly to the storage but connect to two redundant FC switch fabrics.
The FC-to-SAS bridges connect the SAS storage stacks to the FC switches, providing bridging between the two protocols.
The FC switches provide the long haul backbone ISL between the two sites. The switches provide the two storage fabrics that allow data mirroring to the remote storage pools.
The cluster peering network provides connectivity for mirroring of Storage Virtual Machine (SVM) configuration information. The configuration of all SVMs on one cluster is mirrored to the partner cluster.
The following illustration shows a simplified view of the MetroCluster configuration. For some connections, a single line represents multiple, redundant connections between the components. Data and management network connections are not shown.
Additional storage stacks are supported, but only one is shown at each site.
A switched configuration is supported but not shown.
The following illustration shows a more detailed view of the connectivity in a single MetroCluster cluster (both clusters have the same configuration):
The configuration includes the following connections:
If the controllers support a single-chassis HA pair, the HA interconnect is internal, occurring through the backplane, meaning an external interconnect is not required.
SVM configuration is replicated over the cluster peering network.
If the controllers are configured as a switched cluster, each controller would connect to two cluster interconnect switches.