Storage Replication Adapter for VMware vcenter SRM April 2017 SL10334 Version 1.5.0
1 Introduction This lab introduces the fundamentals of VMware vcenter Site Recovery Manager on clustered Data ONTAP. Using the two preconfigured sites, you will perform a Test Recovery, actually excute a Planned Migration Recovery, then Re-protect back to the first site. For your convienence, several steps for deploying and configuring this SRM lab environment have been configured in advance. Storage Replication Adapter is a storage vendor specific plug-in to VMware vcenter Site Recovery Manager that enables interaction between Site Recovery Manager and the storage controller. The adapter interacts with the storage controller on behalf of Site Recovery Manager to discover storage arrays and their associated datastores and RDM devices, that are connected to vsphere. The adapter manages failover and test-failover of the virtual machines associated with these storage objects. Site Recovery Manager uses Storage Replication Adapter to discover arrays and replicated and exported datastores, and to fail over or test failover of datastores. Site Recovery Manager uses virtualization to provide end-to-end disaster recovery management and automation across the entire data center. Site Recovery Manager uses VMware infrastructure to build, automate, and test disaster recovery plans for the data center. Site Recovery Manager integrates with vsphere to provide a seamless view of your environment that includes both virtual infrastructure, and disaster recovery management. Storage Replication Adapter provides array-specific support for Site Recovery Manager by following the input specifications from Site Recovery Manager. The adapter enables Site Recovery Manager to execute the following work flows: 2 Discovery of arrays and replicated devices Test recovery Recovery Re-protect
Figure 1-1: 1 Lab Objectives The following list identifies the objectives of this lab exercise: 3 Examine the SnapMirror replication. Explore the setup of the protection groups. Perform a Test Recovery Operation. Perform a Planned Migration Recovery. Perform a Re-protect Operation. Create a Protection Group.
2 Lab Environment All of the servers and storage controllers presented in this lab are virtual devices, and the networks that interconnect them are exclusive to just your lab session. While we encourage you to follow the demonstration steps outlined in this lab guide, you are free to deviate from this guide and experiment with other SRM and Data ONTAP features that may interest you. Figure 2-1: 2 Table of Systems 4 Host Name Operating System Role/Function IP Address cluster1 clustered Data ONTAP 9.1 cluster 1 at Site A 192.168.0.101 cluster1-01 clustered Data ONTAP 9.1 cluster 1 node 1 192.168.0.111 cluster2 clustered Data ONTAP 9.1 cluster 2 at Site B 192.168.0.102 cluster2-01 clustered Data ONTAP 9.1 cluster 2 node 1 192.168.0.121
Host Name Operating System Role/Function IP Address svm1 Storage Virtual Machine for VMware datastore on NFS at Site A SVM mgmt lif 192.168.0.130 svm2 Storage Virtual Machine for VMware datastore on NFS at Site B SVM mgmt lif 192.168.0.140 jumphost Windows Server 2012 R2 primary desktop entry point for lab 192.168.0.5 dc1 Windows Server 2012 R2 Active Directory / DNS 192.168.0.253 esx1 VMware vsphere ESX 6.0 VMware Hypervisor at Site A 192.168.0.51 esx2 VMware vsphere ESX 6.0 VMware Hypervisor at Site B 192.168.0.52 vc1 Windows Server 2012 R2 at Site A VMware vcenter Server 192.168.0.31 vc2 Windows Server 2012 R2 at Site B VMware vcenter Server 192.168.0.32 snapctr Windows Server 2012 R2 SnapCenter 2.0 Server 192.168.0.75 sra1 Site Replication Adapter 4.0 for vc1 Virtual Appliance 192.168.0.33 sra2 Site Replication Adaptor 4.0 for vc2 Virtual Appliance 192.168.0.34 sitea-vm01 CentOS 6.5 x64 linux Nested VM running at Site n/a A sql1-nested Windows Server 2012 R2 Nested VM running at Site 192.168.0.91 B (db on vmdk) 2 User IDs and Passwords 5 Host Name User ID Password Comments jumphost DEMO\Administrator Netapp1! Domain Administrator cluster... admin Netapp1! Same for individual cluster nodes svm... vsadmin Netapp1! svm administrator esx... root Netapp1! Administrator vc... administrator@vsphere.localnetapp1! Local Admin for vcenter
3 Lab Activities This lab contains the following activities and tasks: Tour the Environment on page 6 Test Recovery on page 18 Recovery using a Planned Migration on page 34 Running a Re-protect on page 40 Creating an SRM Protection Group on page 49 Accessing the NetApp SRA Appliances on page 56 3.1 Tour the Environment In this activity you will log into the vcenter and System Manager web interfaces for both Site A and Site B. In addition, you will examine the preconfigured SnapMirror relationship, and explore the Protection Groups and Recovery Plan that are also staged for this demonstration. 1. After connecting to the Jumphost, allow the PowerShell window to complete the lab prep script. Figure 3-1: 2. Launch the link on the desktop for VC1. Figure 3-2: 3. Log in with credentials: administrator@vsphere.local and password: Netapp1!. 3 Figure 3-3: 4. Minimize the browser, then launch the link on the desktop for Cluster1. 6
Figure 3-4: 5. Click on Continue to this website... 5 Figure 3-5: 6. Sign in with credentials: admin, and Netapp1!. 6 Figure 3-6: 7. Minimize the browser, then launch the link on the desktop for VC2. 7
Figure 3-7: 8. Log in with credentials: administrator@vsphere.local, and password: Netapp1!. 8 Figure 3-8: 9. Minimize the browser, then launch the link on the desktop for Cluster2. Figure 3-9: 10. Click on Continue to this website... 8
10 Figure 3-10: 11. Sign in with credentials: admin, and Netapp1!. 11 Figure 3-11: 12. Optionally, go to both vcenters and clear any warnings that may show up in the Alarms window. 9
12 Figure 3-12: 13. Return to the browser tab for VC1, click on Home and select Site Recovery. 13 Figure 3-13: 14. Click Protection Groups. 10
14 Figure 3-14: 15. Confirm Protection Status is OK, then click SiteA-NFS-PG. 15 Figure 3-15: 16. Login with User name: administrator@vsphere.local and the password: Netapp1!. Note: If you missed the prompt with the login to VC2 from VC1, you may get permission errors. If so, you should log out of VC1, log back in, and return to the steps above. 11
16 Figure 3-16: 17. Review the Summary tab to confirm the Protected Site is vc1, and the Recovery Site is vc2, then click the Related Objects tab. 17 Figure 3-17: 18. Click Virtual Machines and review the settings. 12
19. Click Recovery Plans. 18 19 Figure 3-18: 20. Highlight SiteA-NFS-PG. Click Actions > Edit Plan... 20 Figure 3-19: 21. Review the Recovery Plan by clicking Next. 13
21 Figure 3-20: 22. Click Next. 14
22 Figure 3-21: 23. Click Next. 15
23 Figure 3-22: 24. Click Next. 16
24 Figure 3-23: 25. Click Finish. 17
25 Figure 3-24: 3.2 Test Recovery A test recovery operation ensures that a real operation will work during a disaster, or a planned migration. A test recovery operation does not affect an ongoing SnapMirror replication. During a test recovery operation, Storage Replication Adapter creates a FlexClone volume from the latest Snapshot copy of the SnapMirror destination volume, and displays the cloned export path to Site Recovery Manager. This activity illustrates how to perform a Test Recovery. 1. First, examine the characteristics of the production VM at the Protected Site by going to the browser tab for VC1. Navigate to Home > Hosts and Clusters. 18
1 Figure 3-25: 2. Select the sitea-vm01, and in the Summary tab scroll down to the box labeled Related Objects. 3. Observe that the VM in the Site A cluster, on host esx1, has a network assigned, and is on nfs1 storage (in cluster1). 2 3 Figure 3-26: 19
4. Now observe the replicated seed copy of the VM at the Recovery site by going to the browser tab for VC2. Navigate to Home > Hosts and Clusters. 4 Figure 3-27: 5. While still in VC2, select sitea-vm01, and in the Summary tab scroll down to the box labeled Related Objects. 6. Observe that the recovery copy is listed as being in the Site B cluster, is on host esx2, has no network assigned, and is on esx2local. 20
5 6 Figure 3-28: 7. Go to the browser tab for Cluster1's System Manager UI, click on SVMs. 8. Double-click on svm1. 7 8 Figure 3-29: 9. Drill down into Volumes. 10. Notice that the volume nfs1 (which is the datastore for the virtual machine sitea-vm01) is in the aggregate aggr1_cluster1_1, which is a set of disks in the Site A storage cluster. 21
9 10 Figure 3-30: 11. Now go to the browser tab for Cluster2 s System Manager UI, click on Protection > Relationships. 12. Examine the source SVM is svm1 (on site A), and the source volume is nfs1 with a destination volume of nfs1_dr. 11 12 Figure 3-31: 13. While still in Cluster2, drill down into SVMs > svm2. 22
13 Figure 3-32: 14. Click on Volumes. 15. Examine the volume nfs1_dr (which is the target for the SnapMirror) is in the aggregate aggr1_cluster2_1, that is a set of disks in the Site B storage cluster. 14 15 Figure 3-33: 16. Return to the browser tab for VC1, click on Home > Site Recovery. 23
16 Figure 3-34: 17. Go to Recovery Plans. 24
17 Figure 3-35: 18. With Recovery Plans highlighted, click the green play icon to run a Test Recovery operation. 18 Figure 3-36: 19. Click Next. 25
19 Figure 3-37: 20. Click Finish. 26
20 Figure 3-38: 21. Observe that the progress is updated in the Status column. 21 Figure 3-39: 22. Go to the browser tab for Cluster2 s System Manager. Under Volumes, click Refresh. 23. Note that a new volume has been created named testfailoverclone.... 27
22 23 Figure 3-40: 24. Go to the browser tab for VC2, navigate to Hosts and Clusters, and click the Refresh icon. 24 Figure 3-41: 25. Highlight sitea-vm01, and in the Summary tab under Related Objects, note that the Cluster and Host remain as they were, but a Network is now assigned, and the storage is now nfs1 (in Site B). 28
25 Figure 3-42: 26. Go back to the browser tab for VC1, navigate to the Hosts and Clusters and click the Refresh icon. 27. Note that the protected VM remained unaffected and can be powered on to be fully operational while the Test Recovery is being conducted. 26 27 Figure 3-43: 28. Go to Home > Site Recovery. 29
27 Figure 3-44: 29. Click on Recovery Plans. 30. With SiteA-NFS-RP highlighted, click the yellow broom icon to begin the cleanup operation of the Test Recovery. 30
30 Figure 3-45: 31. Click Next. 31
31 Figure 3-46: 32. Click Finish. 32
32 Figure 3-47: 33. The progress is monitored under the Status tab. 33 Figure 3-48: 34. Return to the browser tab for Cluster2's System Manager, under Volumes click Refresh. 35. Note that the Cleanup removed the test volume created. 33
34 35 Figure 3-49: 36. Return to the browser tab for VC2, click Refresh. 37. Note that the Related Objects in the Summary tab for sitea-vm01 now shows no network setting, and the storage as esx2local. 36 37 Figure 3-50: 3.3 Recovery using a Planned Migration When performing a recovery, Site Recovery Manager offers two options: one for planned migration of services, one for unplanned disaster recovery. During disaster recovery, Storage Replication Adapter cancels any ongoing transfers to the SnapMirror destination, quiesces the destination, and breaks the SnapMirror relationship. When the SnapMirror relationship is broken, the destination volume is ready for read/write operations. During a planned migration, the recovery operation shuts down the virtual machines at the protected site. Storage Replication Adapter performs a SnapMirror update and synchronizes the storage systems, quiesces the 34
destination, and breaks the SnapMirror relationship. When the SnapMirror relationship is broken, the destination volume is ready for read/write operations. This activity illustrates how to perform a Planned Migration Recovery operation. 1. In the browser tab for VC1, under Recovery Plans, confirm that SiteA-NFS-RP has a status of Ready. 1 Figure 3-51: 2. Optional: power on the VM at the Protected Site, sitea-vm01. 2 Figure 3-52: 3. Click OK. 35
3 Figure 3-53: 4. Go to the browser tab for VC2, refresh and confirm that the replication copy on the Recovery Site in the Summary tab under Related Objects sits on esx2local storage, which is the Placeholder Datastore for SRM. 4 Figure 3-54: 5. Return to the browser tab for VC1, under the Recovery Plans, Objects tab. With SiteA-NFS-RP highlighted, click the red circle play icon to begin the operation: Run Recovery Plan. 36
5 Figure 3-55: 6. Click the I understand... checkbox. 7. Make sure that the Planned Migration Recovery type is selected. 8. Click Next. 6 7 8 Figure 3-56: 9. Click Finish. 37
9 Figure 3-57: 10. Select the plan, and go to the Monitor tab. 11. Observe the progress as the Status column is updated. 12. Click back to go to the Array Based Replication. 38
10 12 11 Figure 3-58: 13. Select one of the svms, go to the Manage tab, and observe that the status is listed as Failover in progress. 13 Figure 3-59: 14. Go to Home > Hosts and Clusters. 15. Select sitea-vm01, scroll down in the Summary tab to the Related Objects, and note that the network is not present, and the storage is listed as esx1local. 39
15 Figure 3-60: 16. Go to the browser tab for VC2 and click Refresh. 17. Navigate to the Summary tab for sitea-vm01, and observe that the Related Objects section has sitea-vm01 now running in the Recovery Site with the correct networking assigned. 16 17 Figure 3-61: 3.4 Running a Re-protect After a recovery operation, you can run the re-protect operation to replicate the changes made at the recovery site to the original protected site. During a re-protect operation, Storage Replication Adapter reverses the direction of 40
the existing SnapMirror relationships, and starts replicating the changes made at the recovery site to the original protected site. This activity demonstrates the Reprotect steps. 1. (Optional) Right-click on sitea-vm01 on VC1, and select Power > Shut Down Guest OS. 1 Figure 3-62: 2. Click Yes. 2 Figure 3-63: 3. Go to the browser tab for VC2, in the Summary tab scroll down to the Related Objects, and observe that sitea-vm01 has a network assigned, and is on nfs1 storage. 41
3 Figure 3-64: 4. Go to the browser tab for VC1, in the Summary tab scroll down to the Related Objects and observe that sitea-vm01 has no network assigned, and is on esx1local storage. 4 Figure 3-65: 5. From VC1 (the Protected Site), go to Home > Site Recovery. 42
5 Figure 3-66: 6. Click on Recovery Plans. 43
6 Figure 3-67: 7. Select SiteA-NFS-RP. 8. If prompted, login with the credentials for VC2 (the Recovery Site) of User name: administrator@vsphere.local, with password Netapp1!. 9. In the Monitor tab with the Recovery Steps button pressed, find and click on the gray shield with the yellow lightning bolt icon to being the Reprotect recovery plan operation. 44
7 9 Figure 3-68: 10. Click the checkbox next to I understand... 11. Click Next. 45
10 11 Figure 3-69: 12. Click Finish. 46
12 Figure 3-70: 13. Monitor the progress as the status column is updated. 13 Figure 3-71: 14. After the final step the Plan status changes from Reprotect in progress to Ready. 47
15. Click back in the Navigator panel. 15 14 Figure 3-72: 16. Select Array Based Replication. 16 Figure 3-73: 17. Select svm2. 48
18. In the Manage tab with Array Pairs selected, observe that the status is Ongoing Replication. This demonstrates that the Reprotect is now complete, and the VM is running from the Protected Site (Site A), ready to be sent to the Recovery Site (Site B) once again, and the SnapMirror relationship is still providing the replication between sites. 17 18 Figure 3-74: 3.5 Creating an SRM Protection Group After you configure a NetApp SnapMirror data protection relationship, the NetApp Site Replication Adapter for VMware's Site Recovery Manager makes SRM operations very simple. The tight integration between NetApp's SRA with VMware's SRM allows for quick and easy setup of storage resources in SRM. In this activity, a SnapMirror data protection relationship exists for the volume nfs2 on the storage virtual machine svm2 on cluster 1, going to the volume nfs2_dr on storage virtual machine svm1 on cluster 1. In addition all SRM placeholders and mappings have been pre-configured. This activity will configure a Protection Group in SRM while using the NetApp SRA to demonstrate how tightly integrated the solution can be for an administrator. 1. From VC2, click on Site Recovery Manager. 49
1 Figure 3-75: 2. Double-click Array Based Replication. 2 Figure 3-76: 3. Click on svm2. 4. Confirm the Outgoing Replication exists. 50
3 4 Figure 3-77: 5. Return back to Protection Groups. 5 Figure 3-78: 6. Click the blue shield with green plus icon to create a Protection Group. 51
6 Figure 3-79: 7. Enter SiteB-NFS-PG. 8. Click Next. 7 8 Figure 3-80: 52
9. Accept the defaults, click Next. 9 Figure 3-81: 10. Add a check next to the nfs2 datastore. 11. Observe the registered VMs are displayed. 12. Click Next. 53
10 11 12 Figure 3-82: 13. Click Finish. 54
13 Figure 3-83: 14. The Protection Group for VMs managed by SRM on NetApp storage is now complete. 14 Figure 3-84: 55
3.6 Accessing the NetApp SRA Appliances In order to install the NetApp SRA 4.0 plug-in, known as the Storage Replication Adapter for ONTAP for VMware vcenter Site Recovery Manager, a standard ova server appliance deployment is conducted through vcenter. Following the deployment, a small installer runs to link the vcenter/srm server with the SRA appliance. Following deployment, you can use a command line interface to the SRA appliance maintenance console for maintenance, diagnostics, or to start, stop, or enable ssh. In addition, the Storage Replication Adapter (SRA) 4.0 provides you with a web-based command-line interface to add, edit, or remove clusters or SVMs. The following activities demonstrate two methods to interact with the SRA 4.0 appliances. 3.6 SSH CLI access to Site Replication Adapter Appliances 1. Open PuTTy. Figure 3-85: 2. Double-click on sra1 (or sra2). 2 Figure 3-86: 3. Log in with user maint, and password Netapp1!. 56
3 Figure 3-87: 4. Examine the available options. 5. Press x to exit. 4 5 Figure 3-88: 3.6 Web Based CLI access to Site Replication Adapter Appliances 1. To navigate to SRA1, open your browser, navigate to https://192.168.0.33:9083 (use.34 for SRA2). 2. Log in with user administrator, and password Netapp1!. 57
1 2 Figure 3-89: 3. Examine and explore the available options. 4. To exit, click Logout, or close the browser tab. Figure 3-90: 58
4 Lab Limitations This lab has the following limitations: 59 All of the servers and storage controllers presented in this lab are virtual devices. Consequently, any operations involving movement of large quantities of data will not exhibit performance representative of real systems.
5 References The following references were used to create this lab guide. 60 https://library.netapp.com/ecm/ecm_get_file/ecmp1235991 http://www.netapp.com/us/media/tr-4264.pdf
6 Version History 61 Version Date Document Version History 1.5.0 Apr 2016 Initial Release
Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exact product and feature versions described in this document are supported for your specific environment. The NetApp IMT defines the product components and versions that can be used to construct configurations that are supported by NetApp. Specific results depend on each customer's installation in accordance with published specifications. NetApp provides no representations or warranties regarding the accuracy, reliability, or serviceability of any information or recommendations provided in this publication, or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS, and the use of this information or the implementation of any recommendations or techniques herein is a customer s responsibility and depends on the customer s ability to evaluate and integrate them into the customer s operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document. Go further, faster 2017NetApp, 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, Data ONTAP, ONTAP, OnCommand, SANtricity, FlexPod, SnapCenter, and SolidFire are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.