VMware vcenter Site Recovery Manager 6.0 Configuration and Testing for HP 3PAR StoreServ Storage

Transcription

1 Technical white paper VMware vcenter Site Recovery Manager 6.0 Configuration and Testing for HP 3PAR StoreServ Storage Table of Contents Introduction 2 Purpose and Scope of the document 2 Overview 2 Intended audience 2 Configuring SRA and SRM and running Recovery Plans 3 Pre-Requirements 3 Configuring HP 3PAR StoreServ Storage systems 3 Configuring ESXi hosts 3 Configuration Diagram :SRM/SRA with HP 3PAR StoreServ Storage 3 SRM/SRA Configuration 4 Running the Recovery Plans 15 SRA Supported Configurations 27 Troubleshooting Tips for Configuration 30 Conclusion 32 Acronyms 32 Learn more 32 Other references 32 1

2 Introduction VMware vcenter Site Recovery Manager (SRM) is an industry-leading disaster recovery management software solution. SRM helps to build, manage, test, and execute disaster recovery plans for a VMware vsphere virtual infrastructure. It can integrate natively with VMware vsphere Replication and also supports a wide range of array-based replication products available by all major VMware storage partners. Site Recovery Manager integrates with third-party storage array-based replication products through a Storage Replication Adapter (SRA). HP provides a HP 3PAR SRA to support VMware SRM s array-based replication. Purpose and Scope of the document VMware SRM requires considerable knowledge of the partner storage array involved in replication. Without this knowledge, issues might occur due to incorrect storage, replication configuration, requirements of naming conventions for the components involved, and so on. This document provides steps to configure HP 3PAR StoreServ Storage systems that are involved in replication, to work with VMware SRM. This document also describes the configuration steps that must be implemented on HP 3PAR StoreServ Storage systems in a production environment and possible issues that might occur during the implementation of VMware SRM. Overview HP 3PAR SRA for VMware SRM 6.0 software is installed on VMware SRM servers. The HP 3PAR SRA enables VMware SRM to work with HP 3PAR Remote Copy software for array-based replication. The current version of the HP 3PAR SRA software is 6.0. Intended audience This document is intended for the users and administrators with knowledge of: HP 3PAR StoreServ Storage with Remote Copy software VMware vcenter Site Recovery Manager VMware vcenter Server and Web Client ESXi host and Virtual Machines (VMs) 2

3 Configuring SRA and SRM and running Recovery Plans Prerequisites VMware vcenter Server and vsphere Client are installed on both Protected and Recovery sites. VMware SRM server is installed and configured to pair both Protected and Recovery sites. HP 3PAR SRA 6.0 is installed successfully on both Protected and Recovery sites. HP 3PAR Remote Copy and virtual copy license are enable on HP 3PAR StoreServ Storage systems. HP 3PAR StoreServ Storage systems can be managed with management console software SSMC or through CLI. Configuring HP 3PAR StoreServ Storage systems Create identical virtual volumes on both the primary and the recovery storage systems. Create a Remote Copy Group using the identical volumes on both the storage systems. Export the primary storage systems volume to the primary ESXi host. Configuring ESXi hosts At primary ESXi host, rescan for the exported volumes from the HP 3PAR StoreServ. The exported volumes along with LUN IDs must be visible. Create a VMFS datastore by selecting the primary exported volume. You will see it under Datastores tab. Now create or deploy an active VM (to be protected) on the datastore created using the exported LUN. Install VMTools on the VM created. VM Tools are required by SRM to power on and power off during failover operations. Configuration Diagram: SRM/SRA with HP 3PAR StoreServ Storage 3

4 SRM/SRA configuration Step 1. Configure (pair) SRM sites through VMware vsphere Web Client Launch VMware vsphere Web Client using desktop icon created after install or through navigation : Start->VMware->vCenter Server->VMware vsphere WebClient. Login using user name and the password configured during the vcenter Server installation. Select Site Recovery Manager and click on Site Recovery icon to configure SRM. 4

5 Pair the Protected and Recovery sites so that they can be configured for the further SRM operations. Enter the Recovery site s IP address (default port for SRM is 443), that needs to be paired/configured with Protected site. Enter the remote Recovery site logins and complete the pairing, You will see the paired sites as shown in corner pic. 5

6 Step 2: Install HP 3PAR SRA Install the HP 3PAR SRA 6.0 and rescan it using the SRM GUI at both Sites. You will see the SRA listed in SRM at both sites. Step 3: Configure ESXi hosts to Datacenters Add Datacenters that manages ESXi hosts at both sites as shown below 6

7 Add ESXi host(s) to each site that are managed by their respective datacenters by providing the ESXi host's IP address and login details. Step 3: Add 3PAR StoreServ Arrays to SRM Add Primary and Recovery storage systems to respective sites using the SRM GUI. Follow the below steps to add arrays to SRM. 7

8 Once storage systems are added and configured, they will be enabled (paired) and 3PAR storage systems devices will be automatically discovered and listed in the SRM GUI. 8

