HP Storevirtual 4000 Kurzanleitung

HP P4000 Storage Replication Adapter for

VMware SRM Deployment Guide

HP Part Number: AX696-96101

Published: September 2011

Edition: First

1 Using the HP P4000 SRA for VMware SRM 5

The HP P4000 SRA for VMware SRM enables full featured use of the VMware Site Recovery

Manager. Combining Remote Copy replication with VMware SRM provides an automated solution

for implementing and testing disaster recovery between geographically separated sites.

Configuring SRA

A typical SRM configuration involves two geographically separated sites with TCP/IP connectivity,

the protection site and the recovery site. The protection site is the site that is being replicated to

the recovery site for disaster recovery. Each site contains a HP P4000 SAN Solution, ESX servers,

a Virtual Center Server, and a SRM server.

Figure 1 Typical SRM configuration with two geographically separate sites

Requirements

•SAN/iQ release 9.5

•64-bit Windows OS

•.Net 3.5 will be installed if not present

•VMware vCenter running on two sites

Installing SRA

First install the VMware SRM at each site, and then install the HP P4000 SRA on the SRM server

at each site. Once the HP P4000 SRA is installed, SRM can discover replicated volumes between

sites by configuring arrays in SRM. Configuring HP P4000 SAN Solution arrays in SRM requires

the following:

•The IP addresses of the SAN/iQ managers. More than two addresses can be input by using

a comma or semicolon separator.

•The same user name and password in each site. This is the administrative user name and

password configured in the CMC for the HP P4000 SAN.

The user at the recovery site must have full permissions on the management group but can be

limited to read only on all other permissions.

Configuring SRA 3

Installing Application Aware Snapshot Manager (optional)

Install and configure Application Aware Snapshot Manager on both Primary and Remote site

VCenter servers. For installation instructions, see HP P4000 Application-Aware Snapshot Manager

Deployment Guide

The replication schedule controls the application aware snapshot integration. If the schedule has

managed enabled then that enables the application managed snapshot integration, where in SRA

takes managed snapshots in syncOnce and reports to SRM the recovery points with VM snapshots

using VmImageConsistencyEnabled flag. If the schedule has managed disabled then that disables

the application managed snapshot integration as no managed snapshots are taken. Exceptions:

The SRA can handle any changes in configuration, but this is a normal, baseline scenario.

How the HP P4000 SRA Works with VMware SRM 5

The HP P4000 SRA has four primary functions for SRM.

•Test Failover - A Test scenario that checks failover conditions and parameters. This will create

temporary writable sources at the Backup Site. In the case of HP P4000, Smart Clone Volumes

will be created.

•Failover - Transitioning production services from a Primary Site to a Backup Site, either with

the Primary Site available or not.

•Reprotect - After a Failover, planned or unplanned, transitioning production services from the

Backup Site back to the Primary Site. This entails reversing Replication so Replication goes

from Backup to Primary Site, doing a Failover in Reverse, and then reversing Replication again

so replication goes from the Primary to Backup Site.

These functions each depend on specific configuration information in a HP P4000 SAN Solution

management group.

Array and volume discovery

SRM gets information from the HP P4000 SRA about what volumes are being replicated by the

SAN/iQ software. SRM then compares that list to the volumes it recognizes in a VMware

environment.

For normal SRM operation, a replicated volume needs to have a Remote Copy schedule with

completed remote copies at a different HP P4000 SAN Solution management group under a remote

volume that is not mounted at the remote site. This is a standard HP P4000 SAN Solution Remote

Copy configuration.

For instructions on how to configure Remote Copy schedules, see the Remote Copy User Manual

which can be found on the HP P4000 Management Software DVD. The latest version of this

document can be found by browsing to http://www.hp.com/support/manuals. Click Disk Storage

Systems in the storage section and then select HP P4000 G2 SAN Solutions. The same information

is available from the online help in the HP P4000 Centralized Management Console.

Volumes recognized by the HP P4000 SRA

Volumes must be configured with scheduled remote snapshots or they will not be considered for

SRM by the SRA. The HP P4000 SRA recognizes the scheduled remote snapshots as replicated

LUNs for SRM to manage. Volumes that are being remote copied only manually are not updated

consistently enough to be useful for disaster recovery and SRM.

If a volume has scheduled remote snapshots, and you create an ad hoc manual remote snapshot

of that volume, then the HP P4000 SRA will recognize the manual remote snapshot along with the

scheduled remote snapshots. Such ad hoc remote snapshots may be useful to test failover with a

more recent copy than the schedule has, or to push the latest updates to the remote site before a

foreseeable disaster occurs.

4 Using the HP P4000 SRA for VMware SRM 5

IMPORTANT: A volume in the protected site should not have two or more schedules going to

multiple volumes on the same remote Management Group.

Volumes ignored by the HP P4000 SRA

Remote snapshots within the same HP P4000 SAN Solution management group are ignored. These

snapshots are not considered disaster recovery copies since they are usually created to clone a

volume in the HP P4000 SAN Solution, and copies that reside on the same SAN are not useful for

disaster recovery.

Testing failover at the recovery site

SRM performs test failovers at the recovery site when requested. When test failovers are requested,

the HP P4000 SRA will perform the steps listed.

1. Select the replicated volumes.

2. Identify the latest complete Remote Copy snapshot.

3. Delete any temporary writable space on that snapshot to ensure an unedited snapshot is

presented to ESX servers.

