Double virtual machine density

Aid in increasing storage and server consolidation efforts by up to 50% Monitor and manage HP 3PAR Storage from within the vSphere console Preserve and reclaim free space by leveraging the HP 3PAR ASIC and HP 3PAR Thin Persistence Boosts VMware vSpheres return on investment (ROI) by 50% Enable the reduction of storage provisioning and management time by up to 90%This white paper outlines best practices on how to set up HP 3PAR Storage with VMware SRM as well how to takeadvantage of HP 3PARs unique features to create a world class virtualized IT and application infrastructure. Theinformation contained in this document should be used along with the documentation set provided by HP for the HP3PAR Storage system, HP 3PAR Storage operating system (Inform), and the documentation provided by VMware forvCenter, Site Recovery Manager, and other related products.Figure 1: HP 3PAR Storage for VMware vSphere Environments

HP 3PAR Storage offers the simplest administration of any storage platform available, allowing you to reduceprovisioning and management time by up to 90%. In addition, several HP 3PAR Storage features uniquely simplifyadministration of VMware vSphere environments by enhancing visibility into storage resources and offering superiorgranularity and control over snapshots and rapid online recovery.Integrating HP 3PAR Storage systems with VMware vSphere 5 also enables its users to double virtual machine density onphysical servers, monitor and manage HP 3PAR Storage volumes to create point-in-time, VM and application aware,disk-based snapshots from within the vSphere console, and preserve and reclaim free space by leveraging the HP 3PARASIC and HP 3PAR Thin Persistence to detect the writing of zeros and unallocated storage in a thin provisioned virtualmachine. With these unique features, HP 3PAR Storage boosts VMware vSpheres return on investment (ROI) by 50% byenabling you to optimize your data center infrastructure, simplify storage administration, and maximize virtualizationsavings. (Figure 1)HP 3PAR arrays continue to capture the SPC-1 benchmark due to its architecture with multiple storage controller nodesand wide striping over available disk drives which is crucial to VMwares demand for low latency I/O response and HP3PARs ability to double VM density compared to other arrays on the market today with fewer servers.Target audience: IT Administrators planning to leverage HP 3PAR Storage within a VMware vSphere 5 environmentusing VMware vCenter SRM for disaster recovery.This white paper describes testing performed in April 2012.

Evolution of business continuity for VMware environments

A key advantage of server virtualization is that it consolidates many dedicated physical servers to virtual machines thatshare a smaller pool of physical servers. However, these consolidated virtual environments increase the complexity ofdisaster recovery by adding an extra layer of virtualization which increases the variables required to plan, test, andmanage a disaster recovery scenario. No longer is a simple mapping of application-to-host-to-volume-to-replicationsufficient to manage and protect the data center. As a result, customers require specific and easy to use businesscontinuity and disaster recovery solutions for the virtual machine infrastructure.With the right business continuity solutions in place, virtual machines can actually ease disaster recovery challenges. Byencapsulating applications and operating systems in a generic virtual machine wrapper, IT departments can leverage thehomogeneity of the virtual machine environment to reduce costs, ease administration, and increase agility. Physicalserver technology evolves over time, requiring administrators to implement new server builds and drivers to supportnewer hardware. However, virtual machines offer distinct advantages since they remain predictable and unchanging,even while the physical hardware beneath them is upgraded.Virtual machines sever the ties between the virtual environment and the unpredictable physical environment, makingthem very portable. The portability of virtual machines allows administrators to develop disaster recovery plans that aremore flexible in terms of the hardware deployed at both the primary and the recovery site. In addition, the capitalexpenditure outlay for equipment and the recurring management costs associated with that hardware both decreasewith a consolidated environment. As a result, more and more enterprises are starting to see virtual machines as an idealway to address disaster recovery challenges and are accelerating the move toward virtual machine adoption to meetbusiness continuity requirements. This shift has increased the need for business continuity solutions specificallydesigned for virtualized environments to ease implementation and management of disaster recovery.

OverviewWhen supported with the correct underlying storage platform, server virtualization delivers greater consolidation,administrative efficiency, and cost savings. As a result, server virtualization is not only transforming the data center, butalso the businesses that those data centers fuel. However, these transformative results depend on enterprise storage todeliver the performance, availability, and flexibility to keep up with the dynamic and consolidated nature of virtualizedserver environments.HP 3PAR Storage was built from the ground up to exceed the economic and operational requirements of even the mostdemanding and dynamic IT environments, and to support a converged infrastructure by providing the SAN performance,scalability, and availability that clients need to transform the data center. The next generation of federated Tier 1storage, HP 3PAR Storage delivers 100% of the agility and efficiency demanded by virtual data centers and cloudcomputing environments as part of an HP Converged Infrastructure. It does this through an innovative systemarchitecture that offers storage federation, secure multi-tenancy, built-in thin processing capabilities, and autonomicmanagement and storage tiering features that are unique in the industry.

