Requirements for a MetroCluster configuration with array LUNs

There are some unique requirements for setting up a MetroCluster configuration with array LUNs.

The Interoperability Matrix at support.netapp.com contains the latest policies for MetroCluster configurations that use array LUNs. It includes information about supported storage arrays, switches, and Data ONTAP systems (V-Series systems and FAS systems) that are supported for use with array LUNs. The Interoperability Matrix is the final authority for information about requirements and restrictions for MetroCluster configurations that use array LUNs.

Requirements for Data ONTAP systems using array LUNs in a MetroCluster configuration

  • The platform must be identified in the Interoperability Matrix as supported for MetroCluster configurations.
    • Prior to Data ONTAP 8.2.1, only V-Series systems (not FAS systems) can be deployed in a MetroCluster configuration that uses array LUNs.
    • Starting in Data ONTAP 8.2.1, V-Series systems and FAS systems that can be licensed to use array LUNs can be deployed in a MetroCluster.
  • The Data ONTAP systems in the MetroCluster configuration must be all V-Series systems or all FAS systems, and both nodes must be the same model.
  • A system with two controllers in the same enclosure, such as a 32xx system, requires an FC-VI adapter.

    TheHardware Universe contains information about adapter requirements for different models.

In releases prior to Data ONTAP 8.2, MetroCluster configurations with V-Series systems could not use native disks. Starting in Data ONTAP 8.2, a MetroCluster configuration with V-Series systems can include native disks, storage arrays, or both.

Note: Connecting a single FC initiator port to multiple storage array target ports is not supported in a MetroCluster configuration. This functionality is supported for non MetroCluster configurations starting in Data ONTAP 8.2, as described in the FlexArray Virtualization Installation Requirements and Reference Guide.

Requirements for storage arrays

  • The storage arrays must be identified in the Interoperability Matrix as supported for MetroCluster configurations.
  • The storage arrays in the MetroCluster configuration must be symmetric, which means the following:
    • The two storage arrays must be in the same vendor family.

      The FlexArray Virtualization Implementation Guide for Third-Party Storage contains details about storage array families.

    • A pool of array LUNs for the mirrored storage must be created on each of the two storage arrays.

      The array LUNs must be the same size.

    • Disk types (SATA, SSD, or SAS) used for mirrored storage must be the same on both storage arrays.
    • Storage arrays that provide tiered configurations (for example, Hitachi) must use the same tiered topology on each side of the MetroCluster configuration.
    • The root volume must be mirrored for successful takeover to occur.

Requirements for FC switches

  • The switches and switch firmware must be identified in the Interoperability Matrix as supported for MetroCluster configurations.
  • Each fabric must have two switches.
  • Each Data ONTAP system must be connected to storage using redundant components so that there is redundancy in case of device failure.

The Interoperability Matrix contains the latest information about switch requirements and supported switches. The configuration and firmware requirements for switches in a MetroCluster environment might differ from those in other configurations.

Zoning requirements

  • Single-initiator to single-target zoning is recommended.

    Single-initiator to single-target zoning limits each zone to a single FC initiator port. It also improves discovery and boot time because the FC initiators on the Data ONTAP systems do not attempt to discover each other.

  • FC-VI ports on the FC adapters must be zoned end-to-end across the fabric.

    The Interoperability Matrix contains specific guidelines for FC-VI.

Requirements for ISLs

Data ONTAP supports using one or two ISLs, depending on the configuration. The Interoperability Matrix contains information about the number of ISLs for specific configurations.

For specific information about Traffic Isolation zoning for FC-VI traffic and for information about ISL encryption, see the Brocade's Zoning Feature section in the Fabric-attached MetroCluster Systems Brocade Switch Configuration Guide on the NetApp Support Site at support.netapp.com. Regular zoning guidelines apply for Data ONTAP systems and storage arrays.

SyncMirror requirements

  • SyncMirror is required for a MetroCluster configuration.

    Licenses are no longer required for SyncMirror. You need to enable SyncMirror with the cf.mode and cf.remote_syncmirror.enable options.

  • Two separate storage arrays are required for the mirrored storage.
    Note: Using two different storage arrays for mirroring is optional in configurations that are not MetroCluster configurations.
  • Two sets of LUNs are required—one set for the aggregate on the local storage array (pool0) and another set at the remote storage array for the mirror of the aggregate (the other plex of the aggregate, pool1).

The Data ONTAP Data Protection Online Backup and Recovery Guide for 7-Mode provides more details about setting up SyncMirror for a MetroCluster configuration that uses array LUNs.