Use this snapshot to create a smart clone.

4. Configure authentication for ESX servers to directly mount smart clones.

5. When testing stops, to conserve space on the SAN, delete the temporary writable space that

was used during the test.

Actual failover at the recovery site

In the event of a disaster, the SRM can perform actual failover when requested to. When actual

failover is requested the HP P4000 SRA will perform the steps listed.

1. Select the replicated volumes.

2. Identify and remove any incomplete remote copies that are in progress and present the most

recent completed Remote Copy as a primary volume.

3. Convert remote volumes into primary volumes and configure authentication for ESX servers to

mount them.

If an actual failover does not run completely for any reason, the failover can be called many times

to try to complete the run. If, for example, only one volume failed to restore and that was due to

a normal snapshot being present, the snapshot could be manually deleted and the failover be

requested again.

Reprotect at the recovery site

After a failover, the SRM can perform reprotect when requested to. When actual reprotect is

requested the HP P4000 SRA will perform the steps listed.

1. On the original protected site (which will become recovery site after reportect is executed)

a. Pause any schedules going from primary volume to remote.

b. Remove any ESX Server assignment.

c. Change primary volume to backup

2. On the original recovery site (which will become protected after reprotect is executed)

• Create remote schedule with the primary volume as the target or un-pause remote

schedules.

3. Delete any SRA created snapshots and schedules.

How the HP P4000 SRA Works with VMware SRM 5 5

Troubleshooting the HP P4000 SRA

Table 1 Troubleshooting the HP P4000 SRA

SolutionCauseProblem

Install the HP P4000 SRA and restart

the VMware Site Recovery Manager

Service.

The HP P4000 SRA might not be

installed or the SRM service has not

restarted since the HP P4000 SRA was

installed.

The HP P4000 SAN array does not

appear in the drop down list of arrays

for SRM.

Create a Remote Copy schedule for all

volumes that are to be managed by

SRM.

Volumes are only reported as

replicated to SRM if they have a

Remote Copy schedule.

SRM does not see the volumes that are

replicated.

Create authentication groups for any

CHAP authentication required on the

SRM does not store or pass CHAP

passwords to the HP P4000 SRA. For

CHAP-authenticated ESX servers are

failing to perform test failovers or

actual failover. recovery site before running test failover

or failover.

CHAP authentication to work, the

authentication group with correct

password must be already configured

on the SAN/iQ management group.

Configure a network that can route from

SRM servers to the HP P4000 SAN

SRM servers running the HP P4000

SRA must be able to route TCP/IP

The HP P4000 SRA fails to connect to

the SAN.

Solution, and verify the user account

configured in SRM.

traffic to the SAN that is to be

managed and must have a valid

username and password.

Do not mount primary and remote

volumes at the same site at the same

time.

Both the primary and remote volume

might be mounted at the same site.

When the HP P4000 SAN array is

discovered, an error message states

there are duplicate LUNs.

TIP: Read the messages that are displayed in the SRM UI during various functions as they provide

useful information.

6 Using the HP P4000 SRA for VMware SRM 5

2 Using the HP P4000 SRA for VMware SRM 1.x/4.x

The HP P4000 SRA for VMware SRM enables full featured use of the VMware Site Recovery

Manager. Combining Remote Copy replication with VMware SRM provides an automated solution

for implementing and testing disaster recovery between geographically separated sites.

Configuring SRA

A typical SRM configuration involves two geographically separated sites with TCP/IP connectivity,

the protection site and the recovery site. The protection site is the site that is being replicated to

the recovery site for disaster recovery. Each site contains a HP P4000 SAN Solution, ESX servers,

a Virtual Center Server, and a SRM server.

Requirements

•SAN/iQ release 9.5 and earlier

•32-bit or 64-bit Windows OS

•VMware vCenter running on two sites

Installing SRA

First install the VMware SRM at each site, and then install the HP P4000 SRA on the SRM server

at each site. Once the HP P4000 SRA is installed, SRM can discover replicated volumes between

sites by configuring arrays in SRM. Configuring HP P4000 SAN Solution arrays in SRM requires

the following:

The IP addresses of the SAN/iQ managers. More than two addresses can be input by using a

comma separator.

•A user name and a password for each site.

NOTE: This is the HP P4000 SAN user name and password as configured in the CMC.

The user at the recovery site must have full permissions on the management group but can be

limited to read only on all other permissions.

How the HP P4000 SRA Works with the SRM 1.x/4.x

The HP P4000 SRA performs three main functions for SRM. These functions each depend on specific

configuration information in a HP P4000 SAN Solution management group.

Array and volume discovery

SRM gets information from the HP P4000 SRA about what volumes are being replicated by the

SAN/iQ software. SRM then compares that list to the volumes it recognizes in a VMware

environment.

For normal SRM operation, a replicated volume needs to have a Remote Copy schedule with

completed remote copies at a different HP P4000 SAN Solution management group under a remote

volume that is not mounted at the remote site. This is a standard HP P4000 SAN Solution Remote

Copy configuration.

For instructions on how to configure Remote Copy schedules, see the Remote Copy User Manual

which can be found on the HP P4000 Management Software DVD. The latest version of this

document can be found by browsing to http://www.hp.com/support/manuals. Click Disk Storage

Systems in the storage section and then select HP P4000 G2 SAN Solutions. The same information

is available from the online help in the HP P4000 Centralized Management Console.

Configuring SRA 7