HP 3PAR StoreServ Storage Replication Integration Guide with Microsoft Azure Site Recovery

HP 3PAR StoreServ Storage Replication Integration Guide with Microsoft Azure Site Recovery Document Version: 1.0 Updated Date: 17 th Dec, 2014 Applies to: Azure Administrators SCVMM Administrators Scenario Details Azure Site Recovery can help you protect important applications by coordinating the replication and recovery of private clouds across sites, whether you re protecting dozens or hundreds of virtual machines. You can protect your applications to your own second site, a hoster s site, or even use Azure as your disaster recovery site and avoid the expense and complexity of building and managing your own secondary location. Site Recovery also integrates with storage solutions such HP 3PAR StoreServ to provide Site to Site disaster recovery for Hyper-V environments by leveraging the SAN replication capabilities that are natively offered by HP 3PAR. Learn more about Azure Site Recovery here and about the SAN replication option here Site to Site Disaster Recovery Reference Architecture Microsoft Azure Site Recovery (ASR) enables protection, replication and failover of virtual machines, ensuring that mission-critical applications are always up and running. Microsoft Azure Site Recovery orchestrates replication and failover for virtual machines running on Hyper-V host servers managed by Microsoft System Center Virtual Machine Manager (SC-VMM) clouds. Advantages of using HP 3PAR StoreServ Storage in an ASR deployment include: 3PAR RC offloads host from doing additional work like replication Handling failure cases due to built-in enterprise resiliency Carrying out data integrity checks

Microsoft ASR uses the HP 3PAR Remote Copy feature through SMI-S to create and manage the Replication groups. HP 3PAR Remote Copy is a host-independent, array-based data mirroring solution that enables affordable data distribution and disaster recovery for applications. With this utility, user s can copy virtual volumes from one 3PAR StoreServ to another. HP 3PAR Remote Copy provides the following solutions: Protection Failover Reverse Protection Test Failover Figure 1. Site to site disaster recovery reference architecture

SCVMM, Hyper-V and Azure Site Recovery requirements Following SCVMM and Azure Site Recovery software is required 1. Hyper-V 2012/2012 R2 clusters on Primary and secondary site 2. System Center Virtual Machine Manager 2012 R2 with at least Update Roll Up 5 Preview. (This should be upgraded to Update Roll Up 5 once it is available) 3. Azure Site Recovery Provider (latest version) should be installed on each SCVMM server Refer to Deployment Guide for more details. How to get Access to Software HP 3PAR StoreServ Storage customers can participate in the Technology Adoption Program to try the Azure Site Recovery solution. Further information about the program can be found at these sites: 1. Azure trial subscription: http://azure.microsoft.com/en-us/pricing/free-trial/ 2. VMM UR5 Preview downloads: http://support.microsoft.com/kb/3011473 3. Azure Site Recovery Getting Started Guide: http://azure.microsoft.com/enus/documentation/articles/hyper-v-recovery-manager-san/ Storage Device Details (Primary Site and Remote Site) HP 3PAR Operating System 3.2.1 Concepts Guide, Setup Guide, User Guides, and Release Notes can be found here. Software Requirements Firmware 3PAR InForm Operating System Management 3PAR InForm Management Console Hyper-V and SCVMM Operating System SCVMM 3.2.1 (MU2) 4.6.1 Windows server 2012 R2 SCVMM 2012 R2 UR5

Hardware Requirements Array Required licenses Controllers HP 3PAR Remote Copy License N/A SMI-S Provider (Primary and Secondary Sites) SMI-S Provider is embedded inside HP 3PAR StoreServ Storage. By default no additional cimserver configuration is necessary. Verify that the replica entity policy is set for the CIM server: showcim pol If necessary, set the policy with: setcim pol replica_entity Pre-requisites and License Requirements 1. Activate the Azure account and create the site recovery vault 2. Deploy the Hyper-V host cluster on primary and remote sites with the Windows Server 2012 R2 Operating System and managed by SCVMM 2012 R2 UR5 3. Configure two HP 3PAR StoreServ Storage with the Inform OS 3.2.1(MU2) build, one on the primary and another on the remote site. Primary and Remote arrays should be connected with RC-FC or RC-IP. 4. HP 3PAR Remote Copy License should be enabled on HP 3PAR StoreServ Storage for Replication feature. 5. The primary HP 3PAR StoreServ Storage should be managed by the SC-VMM server at the primary site. The Remote HP 3PAR StoreServ Storage should be managed by the SC-VMM server at the remote site. 6. Ensure that the HP 3PAR StoreServ Storage has sufficient free space available for deployment on the Remote site. 7. Create and configure an Azure Site Recovery vault in the Azure Site Management Portal. Generate a registration key used to authenticate the SC-VMM server with the vault. 8. Install the Azure Site Recovery Provider on the SC-VMM servers, and register the servers in the vault. Verify that the primary and remote site connections to SC-VMM in Azure Site Recovery portal are working.