HP 3PAR Remote Copy for disaster recovery

HP 3PAR Remote Copy Software provides enterprise and cloud data centers with autonomic replication and disasterrecovery technology that allows the protection and sharing of data from any application simply, efficiently, andaffordably. Remote Copy Software dramatically reduces the cost of remote data replication and disaster recovery byleveraging thin copy technology, enabling multi-site and multi-mode replication with both midrange and high-endarrays, and reducing the need for professional services. Its supported native IP implementation eliminates the need forprotocol extenders or converters for long distance replication.HP Remote Copy Software offers fast, autonomic disaster recovery configuration that can be set up and tested inminutes, from a single window. With support for synchronous long distance replication, customers now have anaffordable, multi-site alternative for achieving low recovery time objectives (RTOs) and zero-data-loss recovery pointobjectives (RPOs) with complete distance flexibility.1

VMware vCenter Site Recovery Manager

VMware vCenter SRM provides business continuity and disaster recovery protection for VMware virtual environments.Protection can range from individual virtual machines (VMs) residing on a single, replicated datastore to all the VMs in adata center. VMware SRM helps IT administrators plan, test, and execute the recovery of virtual machines between theprotected site and the recovery site.VMware SRM coordinates the recovery process with HP 3PAR Remote Copy Software to ensure that the virtual machinesat the protected site are shut down cleanly (in the event that the protected site virtual machines are still available whenrecovery is invoked) so that the replicated virtual machines can be recovered and powered up at the recovery site.Recovery of protected virtual machines to the recovery site is guided by a recovery plan that specifies the order in whichvirtual machines are started up. The recovery plan also specifies network parameters, such as IP addresses, ensures thereplicated storage holding the protected VMs is brought online and presented to the recovery hosts properly, and cancontain user-specified scripts that can be executed to perform custom recovery actions.After a recovery has been performed, the running virtual machines are no longer protected. To address this reducedprotection, SRM supports a reprotect operation for virtual machines protected on array-based storage. The reprotectoperation reverses the roles of the two sites after the original protected site is back up. The site that was formerly therecovery site becomes the protected site and the site that was formerly the protected site becomes the recovery site. Atthis point a planned migration back to the original site can be scheduled, if desired.

Optimize service levels / rebalance resources by dragging

Cut storage power requirements

Cut server power requirements

Using VMware SRM for complex DR planning and management

Management of a multi-layered, highly virtualized disaster recovery environment is challenging if the systemadministrator must coordinate actions through multiple management applications across the various components ofthe solution. For example, mapping the applications and virtual machines down through storage fabric zoning to thephysical array volumes and VMware VMFS file systems can be difficult because it is often a many-to-many relationship.To accomplish this, the administrator must map the array volumes between sites, and again those volumes must beassociated with physical servers and their specific virtual machines. If a VMware vSphere administrator migrates virtualmachines between datastores, this can easily disrupt the carefully crafted mapping for array-based replication. Failureto monitor and maintain the end-to-end mappings results in loss of availability of the application at the remote site.To alleviate these challenges associated with manual disaster recovery planning, VMware introduced VMware vCenterSite Recovery Manager (SRM) to provide end-to-end management of array-based replication and virtual machinefailover for VMware vSphere environments. VMware SRM enables system administrators to discover which arrayvolumes are protected via replication, to manage the testing and production failover of these volumes, and to restartthe virtual machines at the remote site. As part of the storage discovery, VMware enumerates the volumes on each siteand ensures that, for any given virtual machine requiring remote replication, all the necessary virtual machinecomponents, datastores, and disk assets are properly mapped and accessible at both sites.

A storage platform with built-in self management and optimization features that does not require administrator intervention

Implementing VMware SRM with HP 3PAR Storage

HP 3PAR Remote Copy makes configuring the replication piece of the disaster recovery solution simple and possible tobe completed without the need to hire professional services with a basic knowledge of VMware and HP 3PAR RemoteCopy. Once the HP 3PAR arrays are installed, replication between the two sites can be easily configured. Remote Copycan be configured, managed, and tested in a matter of minutes. The need for costly and prolonged professional servicesengagements, common with other replication technologies, can be avoided. Special extenders or converters to permitlong distance replication are also not needed.

HP 3PAR Remote Copy configuration

