Post on 20-Aug-2015
transcript
1
Larry Touchette
Technical Marketing
VMware Site Recovery
Manager and NetApp
FAS/V-Series
SE Technical Presentation
Agenda
DR Challenges & VMware Site Recovery Manager
New features in SRM version 5NetApp Value in VMware SRM environmentsSystem and Software RequirementsSRM Workflows and Array InteractionBest Practices and Configuration RulesSRM and SRA Configuration WorkflowsLimitations
2
3
DR Challenges & VMware Site Recovery Manager
Traditional Disaster Recovery
Involves:– Complex processes and infrastructure
– Precise training, documentation, and execution
Requires:– Dedicated, identical hardware
– Significant consumption of time and resources
– 2x to 3x the capacity used for production
– Unacceptable levels of WAN utilization
Results in:– Inability to test or frequently failed tests
– Recovery times of days or weeks
– Ability to protect only a few important workloads
4
VMware Site Recovery Manager
Advanced workflow automation for DR setup, testing and failover, and failback
vCenter™ SRM
VMware® ESX®
vSphere™
SRM vCenter
VMware ESX
vSphere
− Allows dual purposing of hardware for production or test/dev
− Protects more of the environment for less cost
− Integrates with NetApp SnapMirror and NetApp FlexClone®
Recovery SiteProtected Site
NetAppSnapMirror®
5
VMware SRM Failover
Configure protection groups at primary siteBuild recovery plans at the DR siteAfter disaster execute recovery plan at DR siteSnapMirror® break automatically performed
Protected Site Recovery Site
Protection Groups Recovery Plan
®
NetAppSnapMirror
NetAppSnapMirror®
6
NetAppSnapMirror®
VMware SRM DR Testing
SRM DR testing: verifies that DR plan is reliable without interrupting production
Automatically creates private network and FlexClone® volumes for testing
Protected Site Recovery Site
Protection Groups Recovery Plan
7
®
VMware Site Recovery Manager
SRM is bidirectional− Sites can protect each other
Protected / Recovery Site Protected / Recovery Site
Protection Group
Recovery Plan
Protection Group
Recovery Plan
NetAppSnapMirror®
8
®
Site Recovery Manager Major Features
Protect
Test failover
Failover (unplanned)
Centralized administration
vSphere™ replication (host-based replication)
Failover performance improvements
Test failover with storage synchronization
Planned failover with storage synchronization
Automated failback
New inSRM 5
9
Automated Failback in SRM 5
Reverses the SnapMirror® replication relationships
Resynchronizes storage replication in opposite direction
Reverses the roles of the two sites (only for the VMs in the affected recovery plan)
Then failback is simply the planned failover workflow
NetApp FASController
Recovery Site
NetApp® FASController
Protected Site
FlexVolVolume 3
LUN4
FlexVolVolume 4
LUN5
FlexVolVolume 7
FlexVolVolume 8
LUN4
LUN5
NetAppSnapMirrorNetApp
SnapMirror
FlexVol®
Volume 3
LUN4
FlexVolVolume 4
LUN5
NetAppSnapMirror
10
Centralized SRM 5 Administration
SRM 5 administration for both sites can be performed by connecting to either site’s vSphere™ client
Protected Site Recovery Site
vCenter™ SRM
VMware ESX
vSphere
SRM vCenter
VMware ESX®
vSphere
vSphereClient
SRMAdministrator
11
vSphere Replication in SRM 5
12
SnapMirrorvSphere
Replication
Per VM granularity of replication
Datastore granularity of replication
Support for automated failback
Supports ESX hosts of different versions
Supports Physical Mode RDMs
Supports Fault Tolerance, Linked Clones
Supports powered off VMs
Can be used in same environment
SRM 5 Performance Improvements
VM reconfiguration step removed from prepare storage step– VMs can start power on as soon as each VM is
reconfiguredMultiple VMs powered on with one request
– Improves serialization of VM startupNew method for reconfiguration of VM IP
addresses– Does not require additional reboots of VMs
13
14
NetApp Value in SRM Environments
NetApp® FAS Array
RDM RDM
Vol2Vol1
APPOS
ESX® Cluster
VMFS
APPOS
RDM Pointers
F:\ L:\
NFS
NetApp FAS/V-Series Storage Replication Adapter
Multiprotocol support for FC, iSCSI, and NFS in one adapter
Fully thin-provisioned FlexClone® DR test environments
Support for MultiStore® vFiler® units as SRM storage arrays
15
SnapMirror and FAS Deduplication
FAS deduplication on primary storageOnly unique data is replicated to the DR site
Protected Site Recovery Site
New Data Written
Before DedupeAfter
Dedupe
Data Deduplication
NetAppSnapMirror®
16
SnapMirror Network Compression
SnapMirror® native compression reduces WAN utilization
Recovery SiteProtected Site
AfterDedupe
Compression Decompression
NetAppSnapMirror®
17
FlexClone: Space-Efficient DR TestingNetApp FlexClone®
– Allows frequent nondisruptive testing– Reduces capacity needed for DR testing to
only that written during tests
Aggregate capacity
Storage used by replicated datastores
Storage used for FlexClone volume creation(metadata only)
Storage used for writes during DR testing
18
Virtual Storage Tiering with NetApp Flash CacheProvides the performance boost needed
during critical recover times
19
VMware® ESX®
Faster boot timeLess physical disks
requiredNo SSD requiredLess disk I/O performedVirtual tiering without
configuration overhead
20
System and Software Requirements
VMware Requirements for SRM in vSphere
Installed at both protected and recovery sites:− A vSphere™ vCenter™ Server
− A vSphere Site Recovery Manager Server
− SRM 4.1 requires vCenter Server 4.1
− SRM 5.0 requires vCenter Server 5.0
− ESX® Servers
− Multiple ESX versions from 3.5UX to 5.0 with a mix of update releases are supported with both SRM 4 and 5; see compatibility matrix for appropriate SRM version at www.vmware.com/support/pubs/srm_pubs.html
21
NetApp Adapter Requirements
The NetApp® Storage Replication Adapter (SRA) is free software available to VMware® SRM customers. Obtain the SRA from:
Software download page on now.netapp.com orVMware SRM download page www.vmware.com/go/download-srm
NetApp licenses required on protected and recovery site storage− SnapMirror®
− iSCSI, FCP, or NFS
− FlexClone®
22
NetApp Adapter Requirements
All NetApp® FAS and V-Series platforms qualified with VMware® vSphere™ are supported
– See supported NetApp platforms at www.vmware.com/resources/compatibility:select Storage/SAN from What are you looking for box, select NetApp from Partner Name box, and click the Update button
For SRM storage support per SRM version, seewww.vmware.com/pdf/srm_storage_partners.pdf
23
NetApp Adapter Requirements
NetApp Data ONTAP® version support
− 7.2.4 or greater required
− 7.3.2 or greater required for MultiStore® vFiler® support
− Includes NetApp Data ONTAP 8 operating in 7-Mode
Support for NetApp Data ONTAP operating in Cluster-Mode is planned for future release of the NetApp adapter
24
Data ONTAP 7-Mode and Adapter Version Dependencies
NetApp Adapter Version
Minimum Data ONTAP* Version
Supported SRM Version
1.4 NAS 7.2.2 4.x
1.4.2 SAN 7.2.4 4.x
1.4.3 (unified) 7.2.4 4.x
1.4.3 (using vFiler®) 7.3.2 4.x
2.0** (unified) 7.2.4 5.0
2.0** (using vFiler) 7.3.2 5.0
Current as of September 2011. Please check latest documentation for up-to-date support.
* 7-Mode only, including version 8. Support for Cluster-Mode is planned for a future version of the NetApp® SRA.** SRA 2.0 requires SRM 5 and cannot be used with SRM version 4.
25
Replication Software Support
Supported Replication Products– Volume SnapMirror®
– Qtree SnapMirrorUnsupported Replication Products
– SnapVault®
– Failover between MetroClusterTM nodes is not supported however MetroCluster can be the source or destination for SnapMirror with SRM
– Support for NetApp Data ONTAP operating in Cluster-Mode is planned for future release of the NetApp® adapter
26
Upgrading from SRM 4 to SRM 5
VMware® supports upgrade from SRM 4 to SRM 5– It is not an upgrade process, but a remove-
and-import process. Uninstall SRM 4, install SRM 5, use import utility to import configuration into SRM 5
In a NetApp® environment the SRM 4 adapter must be uninstalled before uninstalling SRM 4– Otherwise later uninstall of SRM 4 adapter will
fail and require manual uninstall
27
28
SRM and Array Interaction
Test Failover with Storage Update
Test Recovery Workflow– SRM optionally requests update of replication
– NetApp® SRA performs SnapMirror® update as requested
– SRM requests a temporary copy of replica images
– NetApp SRA creates FlexClone volumes
– SRA adds LUNs to igroups or creates NFS exports
29
Planned Failover with Storage Update
Planned Failover Workflow− SRM requests SnapMirror® update of replication
− SRM shuts down VMs at protected site
− SRM requests second update of replication
− SRM requests promotion of replica images
− SRA breaks SnapMirror relationships, making storage writable
− SRA adds LUNs to igroups or creates NFS exports
− SRM recovers VMs at protected site
30
Reprotect for Automated Failback
Reprotect Workflow (to prepare for failback)− SRM requests reversal of replication
− SRA performs SnapMirror® resync in reverse direction (which synchronizes replication)
− SRM reverses roles of protected and recovery sites for affected protection groups
− SRM administrator may now do planned failover to fail back to original site
31
32
Best Practices and Configuration Rules
SRM Best Practices
Following SRM best practices means following required practices, described below, to have a successful SRM test failover– The first few tests usually fail– Follow the prescribed setup workflows– Make configuration checking part of setup
before attempting test failoverClone AD servers for DR testing
– Microsoft best practice is to not replicate AD servers
33
Upgrading from SRM 4 to SRM 5
VMware® supports upgrade from SRM 4 to SRM 5– It is not an upgrade process, but a remove-
and-import process. Uninstall SRM 4, install SRM 5, use import utility to import configuration into SRM 5
In a NetApp® environment the SRM 4 adapter must be uninstalled before uninstalling SRM 4– Otherwise later uninstall of SRM 4 adapter will
fail and require manual uninstall
34
Required Practices for NetApp Adapters
Source volume must be replicated to only one destination− Volume fanout with SnapMirror® is not supported
− Failover to second or further destination in a SnapMirror cascade relationship is not supported.For example: In A B C cascade, failover between A and B is supported, failover between A and C is not supported.
35
Required Practices for NetApp Adapters
MultiStore® vFiler® support requires zapi option enabled on physical controller >options vfiler.vol_clone_zapi_allow on
36
Required Practices for NetApp Adapters
LUNs at source must be in igroup of type “vmware”Note: RDMs use LUN type of Guest OS, igroup type of “vmware”
Adapter 1.4.x and earlier requires igroups preexist at recovery site– Don’t forget about creating igroups in destination vFiler® units
Adapter 2.0 for SRM 5 automatically creates igroups during failover and test failover
Replicated LUNs must not be preadded to igroups; SRM adds them for test and failover
37
Required Practices for NetApp Adapters
Exports must be in /etc/exports file− Temporary manual exports are not discovered
Exports must use values in RW security field− Exports RW to all are not discoveredDiscoverable: /vol/vol1 -rw=192.168.2.0/24,root=192.168.2.0/24
Not discoverable: /vol/vol1 -rw,root=192.168.2.0/24
Datastores must have VMs in them to be discovered
38
Each NetApp controller or vFiler® unit is a separate array in Site Recovery Manager
A VM must have data ononly one array in each site
NetApp® FAS Array A
VM5
FAS HA Pair
NetApp FAS Array B
VM6
NetApp FAS Array C
VM5
FAS HA Pair
NetApp FAS Array D
VM6
Supported Replication Layouts
Protected Site Recovery Site
39
NetApp® FAS Array A
VM5
FAS HA Pair
NetApp FAS Array B
NetApp FAS Array C
FAS HA Pair
NetApp FAS Array D
Unsupported Replication Layouts
A VM with data on more than one array at either site cannot be protected with SRM
Protected Site Recovery Site
VM5
RDMRDM RDMRDM
40
Using Qtrees with SRM
If using volume SnapMirror (VSM) with multiple qtrees exported as NFS datastores or each containing LUNs– Single qtree failover is possible but not
recommended, use one recovery plan for all qtrees
– Failback of one qtree in a volume with multiple qtrees is not supported as this could affect other VMs at the failback target site
Using VSM replication with volume-level export, but qtree in volume as mount point is not supported
41
Using Qtrees with SRM
Recommendation Use same level for replication and
datastore– If using VSM, export and mount the volume
or store LUN in the volume– If using QSM, export and mount the qtree or
store LUN in the qtree
42
Multiple LUNs In One Volume
With multiple LUNs in one volume all LUNs in that volume should be failed over in the same recovery plan– Failback of one LUN in a volume with multiple
LUNs is not supported as this could affect other VMs at the failback target site when the VSM relationship is reversed
43
Mixed iSCSI and FC Environments
Supported: Failover in either direction between sites where one site is using FC and the other site is using iSCSI is supported
Not Supported: Failover to ESX® hosts having a mix of iSCSI and FC in same cluster or recovery group is not supported by VMware® or NetApp®
44
45
Configuration Workflows
Prerequisites and Recommendations
1. There is VMware® infrastructure at each site– vCenter™ server and ESX® servers– VMware licensing
2. Install VMware SRM application at each site– Typically installed on its own VM– Can share a database server with vCenter– Enable HTTP access between SRM servers (port 80)
3. Install SRA on the SRM server at each site
4. Supporting infrastructure at each site– Active Directory for authentication– DNS for name resolution– Create a VM placeholder datastore at each site
46
Configuration Workflows
Perform configuration checking as a part of the setup workflow
At protected site:1. Verify LUNs are in igroup of type “vmware”
2. Verify NFS exports have –rw security entries
3. Verify proper SnapMirror® relationships exist
47
NetApp
Implementation Workflows
At recovery site:1. Verify controller (or vFiler®) has igroup with OS
type “vmware” (not needed for version 5)
2. Verify proper SnapMirror® relationships exist
3. Verify storage network connectivity between NetApp® storage ports and ESX® VMkernel ports(Ethernet VLANs, FC zoning, etc)
4. Provision storage for placeholder VMs
5. Create private DR testing network if required
6. Check host VM ownership if not using DRS(if not using VMware® DRS, VMs are started on the ESX host that owns the placeholder VM)
NetApp
vCenter
48
Implementation Workflows
SRM 5 has clickable workflows in the vSphere™
client interface on the SRM Getting Started tab
49
Follow the steps in order for a successful SRM setup
Using the NFS IP Addresses Field
When adding the NetApp® controller in the Array Manager, enter the controller NFS addresses in the NFS IP addresses
See network layout example on following slide
50
Using the NFS IP Addresses Field
192.168.50.50192.168.51.50FAS Controller
Storage IPs
Private StorageNetwork
FAS ControllerAdmin IP
192.168.10.50
NAS SharedStorage
Admin Network
51
Enter into NFS IP Addresses field
Volume Filtering in NetApp SRA 2.0
In SRM 5, replicated volumes that are not part of the VMware® environment may be reported with an error or warning in the SRM interface
In the above example the vmcoe volumes are not a desired part of this SRM environment
52
Volume Filtering in NetApp SRA 2.0
The volume filter fields on the array manager configuration screen can be used to include or exclude certain volumes from SRM discovery
53
Volumes containing the text “vmcoe” are excluded
SnapMirror by IP Address with SRA 2.0
If SnapMirror® relationships are created on the destination controller using source IP address as shown here:
At protected site SnapMirror status shows: Source Destination State Lag Statusf3170a:volsrc f3170c:voldst Source 00:05:04 Idle
At recovery site SnapMirror status shows:Source Destination State Lag Status10.72.192.75:volsrc f3170c:voldst Snapmirrored 00:09:29 Idle
54
IP address instead of host name of source controller
SnapMirror by IP Address with SRA 2.0
Then you must configure the use_ip_for_snapmirror_relation option in the ontap_config.txt file at each site
And configure the IP address to hostname mapping in the ip_hostname_mapping.txt file at each site as shown here:
f3170a = 10.72.192.75
f3170c = 10.72.192.78 (entries are case sensitive)
Configuration files are by default atC:\Program Files (x86)\VMware\VMware vCenter Site Recovery Manager\storage\sra\ONTAP
55
56
Limitations
Limitations
Automated Storage DRS Considerations– SRM 5 is not yet integrated with vSphereTM 5
Automated Storage DRS– If Storage DRS performs a migration of a VM
from a replicated datastore to a non-replicated datastore the migrated VM will no longer be protected
57
Limitations
When reversing SnapMirror® relationships SRA will configure same replication schedule on new destination– However, currently, compression and tcp window
size cannot be set by SRA and must be set manually after reversal if nondefault setting is required
58
Limitations
After reversing SnapMirror® relationship, SRA 2.0 does not remove SnapMirror Snapshot™ copies that were used for replication in the other direction– After replication reversal administrator can remove
snapshots (see process in notes)
– A solution is being planned for a future SRA release
59
Limitations
iSCSI initiators should be disabled in the ESX® recovery hosts if those hosts are also using FC and ALUA– If an FC connected ESX host has the iSCSI initiator
enabled, then SRM will include both the FC and iSCSI initiators in the failover connection request
– Data ONTAP® does not support adding a LUN to an iSCSI igroup and an FC ALUA-enabled igroup at the same time
– This configuration is also not supported by VMware® SRM
60
Limitations
Non-quiesced SVMI snapshot recovery feature– Not available in SRM 5 adapter– Supported only with SRM 4 adapter 1.4.3– Has very limited use cases– Has specific configuration requirements
(See appendix of TR-3671 and notes below)
61
Field Resources
SE Technical Presentation on Field Portalhttps://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=36857
– Describes NetApp capabilities, values, best practices, requirements, and limitations in a SRM environment
– Contains links to matrices, docs, and articles
Customer Presentation on Field Portalhttps://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=24728
– Sales enablement presentation covering NetApp SnapMirror integration with SRM
– Contains a subset of SE deck slides
62
Resources
NetApp SRA Administration Guide and Release Notes in SRA package and on the NOW® site
SRM compatibility matrices for SRM, VC, ESX/ESXiwww.vmware.com/support/pubs/srm_pubs.html
For SRM storage support per SRM versionwww.vmware.com/pdf/srm_storage_partners.pdf
VMware SRM download page www.vmware.com/go/download-srm
Supported NetApp platformswww.vmware.com/resources/compatibility:select Storage/SAN from What are you looking for box, select NetApp from Partner Name box, and click the Update button
VMware SRM Documentation Sitewww.vmware.com/support/pubs/srm_pubs.html
63
Additional Resources
NetApp TR-3671: VMware vSphere Site Recovery Manager in a NetApp Environmentmedia.netapp.com/documents/tr-3671.pdf (SRM 4 only, work in progress for SRM 5 update)
RBAC rights for NetApp SRM version 4 Adaptershttps://kb.netapp.com/support/index?page=content&id=1010829
RBAC rights for NetApp SRM version 5 Adapterhttps://kb.netapp.com/support/index?page=content&id=1013325
64
65
© 2011 NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consent of NetApp, Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, Go further, faster, Data ONTAP, FlexClone, FlexVol, MetroCluster, MultiStore, NOW, SnapMirror, Snapshot, SnapVault, and vFiler are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries. VMware and ESX are registered trademarks and vCenter and vSphere are trademarks of VMware, Inc. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.