Configuration: 1. Add 3PAR SMI-S Provider in SC-VMM. Create storage classifications and set storage pools. 2. Create LUNs on the primary storage array and present them as cluster-shared volumes on the primary site Hyper-V cluster. 3. Create a replication group using the same cluster-shared volumes which needs to be synchronized (protected). 4. Create cloud on both primary and secondary SC-VMM and publish to ASR portal. 5. Select the Replication Group to the existing/new cloud in primary site. 6. Make sure primary and secondary pools are associated to Hosts on primary and secondary SCVMM respectively. 7. Create and configure the storage array mapping to specify the mapping between Primary storage pool and the Secondary pool. Features: 1. Protection of Replication Groups. 2. Failover of Replication Groups 3. Reverse Protect Replication Groups post Failover 4. Test Failover

ASR Logical Flow Diagram Figure2. ASR Logical Flow Diagram

Detailed Steps: Follow these steps to create volumes on the primary SCVMM In Primary SCVMM, under VMs and Services select the cluster. Right click to select -> Properties Go to Shared Volumes. Click Add-> Create Logical Unit. Select the required storage pool: provide details such as Name, Size of the LUN thin or thick logical unit. Select classification and click OK Figure 3. Create volumes on Primary SCVMM

Create Replication Group in Primary SCVMM In the primary SCVMM, go to Fabric. Under Arrays select the Primary array. Right click, select Properties -> Replication Group. Select New. Provide the Replication Group name Select the previously created LUN Click Create, then OK Figure 4. Create Replication Group

Create the Cloud in the primary SCVMM: In Primary SCVMM, shown in Figure 5. go to VMs and Services, right click on Cloud. Select Create Cloud.Provide a cloud name. Select the option as below to publish the cloud in Azure site Figure 5. Create the cloud in the primary SCVMM

Click Next to confirm your settings. As shown in figure 6, make the following selections: Select All Hosts in the Resources: option. Select the required classification. Select the Replication Group. Figure 6. Specify and confirm your settings.

Create a cloud in recovery site without assigning any replication group. In Remote SCVMM, shown in Figure 7. Go to VMs and Services, right click on Cloud. Select Create Cloud.Provide a cloud name. Select the option as below to publish the cloud in Azure site Select All Hosts in the Resources: option. Select the required classification. Do not select any replication group Figure 7. Create a cloud in the recovery site without assigning any replication group.

To see if the SCVMM servers are shown as connected to the Azure site, log in to the Azure portal, as shown in Figure 8. Figure 8. Azure portal Select Resources from the Dashboard to create and configure Storage Array Mapping. (See Figure8)

Create and Configure Storage Array Mapping To create and configure Storage Array Mapping as shown in figure 9, follow these steps: Select Server Storage. Select the Source and Target SCVMM servers by scrolling to your choice in the drop-down lists. Click the arrow to select the option MAP SOURCE AND TARGET STORAGE ARRAYS. Figure 9. Create and configure Storage Array Mapping

Select a Storage Array and Storage Pool, as shown in figure 10. Click OK (which is the icon seen below at right bottom end) Figure 10. Add Storage Array Mapping

Mapped pools are as shown below Figure 11. Mapped pools

Click on Protected items, shown in Figure 12. Select the Primary Cloud. Figure 12. Select the primary cloud

Enable cloud configuration To enable cloud configuration, follow the steps shown in Figure 13: 1. Select the Primary cloud: HP CLOUD_PRI. 2. Click, CONFIGURE PROTECTION SETTINGS. 3. Select Target, Target Location, Target Cloud, and Replication Type. 4. To save the options selected in Step 3, click SAVE at the bottom of the screen These configure cloud protection settings will be applied to all virtual machines in the cloud Figure 13. Enable cloud configuration