Setting up a basic HP 3PAR Remote Copy configuration can be accomplished by first selecting and configuring the portsto be used for Remote Copy functions, the ports can either be Fibre Channel or Ethernet. Once the port type is selected,change the Connection Mode to Remote Copy over Fibre Channel (RCFC) or Remote Copy over IP (RCIP), and thenproceed with configuring the interface. It is recommended and a best practice to configure two ports (of the same type)on each HP 3PAR array from the same node pair. For more information on this topic please reference the HP 3PARRemote Copy Software User's Guide which can be found in the For more information section of this paper.Once the ports are configured for Remote Copy, establish an array relationship by configuring the logical links. ForVMware SRM a one-to-one Remote Copy relationship is recommended. While other relationships other than one-to-oneare possible, a one-to-one relationship is a best practice and shown in this paper. A one-to-one Remote Copyrelationship involves two HP 3PAR Storage systems. Depending on how the one-to-one Remote Copy relationship isconfigured, one server can serve as the primary (source) server and the other as the backup server (unidirectional), orboth servers can serve as both the primary and backup servers (bidirectional). In order to enable SRM to be able to failover to either site, a bidirectional relationship is required.

In the Manager Pane, click Remote Copy.

In the Common Actions panel, click New Configuration.The New Remote Copy Configuration wizard appears.Under Select a Topology, click 1-1.Under Assign Systems, click a storage server icon. In the menu that appears, select a storage server to assign.Repeat for the other storage server icon. (Figure 3)Optionally, define the Systems Location and/or the Target Names.Click Next.

Figure 3: Configure Relationship

8.9.

A graphical representation of each system's Remote Copy ports appears under Create Links. Click and drag fromone port on one system to a port on the other system. Repeat for the second port. (Figure 4)Configure interconnect linksa. For IP links, in the IP Settings groups for each system/port, all fields are automatically populated based on thelink relationship established under Create Links.I.II.

(Optional) Enter the gateway address for each system/port.

(Optional) Click Apply to test the link configuration, or Ping to test the communication between the links.b. For Fibre Channel links, in the Settings group for each system/port:I.Connection Type - Select Point for point-to-point mode or Loop for arbitrated loop mode.II.Configured Rate - Select 1, 2, 4 Gbps, or Auto (default).III.Click Apply to test the link configuration, or Ping to test the communication between the links.10. Click Next.Figure 4: Configure Links

10

11. In the Source group section:

a. System - Select the system on which the Remote Copy group will reside.b. Domain - Select the domain in which the Remote Copy group will reside. If not using a Virtual Domainconfiguration, this step can be skipped.c. Group - Enter a name for the Remote Copy group.d. Enable Start group after completion (default).12. In the Backup group section:a. Name - The system NOT selected as the source system, automatically appears.b. Mode - Select Synchronous (default).13. Click Add.14. Repeat the steps above for the other array using it as the source array and the array just configured above as thebackup array.Once the array relationship is established, the next step is to select the virtual volumes that will be replicated.1.2.3.

4.

Select a Remote Copy group from the Group list.

Under the Source Volume list, select a virtual volume.Under the Backup Volume list:a. Select either Existing or New.I.Existing, select a backup virtual volume.II.New:1) Name - Enter a name for the backup virtual volume.2) CPG under User CPG - Select a CPG from which the volume's user space is allocated.3) CPG under Copy CPG - Select a CPG from which the volume's copy space is allocated.4) (Optional) In the Allocation Warning and Allocation Limit text boxes, enter the appropriate information.Click Add.

The two 3PAR systems are now configured in a bi-directional one-to-one remote copy configuration.

Site Recovery Manager installation

VMware vCenter Site Recovery Manager integrates tightly into VMware vSphere Client. When installed, a newmanagement view is available in VMware vSphere Client where administrators can create, manage, and execute disasterrecovery plans. The Protection Setup and Recovery Setup options will guide you through the wizard-based process ofconfiguring VMware SRM. The first step in the Protection Setup process is to establish a connection between theprotected and the recovery site (Figure 5).1.2.3.4.5.

Run the VMware vCenter Site Recovery Manager installer and go through the windows and the agreement until theDestination Folder window is reached.In this window, select the location to install SRM; by default, it is installed intoC:\Program Files (x86)\VMware\VMware vCenter Site Recovery Manager\Click Next.On the vSphere Replication window select Install vSphere Replication.Click Next

11

6.

In the following window, complete the vCenter Server Credentials for the local site similar to Figure 5. This willregister SRM with vCenter.

Figure 5: Entering Credentials for VMware vSphere Registration of SRM

The next several screens will assist in either creating or importing a certificate. The certificate is used by SRM forauthentication. Either Automatically generate a certificate or Use a PKCS#12 certificate file depending on howyou want to configure this step.

12