9 Step 4: Resource Mapping Resource mappings provides a convenient way to specify how Site Recovery Manager (SRM) maps virtual machine resources at the Protected site to resources at the Recovery site. Resource mapping are one of the most important tasks to be carried out before migrating the VMs from the Protected to the Recovery site. Based on resource mapping the VMs will be migrated and allocated as per the resources mapped at the respective site. Click Sites in the Site Recovery Manager interface on the protected sites and use the Resource Mappings, Folder Mappings, Network Mappings, and Placeholder Datastores tabs to configure the mappings. Map the VM Network in both directions. 9

10 Create the Folders (for placing the host and migrated VMs) at both sites and map them in both directions. Create Resource Pool at both ESXi hosts for VMs and map them at Resource Mapping tab. 10

11 Map Place Holder (local datastore) of both ESXi for VMs and map them at PlaceHolder Datastore tab. Step 5: Create VM on the datastore created over exported 3PAR LUN Make sure the VM(s) to be protected are created on the datastore that is created using the exported 3PAR storage system LUN at Protected Site. Step 6: Create Protection Group Create the Protection Group (PG) by following the below steps: 11

12 12

13 Make sure that the Protection Status under the Protection Group tab is OK. However, if you see the message with 'Not configured' status, then check the resource mapping and restore the protection group. Step7:CreateRecoveryPlan Right-click the Protection Group and click Create Recovery Plan to create a recovery plan for the Protection Group. 13

14 On successful creation of the Recovery Plan, the status displays 'Ready' indicating that the Protection Group is ready for SRM operations. 14

15 Running the Recovery Plans 1. Test This operation performs non-disruptive recovery operations. SRM communicates with HP 3PAR SRA using the remote storage information obtained during the discovery process. SRA creates snapshots of the Remote Virtual Volumes, and presents them to the recovery ESX server. During this recovery process, the VMs continue to run at the protected site. You can verify the VMs are running at the Recovery site. 15

16 2. Cleanup Perform the Cleanup operation after you have verified that the VMs are running at the Recovery site (using the Test operation). SRA cleans up previously created snapshots by unpresenting and deleting it. 16

17 3. Recovery with Planned Migration Perform a recovery operation by shutting down the VMs at the Protected site, and recovers those VMs at the Recovery site. Planned migration-srm shuts down the VMs at Protected site and unmounts the Datastores. SRA changes the status of the source Datastores to read-only, and then creates the snapshots of the source device. SRA reverses the replication direction and makes the Recovery site volumes read/write and exports the volume to the Recovery site ESXi hosts. SRM then rescans the Datastores and restarts the VMs. NOTE: Later, the snapshots taken at the Protected site (before failover) will be used for restorereplication operation by SRA. Restore replication is restoring the VMs to the original state by discarding the recent changes made at the Recovery site. You cannot perform this operation from the SRM GUI. However, you can run the following SRM commands, sequentially, to perform this operation: preparerestorereplication restorereplication 17

18 18

19 After the successful SRM Recovery (failover from the Protected site to the Recovery site), the migrated VM is up and running at Recovery site. During this process, The VM is shutdown at Protected site and brought up at Recovery site. The states of the protected and Recovery sites are changed after the successful Recovery. 19

20 4. Reprotect after the Planned Migration. Perform the SRM Reprotect operation to configure protection in the reverse direction (from Recovery site to Protected Site), as a preparation for failback to the original state. The SRA operations are similar to the planned migrations, and deletes the earlier snapshots that were created during failover from Protected site to Recovery site. 20

21 20 21

22 4. Recovery (Failback) after the Planned Migration (Failover) Shuts down the VMs at the Protected site and recovers them at the Recovery site. 22

23 After a successful SRM Recovery, the states of the Protected and the Recovery site are back to the original states. 6. Recovery with Unplanned Migration (Disaster Recovery option checked) If the user is not sure whether the Protected site data center is available or not, they will have to run the SRM recovery plan without checking the "Forced Recovery" option so that the latest data can be synced from the Protected site array(s) (if they are available) to start up the VMs at the Recovery site. Disaster recovery - If the Protected Datacenter is unavailable due to any disasters or failures, then you must run the SRM recovery plan to start up the VMs at the Recovery site. The SRA recovery process is similar to planned migration, except for the snapshot creation operations performed at the protected site. 23

24 24

25 7. Reprotect after unplanned migration Configure the protection to the reverse direction (replicate from the Recovery site to the Protected site) Note: Run the SRM Recovery (failback) again to bring the sites to their original states. 8. Recovery: Unplanned Migration with 'Forced Recovery' If the protected datacenter becomes unavailable due to some unpredicted disaster/failures, a user has to run SRM recovery plan with the 'Forced Recovery' option selected to start up the VMs at the Recovery site without syncing the latest data from the protected site. Note: 'Forced Recovery' option must to be enabled at Advanced Settings before Recovery. By default, this option is disabled. 25

26 Run Recovery with Forced Recovery selected. After the successful completion of the Forced Recovery, you must run Recovery to recover the VMs. 26

