Specifications

10
roles are seized it is very important that the clone never be connected to a production VM Network, and that
it is destroyed after DR testing is complete.
PROVIDING ACTIVE DIRECTORY SERVICES FOR SRM FAILOVER
For a real DR failover scenario, the AD cloning process is not required. In the SRM failover scenario, the
existing AD and name resolution servers at the recovery site provide those services. However, the five
FSMO roles must be seized per the procedure described in the Microsoft KB at
http://support.microsoft.com/kb/255504
5 REQUIREMENTS
5.1 SUPPORTED STORAGE PROTOCOLS
SRM 1.0.X provides support for VMFS datastores and RDM devices (FC or iSCSI) only.
The vSphere version of SRM (4.0) provides support for VMFS datastores, RDM devices, and NFS
datastores.
The unified SRM adapter allows a virtual machine to have data in an NFS datastore as well as a iSCSI or
FC datastores or RDM devices. A virtual machine system disk may be stored in NFS, while iSCSI or FC
RDM devices in the same VM are used for application data.
5.2 SRM/SRA VERSION DEPENDENCIES
Specific versions of the NetApp SRA are required to support different versions of VMware SRM. Please see
the table below regarding which versions of SRM and the NetApp SRA are supported together.
NetApp
SRA Version
VMware vCenter SRM Version
V1.0
V1.0U1
V4.X*
v1.0 SAN
Yes
No
No
v1.0.X SAN
No
Yes
No
v1.4 to 1.4.2 SAN or NAS*
No
No
Yes
v1.4.3 (unified)**
No
No
Yes
v1.4.3P1 (unified)**
No
No
Yes
Table 1 NetApp SRA and VMware SRM compatibility
* NFS support with SRM requires vCenter 4.0 and is supported with ESX 3.0.3, ESX/ESXi 3.5U3+, and ESX/ESXi 4.0.
SRM 4.0 is not supported with Virtual Center 2.5.
** Combining NAS and SAN storage protocols for the same VM requires version 1.4.3.