Protect Replication Group: In the Azure Site Recovery portal, follow these steps: 1. Click Protected Items. Select the Primary cloud and click Add Replication Group. 2. Select one or more Replication Groups, Source and Target Arrays, and Replication Types. (Synchronized\ Asynchronized) 3. Enable protection for new or existing virtual machines on the Primary cloud. VMM optimally places the virtual machine storage on the LUNs of the replication group. Azure Site Recovery orchestrates the creation of a shadow virtual machine on the secondary site with similar capacity and compute configurations. ASR helps ensure that the failed over VMs connect to the correct CSVs and LUNs, which are replicated to the secondary site. Figure 14. Add replication groups.

Enable protection completed as seen in Figure 15. Figure 15. Protection enabled.

Create VM Template in the Primary SCVMM: 1. Select a source for the template from one of the options shown in figure 16. Create the template on either an existing or new VHD. 2. Click Next. Figure 16. Create VM template.

VM Template Identity 1. Select the Identity option, as shown in figure 17. 2. Provide VM template name: 3. Click Next to open the Configure Hardware dialog box. Figure 17. Provide the VM template name.

Configure Hardware In the Configure Hardware dialog box, select your device from the Bus Configuration list, as shown in figure 18.. Figure 18. Configure Hardware: Bus Configuration

Availability: Figure 19 shows a different selection within the Configure Hardware dialog box, where you can specify high availability if desired. As shown in the figure, go to Advanced Availability -> select the option Make this virtual machine highly available Click Next. Figure 19. Specify High Availability

Confirm settings for new template To finish configuring the new VM template, confirm your settings in the Summary dialog box, shown in figure 20. 1. Review your settings before creating the template. 2. Click Create when satisfied with the template. Figure 20. Confirm settings for new template.

Create the Virtual Machine in Primary SCVMM After you have created your template, follow the steps shown in figure 21 to create the virtual machine in the Primary SCVMM. 1. Return to the Identity dialog box. 2. To create the virtual machine, select VMs and Services, shown in the bottom left corner of the dialog box. 3. Select the previously created template and provide VM Name as shown in Figure 21 4. Click Next to open the Configure Hardware dialog box. Figure 21. Create virtual machine

Select the Replication Group Use the Configure Hardware dialog box to provide hardware for the virtual machine Select the previously created Replication group Figure 22. Select Replication Group.

Select the cloud: 1. From the drop-down list, choose Select Cloud to specify a destination for the virtual machine, as shown in figure 23. 2. Click Next to see a summary of your settings. Figure 23. Select a destination in the cloud.

Confirm Settings In the Summary dialog box, confirm the settings you have made and click Create. Figure 24. Confirm Settings

Primary and secondary virtual machine results Figure25 and 26 show the virtual machines states in the Primary and Secondary sites: In the Primary SCVMM, Virtual machine state will be running or stopped, as shown in figure 25: Figure 25. Primary SCVMM In the Secondary SCVMM, the virtual machine state will be reserved, as shown in figure 26. Figure 26. Secondary SCVMM

Failover (Planned/Unplanned) In Azure Site Recovery Portal we will be able to see all virtual machines that are protected by Azure site Recovery, as shown in figure 27. We can view properties, track replication health and perform failover of replication group that contains one or more virtual machines. Login to the Azure portal. Click on Primary Cloud under Protected Items. Click on planned/unplanned Failover shown at the bottom of the portal as shown in Figure 27. Figure 27. Planned/Unplanned failover

Confirm the planned failover Click on OK Figure 27. Confirm Planned failover

Failover completed as shown in Figure 28. Figure 28. Failover completed

Primary and secondary virtual machine results after Failover is completed Figure29 and 30 show the virtual machines states in the Primary and Secondary sites: In the Primary SCVMM, Virtual machine state will be stopped, as shown in figure 29: Figure 29. Primary SCVMM after planned failover In the Secondary SCVMM, the virtual machine state will be running, as shown in figure 30. Figure 30. Secondary SCVMM after planned failover

Reverse Protect In primary site to execute a failback, the user needs to enable Reverse replication which will transfer the delta changes from the remote site to the primary site. Login to Azure Portal Select the Primary Cloud as shown in Figure 31 Figure 31. Reverse Protect