27 SRA Supported Configurations 1 to-1 Configuration (2DC Configuration) In a bidirectional 1-to-1 remote-copy configuration, each storage system in the pair functions as both the primary and backup system, and each system contains both primary and secondary volume groups. Each system provides backup for the other, according to the direction of replication specified for each volume group. 1-to-N Configuration A 1-to-N remote-copy configuration is composed of multiple remote-copy pairs. A single primary storage system can use a maximum of four backup storage systems. One primary system participates in four remote-copy pairs, one for each backup system. 27

28 N-to-1 Configuration An N-to-1 remote-copy configuration is composed of multiple remote-copy pairs. A maximum of four primary storage systems use the same backup storage system. 28

29 SLD Synchronous Long Distance configuration (3DC) A synchronous long distance (SLD) remote-copy configuration is composed of two targets: one synchronous group and one asynchronous periodic group. In SLD remote copy, one primary system uses two backup systems and participates in two remote-copy pairs, one for each backup system. In an SLD configuration, remote copy volume groups from the primary system are replicated to the two separate target arrays simultaneously. Data is replicated to one target in synchronous mode and to the second in asynchronous periodic mode. The target systems must each have appropriate network connections to the source systems to support the replication mode being used. There is no requirement that the closer of the two secondary systems be replicated to synchronously. 29

30 Troubleshooting tips for configuration: If any of the SRM operation fails with a time out error, increase the storage command time out from 300 to 1200 ms. Install the VMware Client Integration plug-in through the Web Client, which is required to deploy VMs on managed ESXi hosts in the vcenter. In case the SRM Test or Recovery operation fails with time-out error for VMware Tools, install them on the VMs to be protected. After the VM Tools are installed successfully, restart the VMs and rerun the recovery plan. HP 3PAR SRA logs can be found at vcenter Server location: C:\ProgramData\VMware\VMware vcenter Site Recovery Manager\Logs \SRAs\3PARInServ VMware SRM logs can be found at vcenter Server location: C:\ProgramData\VMware\VMware vcenter Site Recovery Manager\Logs HP 3PAR SRA install path : C:\Program Files\VMware\VMware vcenter Site Recovery Manager\storage\sra\3PARInServ 30

31 Enable Window s (Administrator) login for Web Client on both sites. It will avoid user entering login (administrator@vsphere.local and password) details every time. By checking the below checkbox a user can login and work with vcenter and SRM through the Web Client. Here are the steps to enable Windows(Administrator) login and permissions. Also refer to below screenshot sample navigation. 1. Connect to each site (Protected and Recovery) with the vsphere Web Client, using the SSO credentials configured during the vcenter installation. It will be administrator@vsphere.local and the password 2. Change the view of the vsphere Client to Inventory -> Hosts and Clusters. 3. Select the local site name (this is usually the computer name). 4. Select the Permissions tab. 5. In the window Select Users and Groups, under the section labeled Users and Groups, select the Administrator user (local machine Administrator) and click Add, then click OK. 6. Under Assigned Role, change the role (using the drop down) and select Administrator. 7. Click OK. 8. Change the view to Solutions and Applications -> Site Recovery Manager. 9. In the Sites pane, select the local SRM server. 10. Click on the Permissions tab. 11. Select Add Permission. 12. In the window Select Users and Groups, under the section labeled Users and Groups, select the Administrator user (local machine Administrator) and click Add, then click OK. 13. Under Assigned Role, change the role (using the drop down) and select Administrator. 14. Click OK. 15. In the Array Managers page, select the SRAs tab. Verify that the SRA is installed (it should list that it cannot find the paired SRA; this is expected). 16. Close the vsphere client. 17. From this point forward, you may use the local Administrator account for logging in with the vsphere client, or the SSO credentials. 31

32 Conclusion The document covers the sequence of steps to configure VMware SRM for HP 3PAR StoreServ using HP HP 3PAR SRA. Technical people with little knowledge of vcenter and SRM, can refer this document (steps) to configure SRM/SRA with 3PAR StoreServ and run recovery plans to protect VMs managed in their environment. Acronyms SSMC: StoreServ Storage Management Console SRM: Site Recovery Manager SRA: Storage Replication Adaptor VM: Virtual Machine Learn more To understand HP 3PAR Storage and VMware SRM, visit: Other references Additional documentation can be found via the following website: lang=en&cc=us&taskid=101&prodclassid=-1&contenttype=supportmanual&docindexid=64255&prodtypeid=18964&prodseriesid = Best practices for the HP 3PAR Array using VMware vcenter Site Recovery Manager: For a complete list of supported hardware and firmware versions, please view the VMware vcenter SRM Storage Partner HCL: Support Matrix for HP 3PAR SRA Versions: solutions_vmware/sra552_3par_srm60_srm5x.2015_03_19.pdf VMware references For addition information on VMware vcenter SRM, please visit VMware's website: VMware Compatibility Guide(VCG) for SRA's Get connected hp.com/go/getconnected Current HP driver, support, and security alerts delivered directly to your desktop Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only 32

33 warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. 33