10. In the VMware vCenter Site Recovery manager Extension window, fill in the information for the local site as in Figure6.a. Local Site Name: User defined string for the site name. This name will show up in SRM.b. Administrator E-mail: Email address of the site administrator. This is needed to receive notification of eventsthat happen on the site.c. Additional E-mail: This field is optional. Enter another email address here if a second person is needed toreceive notifications.d. Local Host: Select the IP of the local instance of vCentere. Listener and API Listener Ports: Leave the defaults unless there is a specific reason not to use the defaults.11. Click NextFigure 6: Info for SRM extension registration with vCenter Server

13

12. In the database configuration window (Figure 6), select the Database Client and the Data Source Name (DSN) of thelocal or remote database server. If there is not a DSN available or created for this instance, one will need to becreated. A system DSN is required, and in most cases it should refer to the localhost connection of the vSpheredatabase.a. If creating a new DSN, the newly added DSN will not show up in the Data Source Name drop down list and willneed to be entered in manuallyb. Enter in the Username and Password as well as change the Connection Count and Max. Connections asneeded.Figure 7: VMware vCenter Site Recover Manager database information

13. Click Next.

14. Installation of SRM will now start once the Install button is clicked.15. Once the installation has finished successfully, click the Finish button.

14

16. Login to the vCenter Server and enable the plugin using the Plug-in Manager, see Figure 8. To do this selectDownload and InstallFigure 8: VMware vCenter Site Recover Manager Extension available as a plugin

17. Repeat at the other site.

VMware SRM is now installed at both sites and imported into VMware vCenter.

HP 3PAR Storage Replication Adapter (SRA) Software for VMware vCenter

SRM installationBefore completing the configuration of VMware SRM, the HP 3PAR Storage Replication Adapter (SRA) Software forVMware vCenter SRM (Site Recovery Manager) needs to be installed. This adapter integrates VMware SRM with HP 3PARStorage and replication software to provide a complete and integrated business continuity solution. The VMwarevCenter Site Recovery Manager communicates with HP 3PAR Remote Copy Software for storage replication through theHP 3PAR SRA. The HP 3PAR SRA provides information about Remote Copy volume groups that exist in HP 3PAR Storagesystems to Site Recovery Manager. SRM identifies datastores and raw device mappings (RDMs) in the Remote Copyvolume group (also referred to as consistency groups). These datastores and RDMs have corresponding virtual volumesin the Remote Copy volume group and replicates between the protected site and the recovery site.1.

2.

HP 3PAR SRA requires the following companion packages to be installed on the host before installation:a. VMware vCenter Site Recovery Manager 5.0.b. Microsoft .NET Framework 3.5 Service Pack 1 or abovec. Microsoft Visual C++ 2008 Redistributable Package (x86)Double-click the installation executable to launch the wizard. Click Next to continue.

3.4.

a. The HP 3PAR SRA and VMware vCenter Site Recovery Manager must be installed on the same host.Click I Agree to acknowledge the User License Agreement and click Next to continue.Click Next to start the installation.

5.

After the installation is complete, restart the VMware vCenter Site Recovery Manager service to ensure that HP3PAR SRA is recognized by SRM. We will configure SRM to use the 3PAR SRA in the Configure the 3PAR StorageReplication Adapter section.

15

For more information about the plugin and where to download it for free:https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=HP_3PAR_SRM

Site Recovery Manager configuration

Once both sites have SRM installed and registered in vCenter, then the configuration of SRM can begin. To begin, start onone of the sites, and switch to the Site Recovery plugin view (Solutions and Applications Site Recovery). The GettingStarted with Site Recovery Manager screen will be the starting point for each of the following subsections. (Figure 9)Figure 9: Getting Started with Site Recovery Manager Window

Connect the sites

The first step is to connect the two sites.1.2.

Select Configure Connection.

Enter in the Address and Port of the remote vCenter Server. Once finished click Next.

3.

a. You may need to accept certificate errors to proceed.

On the vCenter Server Authentication windows, enter in the Username and Password of the vCenter Server. Oncefinished click Next.

4.

16

a. You may need to accept certificate errors to proceed.

Several tests will now be run. If all is successful, then click Finish.

5.

You will now be prompted again for the credentials to the remote site. Enter in those credentials and accept anySecurity Warnings that appear. Once login is successful, the second site will appear in the Sites field as in Figure 10.If a local certificate is being used, mark it to accept always.

Figure 10: Both sites are now connected

Set Up Inventory Mappings