Click on Reverse Replication seen at the bottom end of Azure portal Confirm Reverse Replication of Replication Group Click on OK Figure 32. Confirm Reverse Replication

Reverse Replication completed as shown in Figure 33: Figure 33. Reverse Replication completion

Failback: Once Reverse Protection is completed, select the cloud and click on Planned Failover again to execute a Failback to the primary site. Confirm Planned Failover as shown in Figure 31 Click on OK Figure 34. Confirm Planned Failover

Planned Failover completed as shown in Figure 35 Figure 35. Planned Failover completion

Primary and secondary virtual machine results after failback Figure 36 and 37 show the virtual machines states in the Primary and Secondary sites after failback: In the Primary SCVMM, Virtual machine state will be running, as shown in figure 36: Figure 36. Primary SCVMM In the Secondary SCVMM, the virtual machine state will be stopped, as shown in figure 37. Figure 37. Secondary SCVMM

Disable Protection: Disable Protection unprotects the VMs on the primary cloud.target LUNs in secondary site will be deleted during removal process. Login to Azure portal, Select the Cloud as shown in Figure 38 Figure 38. Azure portal for Disable Protection

Click on Disable Protection as shown in Figure 39: Figure 39. Disable Protection Disable Protection completed as shown in Figure 40: Figure 40. Disable protection completion Test Failover: Select the cloud in Azure portal Click on Test Failover as shown in Figure 41 Figure 41. Test Failover

Confirm Test Failover and click on OK as shown in Figure 42 Figure 42. Confirm Test Failover

Supported Scenario Scenario Supported Notes Create and Protect Replication Yes Groups Planned Failover of Replication Yes Group Reverse Replication of Yes Replication Group Unplanned Failover of Yes Replication Group Test Failover of Replication Group Yes Functional Tests: Following table summarizes the functional requirements; Functional Test Add VM to RG Enable RG protection Unprotect RG Add VM to RG Enable RG protection Failover Unprotect RG Add VM to RG Enable RG protection Failover Reverse Unprotect RG Add VM to RG Enable RG protection Failover Reverse Failback Unprotect RG Add VM to RG Enable RG protection Test Failover Results PASS Documented for Unprotect RG PASS Documented for Unprotect RG PASS Note: Refer to the Known Issues / Limitations sections for more details on the documented scenarios.

Supported Scale and Parallel Operations for each Scenario Overall Scale Targets Following table summarizes the overall targeted scale for a large scale environment that can be protected using ASR and Storage replication Scale objects GA Target Preview Target Max number of replicating LUNs that can be orchestrated using ASR 250 125 Pass Max number of LUNs in a Replication Group 20 10 Pass Results Concurrent Operations Target (Goal for Storage Partners) Scale operation Number of LUNs that can be protected in parallel (upto a max of 10 RGs) Number of LUNs that can be failed over in parallel (upto a max of 10 RGs) GA Target Preview Target Results 10 RGs x 5 LUNs 5 RGs x Pass 5 RGs x 10 LUNs 5 LUNs Pass 10 RGs x 5 LUNs 5 RGs x Pass 5 RGs x 10 LUNs 5 LUNs Pass Scale Operations Target (Goal for Storage Partners) Scale operation Preview Target Results Time taken to failover 5 RGs with 5 LUNs each (all 1 GB LUNs) Time taken to failover 10 RGs with 5 LUNs each (all 1 GB LUNs) Time taken to failover 5 RGs with 10 LUNs each (all 1 GB LUNs) SAN FO: 10 mins ASR FO: 30 mins SAN FO: 20 mins ASR FO: 60 mins SAN FO: 20 mins ASR FO: 60 mins Pass Pass Pass Pass Pass Pass

