There are several prerequisites that you should consider as part of planning a SnapMirror Business Continuity solution deployment.


  • Only two-node HA clusters are supported

  • Both clusters must be either AFF or ASA (no mixing)


  • ONTAP 9.8 or later

  • ONTAP Mediator 1.2 or later

  • A Linux server or virtual machine for the ONTAP Mediator running one of the following:

Mediator version

Supported Linux versions


Red Hat Enterprise Linux: 7.6, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3

CentOS: 7.6, 7.7, 7.8, 7.9


Red Hat Enterprise Linux: 7.6, 7.7, 7.8, 8.0, 8.1

CentOS: 7.6, 7.7, 7.8


  • SnapMirror synchronous (SM-S) license must be applied on both clusters

  • SnapMirror license must be applied on both clusters

    Note If your ONTAP storage systems were purchased before June 2019, click NetApp ONTAP Master License Keys to get the required SM-S license.

Networking environment

  • Inter-cluster latency round trip time (RTT) must be less than 10 milliseconds

Supported protocols

  • Only SAN protocols are supported (not NFS/CIFS)

  • Only Fibre Channel and iSCSI protocols are supported

  • The default IPspace is required by SM-BC for cluster peer relationships. Custom IPspace is not supported.

ONTAP Mediator

Read-write destination volumes

  • SM-BC relationships are not supported on read-write destination volumes. Before you can use a read-write volume, you must convert it to a DP volume by creating a volume-level SnapMirror relationship and then deleting the relationship. For details, see Converting existing relationships to SM-BC relationships

Large LUNs and large volumes

  • Large LUNs and large volumes greater than 100TB are supported only on All SAN Arrays

Note You must ensure that both the primary and secondary cluster are All SAN Arrays, and that they both have ONTAP 9.8 installed. If the secondary cluster is running a version earlier than ONTAP 9.8 or if it is not an All SAN Array, the synchronous relationship can go out of sync if the primary volume grows larger than 100 TB.