Once the sites are connected, the Inventory Mappings should be defined. Mappings provide default locations andnetworks for use when placeholder virtual machines are initially created on the recovery site.Unless you intend to configure these mappings individually for each member of the group, configure inventory mappingsbefore creating protection groups. Inventory mappings provide a convenient way to specify how resources at theprotected site are mapped to resources at the recovery site. These mappings are applied to all members of a protectiongroup when the group is created and they can be reapplied as needed, such as when new members are added. If aprotection group is created and no mappings exist, the administrator must configure each protected virtual machineindividually. While SRM does not enforce an inventory mapping requirement, a virtual machine cannot be protectedunless it has some form of valid inventory mappings for networks, folders, and compute resources. Inventory mappingscan be created at both the protection and recovery site.1.2.

3.4.5.

Select a Site from the Sites section and then click Resource Mappings.Click Configure Mapping and configure a mapping to the appropriate resources for the protected virtual machineswhen they are recovered to the other site. For example, a cluster at Site A is protected by a cluster at Site B. Oncefinished, click OK.Select a Site from the Sites section and then click Folder Mappings.Click Configure Mapping and configure a mapping to the appropriate location in the resource mapping for theprotected virtual machines when they are recovered to the other site. Once finished, click OK.Select a Site from the Sites section and then click Network Mappings.

17

6.

Click Configure Mapping and configure a mapping to the appropriate network to be used for the protected virtualmachines when they are recovered to the other site. Once finished, click OK.

7.

Repeat steps for the second site.

Assign Placeholder Datastores

Once the Resource, Folder, and Network mappings are completed, Placeholder Datastores need to be set up. APlaceholder Datastore contains information about a protected virtual machine in a protection group at the recovery site.These placeholders are added to and managed as part of the recovery sites inventory.After determining which datastore will hold placeholders, SRM reserves a place for protected virtual machines in therecovery site's inventory. This is done by creating a subset of virtual machine files on the specified datastore at therecovery site and then using that subset to register the placeholder virtual machine with the recovery site vCenter. Thepresence of these placeholder virtual machines in the recovery site inventory provides a visual indication to SRMadministrators that the virtual machines are protected. They also indicate to vCenter administrators that the virtualmachines can be powered on and will start consuming local resources when SRM tests or runs a recovery plan.Placeholder datastores must be established at both sites. Having placeholder datastores at both sites enablesreprotection by providing a location to store the identity and inventory location of the old production machine in anempty shell of a virtual machine. This placeholder virtual machine is created during the recovery workflow when theproduction virtual machine is deactivated. This placeholder virtual machine can then be subsequently used andeventually removed as the recovery process is completed.Placeholder virtual machines behave like any other member of the recovery site vCenter inventory except that theycannot be powered on. When a placeholder is created, its folder and compute resource assignments are derived frominventory mappings established at the protected site. Note that any changes made to the placeholder virtual machinesin the recovery site inventory override settings established by inventory mapping. These settings are preserved duringthe recovery or test.When evaluating datastores in which to establish placeholder datastores, consider the following:

For clusters, the placeholder datastores must be visible to all hosts in the cluster. Placeholder datastores cannot be replicated.To configure the placeholder datastores:1. Select a site from the Sites section and then click Placeholder Datastores.2. Click Configure Placeholder Datastore.3.4.

Expand the folders to find a datastore to designate as the location for placeholder datastores.Select an appropriate datastore. Once finished, click OK.a.

5.

18

Only datastores that are valid choices are displayed. For example, replicated datastores are not suitable forholding placeholder files, so such datastores are not presented as choices.Repeat for the second site.

Configure the 3PAR Storage Replication Adapter

After connectivity is established between the two sites, the HP 3PAR Storage systems need be configured as arraymanagers in vCenter so that SRM can discover the replicated devices, compute datastore groups, and initiate storageoperations.Before configuring the array managers, ensure that the 3PAR SRAs that were installed earlier are loaded into vCenter. Todo this, perform the following:1.2.3.

On the left side of the Site Recover plugin in vCenter, select Array Managers.Select the SRAs tab.Ensure the HP 3PAR SRA Software version 5.0 that was installed earlier is displayed (Figure 11). If it is not, click theRescan SRAs button.

4.

Repeat for the second site.

Figure 11: HP 3PAR SRA loaded into vCenter

Now that the SRAs are properly loaded, the array managers can be configured.1.2.

Under the Array Managers configuration group select the Getting Started tab and click Add an Array Manager.In the Array Manager Information window, enter the following:a. Display Name: Use any descriptive name that makes it easy to identify the storage associated with this arraymanager.b. SRA Type: Select HP 3PAR SRA Software version 5 (default).c. Click Next.

Click Finish once the Add Array Manager wizard is successful.

5.

Repeat steps 1 through 4 for the other site and its array.

NoteIt is only needed to configure array based replication for the vSphere Cluster andthe HP 3PAR array at the same site. It is not needed to configure array basedreplication for a vSphere cluster at one site with the array at the other site as it isnot directly attached to that storage and using its resources.What needs to be configured in this section:Site As vSphere Cluster to Site As HP 3PAR ArraySite Bs vSphere Cluster to Site Bs HP 3PAR Array

