Specifications

ManualsBrandsVMware ManualsComputer equipmentVC-SRM4-A - vCenter Site Recovery Manager

37 Deploying VMware vCenter Site Recovery Manager with NetApp FAS/V-Series Storage Systems

directories exist, it might be necessary to delete and recreate the protection group for those VMs. If these

directories remain, they might prevent the ability to run a DR test or failover.

NFS SUPPORT

NFS support requires SRM 4.0 and vCenter 4.0. ESX 3.0.3, ESX/ESXi 3.5U3+ and 4.0 are also supported

for SRM with NFS.

USING THE RW (READ/WRITE) FIELD IN NFS EXPORTS

NFS support requires that replicated NFS datastores exported from the NetApp array using values in the

RW field. An NFS export with a default RW field value of empty, meaning export RW to all hosts, will not be

discovered by the NAS adapter.

SRM ARRAYS ARE NETAPP CONTROLLERS

Each controller in a NetApp HA cluster takeover pair is considered an array in SRM. Each controller must be

added to array managers separately. In environments using both the SAN and NAS adapters, each

controller must be added both as a SAN array and as a NAS array.

ROLE-BASED ACCESS CONTROLS FOR THE STORAGE ADAPTERS

Instructions and rights required to configure Data ONTAP role-based access controls for the accounts used

as array credentials with SRM 4 can be found in KB article 1010829 at

https://kb.netapp.com/support/index?page=content&id=1010829.

Instructions and rights required to configure Data ONTAP role-based access controls for the accounts used

as array credentials with SRM 5 can be found in KB article 1013325 at

https://kb.netapp.com/support/index?page=content&id=1013325.

SETTING WORKINGDIR VARIABLE IN VMX FILE AFFECTS SRM RECOVERABILITY

Setting a custom value for the workingDir variable in a .vmx file changes the location where ESX stores

virtual machine Snapshot delta files. SRM does not support storing Snapshot delta files outside of replicated

datastores. See the appendix regarding protecting virtual machines without replicating transient data.

DEPLOYING DIFFERENT STORAGE PROTOCOLS AT PRIMARY AND DR SITES

SRM and Data ONTAP do support having differing SAN storage protocols at the primary and DR sites. For

example, you can use a lower cost software iSCSI solution at the DR site while the primary site is using

Fibre Channel. However, NFS cannot be used to recover SAN storage, and SAN protocols cannot be used

to recover NFS storage.

APPLICATION CONSISTENCY

SRM and SnapMirror do not provide application consistency. Application consistency is determined by the

consistency level stored in the image of data that is replicated. If application consistent recovery is desired

applications such as Microsoft SQL Server®, Microsoft Exchange Server® or Microsoft Office SharePoint

Server must be made consistent using software such as the NetApp SnapManager® products.

Implementation of SRM in an environment with virtual machines running SQL, Exchange and SharePoint is

described in detail in TR-3822 Disaster Recovery of Microsoft Exchange, SQL Server, and SharePoint

Server using VMware vCenter Site Recovery Manager, NetApp SnapManager and SnapMirror, and Cisco

Nexus Unified Fabric.

12 REFERENCE MATERIALS

TR-3749: NetApp and VMware vSphere Storage Best Practices

www.netapp.com/us/library/technical-reports/tr-3749.html

TR-3428: NetApp and VMware Virtual Infrastructure 3 Storage Best Practices

www.netapp.com/us/library/technical-reports/tr-3428.html

TR-3446: SnapMirror Best Practices Guide

www.netapp.com/us/library/technical-reports/tr-3446.html

TR-3822: Disaster Recovery of Microsoft Exchange, SQL Server, and SharePoint Server using VMware

vCenter Site Recovery Manager, NetApp SnapManager and SnapMirror, and Cisco Nexus Unified Fabric