Specifications

11 Deploying VMware vCenter Site Recovery Manager with NetApp FAS/V-Series Storage Systems
5.3 SRA AND DATA ONTAP VERSION DEPENDENCIES
Certain versions of the SRA require specific versions of the Data ONTAP operating system for compatibility.
Please see the table below regarding which versions of Data ONTAP and the NetApp SRA are supported
together.
NetApp
SRA Version
NetApp Data ONTAP
version required
v1.0 SAN
7.2.2+
v1.0.X SAN
7.2.2+
v1.4 to v1.4.2 SAN
7.2.2+
v1.4 to v1.4.2 NAS
7.2.4+
V1.4.3
7.2.4+
v1.4.3 (using vFiler support)
7.3.2+
Table 2 NetApp SRA and Data ONTAP version compatibility
5.4 SUPPORTED REPLICATION TECHNOLOGIES
The NetApp SRA supports the following data replication technologies:
• Asynchronous volume SnapMirror
• Asynchronous qtree SnapMirror
• Synchronous SnapMirror
The NetApp SRA does not support the following replication technologies:
• SnapVault®
• SyncMirror® replication between SRM sites (as in MetroCluster)
Note: A MetroCluster system may serve as the source or destination of SnapMirror relationships in an
SRM environment. However, SRM does not manage MetroCluster failover or the failover of SyncMirror
relationships in MetroCluster.
5.5 SUPPORTED REPLICATION LAYOUTS
Each storage controller or vFiler in a NetApp FAS system is considered an array in SRM. SRM supports
certain array-to-array (or controller-to-controller) replication layouts. To determine supportability, keep this
rule in mind: A single virtual machine cannot own data (vmdk or RDM) on more than one array or vFiler.
Relationships where the data (vmdk or RDM) owned by any individual virtual machine exists on only one
array (physical controller or vFiler) at each site are supported. The SnapMirror relationship layout scenarios
shown here are supported. Each virtual machine in the replicated volumes owns data on only one array
within each site.
Figure 5 Supported Replication Example