20

Once completed, both array managers are displayed (Figure 13).

Figure 13: Array Managers configured in SRM

21

Enable SRM to manage the arrays. (Figure 14)

1.2.3.4.

Select one of the arrays from Array Managers

Click on the Array Pairs tabUnder the Actions column click EnableIt is only needed to click Enable on one of the sites, the other site is automatically enabled.

Figure 14: Array pairs enabled for use with SRM

22

Create a Protection Group

Protection groups provide coverage for all virtual machines in the group. For array based replication, SRM organizesdatastore groups to collect all files associated with protected virtual machines. These datastore groups are thenassociated with protection groups. All virtual machines in a datastore group replicate their files together and failovertogether. It is possible to have a virtual machine with files on different datastores. In such a case, SRM combines thedatastores that contain files for a single virtual machine to create a datastore group.1.2.

From Sites in the left pane select the Getting Started tab and click Create a Protection Group (Figure 15).In the Select Site and Protection Group Type windowa. Select the Local site from the Protection Site group box.b. Select Array based replication (SAN) from the Protection Group Type group boxc.a.

Select that appropriate array from the list for the local site.Click Next.

Figure 15: Example of a Protected Site configuration

3.4.5.6.

In the Select One or More Datastore Groups select the datastore(s) to be protected by SRM. All VMs under theselected datastore(s) will be protected. Click Next.In the Name and Description window, enter in an appropriate Protection Group Name and Description. Click NextIn the Ready to Complete window, click Finish.Repeat for the second site. Once finished, a screen similar to Figure 16 will be displayed for each of the protectiongroups.

23

NoteIf a virtual machine cannot be mapped to a folder, network, and resource pool onthe recovery site, it is listed with a status of Mapping Missing, and aplaceholder cannot be created for it and SRM will not protect that VM.If after configuring the protection groups if there are unresolved devices with avirtual machine, those issues need to be resolved before continuing. A possibleexample of this would be an attached ISO that is not available at the remote site.

Figure 16: Successful protection configuration

In the Host and Clusters view in vCenter for each site, placeholders are now visible for each of the protected VMs at thatsite. (Figure 17)

Create a recovery plan

In order to recover a protection group in the case of a planned or unplanned event, a recovery plan needs to beestablished that lays out how virtual machines are recovered. A basic recovery plan includes a number of prescribedsteps that use default values to control how virtual machines in a protection group are recovered at the recovery site.Users can customize the plan to meet their needs for their environments. Recovery plans are different from protectiongroups in that recovery plans indicate how virtual machines in one or more protection groups are restored at therecovery site.1.2.3.4.5.6.

From Sites in the left pane select the Getting Started tab and click Create a Recovery Plan.Select the Local site from the Recovery Site group box and click Next.In the Select Protected Groups window, select the Protection Group(s) to include in the recovery plan. Click Next.In the Test Networks window, select the Recovery Network for the VMs. Click Next.In the Name and Description window, enter in an appropriate Recovery Plan Name and Description. Click Next.In the Ready to Complete window, click Finish.

7.

Repeat steps 1 through 6 for the other protection groups. Once finished, there should be a list of recovery plan(s)with a Plan Status of Ready (Figure 18).

25

Figure 18: Recovery Plan

VMware SRM is now configured and should now be tested before performing a planned or unplanned recovery to ensurethat everything was configured properly.

Testing recovery plans

Once VMware SRM configuration is complete, testing of the recovery plan can be initiated at any time without impactingthe virtual machines at the protected site.When a recovery plan is tested, a test network and a temporary snapshot of replicated data at the recovery site is used.No operations are disrupted at the protected site.Testing a recovery plan runs all the steps in the plan with the exception of powering down virtual machines at theprotected site and forcing devices at the recovery site to assume ownership of replicated data. If the plan requestssuspension of local virtual machines at the recovery site, they are suspended during the test. A test makes no otherchanges to the production environment at either site.

26

PrerequisitesBefore proceeding with the testing, as well as performing any planned and unplanned failover events, you need toensure that your HP 3PAR arrays are running one of the following versions of the InForm OS.

2.3.1 MU5 with patch P32 or greater

