Table of ContentsView in Frames

Requirements for creating relationships between clusters or SVMs

Before you create a SnapMirror or SnapVault relationship between volumes in different clusters or Storage Virtual Machines (SVMs), you should ensure that the relationship follows the supported configurations.

Relationships between volumes in different clusters

Before you can create a relationship between volumes in different clusters, there must be a cluster peer relationship established between the two clusters and an SVM peer relationship established between the two SVMs.

SnapMirror relationships between clusters running different versions of Data ONTAP

The Data ONTAP versions supported depend on the relationship type and policy defined for that SnapMirror relationship.

For SnapMirror relationships using type DP and policy async-mirror, a relationship can be built from an earlier Data ONTAP release to a one that is no more than two releases later. The following relationships are permitted:

If the source volume is located on a system running Data ONTAP… The destination volume can reside on a system running one of the following releases…
  8.0.x 8.1.x 8.2.x 8.3.x
8.0.x yes yes yes no
8.1.x no yes yes yes
8.2.x no no yes yes
8.3.x no no no yes

SnapMirror relationships using type XDP and policy mirror-vault, also known as version-flexible SnapMirror, are available with Data ONTAP 8.3. Such a relationship can be built only from source and destination volumes running an 8.3.x release.

Note: The version-flexible SnapMirror feature is not available before Data ONTAP 8.3; therefore, you cannot have a version-flexible SnapMirror relationship with a volume earlier than Data ONTAP 8.3.

The snapmirror show command displays mixed-version relationships in addition to same-version relationships.

For more information about SnapMirror relationships between clusters running different versions of Data ONTAP, see the Clustered Data ONTAP Upgrade and Revert/Downgrade Guide.

SnapVault relationships between clusters running different versions of Data ONTAP

For SnapVault relationships, the version of Data ONTAP that is running on the primary and secondary volumes must be Data ONTAP 8.2 or later. Starting with Data ONTAP 8.2, a SnapVault relationship can be built from an earlier Data ONTAP release to a one that is no more than two releases later. Also starting with 8.2, a SnapVault relationship can be built from a later release to a one that is no more than two releases earlier, providing that the earlier release is 8.2 or later.

The following SnapVault relationships are permitted using type XDP and policy async-mirror:

If the primary volume is located on a system running Data ONTAP… The secondary volume can reside on a system running one of the following releases…
  8.1.x 8.2.x 8.3.x
8.1.x no no no
8.2.x no yes yes
8.3.x no yes yes

Relationships between volumes in different SVMs

Before you can create a relationship between volumes in different SVMs, there must be a peer relationship established between the two SVMs. You can only establish an SVM peer relationship between SVMs with unique names. You should use unique, fully qualified domain names for each SVM.

You can create a peer relationship between two SVMs with FlexVol volumes or between two SVMs with Infinite Volume, but you cannot create a peer relationship between an SVM with FlexVol volume and an SVM with Infinite Volume.