Known Issues/Limitations: 1. Disable Protection isn t working Description: The disable protection workflow will not remove a replication group when the replication group is in a failover state. Both the primary and failover storage systems and the communication channel between them must be available for ASR to remove a replication group. If a planned or unplanned failover has occurred then the group must be recovered before it can be deleted by ASR. ASR s reverse roles workflow may be used to recover a replication group after a planned or unplanned failover. 2. Mixed Synchronization Modes: Description: HP 3PAR does not support the use of mixed synchronization modes over the same Remote Copy link. When both synchronous and asynchronous mode remote Replication Groups are required for the same pair of Storage Systems, then all groups with the same synchronization mode must use the same Remote Copy link. When used with ASR, HP 3PAR will automatically select the appropriate link (by selecting the Remote copy Target that uses the appropriate link). However, if groups are also configured outside of ASR it is possible that all available links will be configured with the same synchronization mode. If this occurs refer to the HP 3PAR Remote Copy Software User Guide (http://www.hp.com/go/3par and select the support link for your StoreServ product) for instructions on how to assign a different mode or new target to an existing Remote copy group. Contacting HP Support For worldwide technical support information, see the HP support website at: http://www.hp.com/support Before contacting HP, collect the following information: Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Detailed questions

How to collect HP 3PAR StoreServ and cimxml Logs To collect Logs, the user is expected to have the root credentials for HP 3PAR StoreServ Storage and access through SSH or access to the Service Processor of the array. To collect cimserver logs: Procedure from a SSH with root access: 1. Go to tpd location cd /var/log/tpd 2. Tar cimserver files tar cvf /common/cimserver.tar cimser* Procedure from a Service Provider to capture log files: 1. ssh spdood@<sp ip address> 2. su, password = <sp root user password> 3. Log into the command shell of the HP 3PAR StoreServ array ssh -i ~spcomm/.ssh/<cert file> root@<array IP address> where <cert file> = the file in ~spcomm/.ssh directory which name is Processor array name 4. From HP 3PAR StoreServ array prompt cd /var/log/tpd tar cvf /common/cimserver.tar cimser* exit 5. From the vsp prompt copy the cimserver.tar file scp -i ~spcomm/.ssh/<cert file> root@<array IP address>:/common/cimserver.tar cimserver.tar And share the tar file in the report. To collect cimxml logs: Create a Temp folder in C:\ drive Enable SMI-S tracing and logging Refer the Storage Service (SMI-S) Tracing and Logging link for more information Run the ASR operation for which logs are required. Share cimxml logs which would be created in Temp folder Frequently Asked Questions 1. Which type of replication do you support with ASR? Synchronous and Asynchronous Periodic 2. Do you support both 2DC and 3DC configuration with ASR?

No. Only 2DC is supported. 3. Will ASR help you give customers more flexible data protection? (e.g., fail over to another primary datacenter, to a provider site, or to Azure) Yes 4. Will ASR help you offer customers a simpler, lower-cost DR solution? Yes 5. Will ASR help you simplify DR recovery plan testing? Yes 6. What happens in an Asynchronous scenario, if the disaster happens before the synchronous time? Currently ASR supports only 1 to 1 array configuration and the delta data would be lost if the disaster happens before the synchronization. In order to avoid this, 3DC support is required, which is not supported from ASR currently. 7. What is the Security when the VMs replicated from Azure? Microsoft Azure and Azure Site Recovery follow a stringent security and privacy model. In this solution, only SCVMM Server is connected to Azure service, hyper-v hosts and storage infrastructure is not connected. All data replication is always site to site between HP 3 PAR arrays. All communication from SCVMM to Azure Site recovery is always outbound over HTTPS and can be controlled via a proxy server. Azure Site Recovery only have non-pii metadata which it uses for orchestration of DR operations. All DR operations, including storage related operations are always brokered via SCVMM which in on-premises. Please refer to following links for additional details Microsoft Azure Privacy statement: http://azure.microsoft.com/enus/support/legal/privacy-statement/ 8. What is the downtime/outage on the VMs when there is a disaster? For a Synchronous RG, the outage is the time the ASR takes to complete the failover operation. From Storage standpoint it is less than a second. For an asynchronous RG, the outage is the time the ASR takes to complete the failover operation and the periodic time set at the 3PAR side for the respective RG. Abbreviations: SCVMM ASR System Center Virtual Machine Manager Azure Site Recovery

VMM RG VM SMI-S CIM LUN SP CLI 2DC 3DC RC-FC RC-IP Virtual machine Manager Replication Group Virtual Machine Storage Management Initiative Specification Common Information Model Logical Unit Number Service Processor Command Line interface 2 Data center 3 Data center Remote Copy Fiber Channel Remote Copy Internet Protocol