3.1.1 MU1 with patch P13 or greaterFailing to meet this requirement will cause testing and failover actions to fail with failure message Invalid Metadatawhen trying to create a writeable snapshot as part of a recovery action. If you are unsure of the version of your HP 3PARStorage system or need the InForm OS upgraded, contact your HP Services representative or your HP partner(hp.com/large/contact/enterprise/index.html) for assistance.The appropriate licensing for the HP 3PAR arrays is also required. Please contact your HP Sales Representative if youhave any questions or are missing the required licenses listed below on your HP 3PAR arrays. The exact licenses neededdepend on the array and disk configurations. Refer to the HP 3PAR Software Products QuickSpecs(http://h18000.www1.hp.com/products/quickspecs/13964_na/13964_na.html) for more information.

In the Testing Confirmation window, determine whether to enable the Replicate recent changes to recovery siteoption when the plan runs. Enabling this option ensures the recovery site has the latest information, but thesynchronization may take additional time. Click Next.Click Start on the confirmation window.Progress and completion of the recovery test can be viewed by looking at the Recovery Steps tab. (Figure 19)

27

Figure 19: Recovery Plan Testing

4.

Once the test has completed successfully, click Cleanup to remove the test environment and reset the plan to theReady state.

Recovery and reprotect

After ensuring that all the recovery plans test successfully, the Recovery and Reprotect actions can be leveraged whenneeded for an actual failover for a planned migration or as part of disaster recovery. During failover, Site RecoveryManager shuts down virtual machines, promotes the replicated copy of storage, attaches it to the ESX servers at therecovery site, brings up the virtual machines, and generates reports about the recovery process.All that is required to begin a recovery in the event of a real disaster is to click the Recovery button. Although SiteRecovery Manager provides notification when it loses contact with the primary site, the administrator must initiaterecovery. The administrator declares that a disaster requiring recovery has occurred, and then Site Recovery Managertakes over and executes its recovery process.1.

Click Recovery Plans in the left pane, select a recovery plan and click Recovery.

2.3.4.5.

Confirm the request to initiate recovery.

Since this is a Planned Migration, select that option from the Recovery Type group box, and click Next.Click Start on the confirmation window.Progress and completion of the recovery test can be viewed by looking at the Recovery Steps tab.

28

Once finished, the Recovery Complete message will be displayed similar to Figure 20. The VM from Site B is now runningon Site A (Figure 21).Figure 20: Successful site recovery

Figure 21: VM from site B running on site A

Now that the primary site has been migrated to the recovery site it is no longer protected against failure. To reestablishthe protection of the VMs at the new site, the Reprotect action must be executed. Reprotection results in array-basedSRM protection groups and recovery plans being reconfigured to work in the opposite direction. This provides the optionof failing virtual machines back to the original site, if desired. Note that the reprotect workflows are designed for usewhen the physical infrastructure at both sites is intact. If the failover was unplanned and physical site and equipmentloss has occurred (specifically the replicated storage layer) at one of the sites, then the reprotect workflows cannot beutilized.

29

Reprotecting is only applicable in cases where array based protection has been established, a failover has beencompleted, and there is a need to re-establish protection. If an unplanned failover has occurred, a planned failover mustbe completed before attempting reprotection. This action is needed to ensure the original protected site has beenrestored, and a planned failover is completed to ensure both sites are fully aware of the current status. If errors occurduring such an attempted planned failover, the errors must be resolved, and the failover re-run until the failoversucceeds. Running a planned migration after a failover will NOT affect the running of the recovered VM's but is needed toallow SRM to reset certain aspects of the configuration in readiness for reprotect.

NoteRunning a planned migration after a failover will NOT affect the running of therecovered VMs but is needed to allow SRM to reset certain aspects of theconfiguration in readiness for reprotect.

To initiate a reprotect of a site:

1.2.3.4.

Click Recovery Plans in the left pane, click the Recovery Plan that was executed previously, and then clickReprotect.Select I understand that this operation cannot be undone and click Next.Click Start on the confirmation window.Once complete, the recovery sites plan will be modified to work in the reverse direction and set back to normal.Now both VMs are on the same site and protected.

FailbackTo fail Site Bs VM back to Site B, just rerun the same recovery plan, and then reprotect again on Site B to re-establishprotection.

30

Site failure validation

Figure 22: Diagram of hardware setup

In the following scenario, we will test a power failure at Site A. A power failure at Site A means that all communicationwith Site A over the Ethernet network will be lost (Figure 23). Once Site B sees that it has lost communication with Site A,a message on Site B (Figure 24) will be displayed indicating it has lost communication with Site A.

31

Figure 23: Failure at Site A

Figure 24: Lost of connectivity to Site A

32

Just as in the Recovery and reprotect section, the same steps will be performed to recover Site A with a few differences.Since this is an unplanned failure, select Disaster Recovery in the Recovery Type group box (Figure 25). By selectingDisaster Recovery, the recovery actions will attempt to talk to the Protected Site to replicate any recent changes,however if it cannot it will continue if there are errors. In a planned migration, errors would stop the operation.Figure 25: Executing a Recovery Plan in a Disaster Recovery scenario

If a Disaster Recovery is performed and the Recovery Site cannot talk to the Protected Site during a failover, a messagedialog will be displayed (Figure 26) and the Recovery action will have to be run again once the sites are reconnected toensure the VMs at the failed site have been shut down and placeholders are created for them.Figure 26: Disaster Recovery warning that SRM could not shut down the original protected VMs

33

The recovery completed successfully (Figure 27) and the warning shown in Figure 26 was displayed sincecommunication between Site A and Site B was lost. Site As VM is now running on Site Bs ESXi 5 cluster (Figure 28)Figure 27: Failure Site A Recovery Steps

Figure 28: Failure Site A VM running on Site Bs ESXi cluster

Upon reestablishment of site connectivity, VMware SRM alerts the user that the Recovery action needs to be re-run inorder to complete the recovery action (Figure 29).Figure 29: Failure - Recovery required to complete failover

Upon completion of the recovery, all the steps in the Recovery Steps will be marked as Already Done or Success and allthe VMs at Site A are shut down and place holders are created for them. The option to Reprotect the VMs on Site B isnow available and should immediately be run to protect the VMs and is needed before the VMs can be recovered backonto Site A.

34

Implementing a proof-of-conceptAs a matter of best practice for all deployments, HP recommends implementing a proof-of-concept using a testenvironment that matches the planned production environment as closely as possible. In this way, appropriateconfiguration and solution deployment can be obtained. For help with a proof-of-concept, contact an HP Servicesrepresentative or your HP partner (hp.com/large/contact/enterprise/index.html)

SPC-1 benchmarkSPC-1 benchmark is designed for business-critical applications that process large and multiple complex transactionsand workloads such as VMware vSphere 5.The HP 3PAR P10000 V800, T800 and F400 Storage systems have set individual performance records by achievingSPC-1 benchmark results of 450,212 IOPS for the V800; 224,989 IOPS for the T800; and 93,050 IOPS for the F400. Thestorage performance council website may be referred to for further details on these records and tests performed by SPCat storageperformance.org/results/benchmark_results_spc1.HP 3PAR Storage offers unique mixed workload support so that transaction and throughput-intensive workloads runwithout contention on the same storage resources, alleviating performance concerns and dramatically cuttingtraditional array costs. HP 3PAR Storage is massively parallel and autonomically load balanced, making simplifiedstorage administration, high performance and consolidation easily achievable by any organization. HP 3PAR Storage issuitable for a mission-critical virtualized environments like VMware that relies on top storage array performance.Table 1. HP 3PAR SPC-1 performance

Tested storage configuration

HP 3PAR P10000 V800

HP 3PAR T800

HP 3PAR F400

SPC-1 IOPS

450,212.66

224,989.65

93,050.06

Total ASU* capacity (GBs)

230,400GB

77,824GB

27,046GB

SPC-1 Price/performance $/SPC-1 IOPS

$6.59

$9.30

$5.89

Data protection level

Mirroring

Mirroring

Mirroring

Identifier

A00109

A00069

A00079

Version

1.12

1.10.1

1.10.1

SummaryCoupling the simplicity and efficiency of HP 3PAR Remote Copy with HP 3PAR Replication Adapter for VMware vCenterSite Recovery Manager enables HP 3PAR customers to easily implement VMware vCenter Site Recovery Manager forend-to-end management of array-based replication and failover of virtual machines. The combination of HP 3PARRemote Copy and VMware vCenter Site Recovery Manager lets customers build resilient utility computinginfrastructures, protect applications at a lower cost, and recover data more quickly and efficiently compared totraditional disaster recovery offerings.Not only does leveraging HP 3PAR Storage enable seamless integration with VMware SRM for simplified disasterrecovery, but is also enables organizations using VMware vSphere with HP 3PAR several other key benefits. Using HP3PAR Storage with VMware vSphere storage enables its users to double virtual machine density on physical servers,placing twice as many VMs on physical servers as with traditional storage platforms. Also the tight integration ofVMware vCenter Server and the HP 3PAR Management Software Plug-In for VMware vCenter allows administrators tomonitor and manage HP 3PAR Storage volumes to create point-in-time, VM-and application-aware, disk-basedsnapshots from within the vSphere console. Lastly with HP 3PAR Thin Persistence, as the ESXi host writes zeros to theVMDK file, the zeros are detected in-line by the ASIC, and no space is allocated for the VMDK in the thin provisioned

To help us improve our documents, please provide feedback at hp.com/solutions/feedback.

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The onlywarranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing hereinshould be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omiss ions contained herein.Microsoft is a U.S. registered trademark of Microsoft Corporation.