1

IBM System Storage SAN Volume Controller

Storage Replication Adapter for VMware SRM

Installation and Users Guide

Version 1.2

2

About this guide The IBM System Storage SAN Volume Controller Storage Replication Adapter for VM-ware SRM Installation and Users Guide provides information that helps you install and con-figure Storage Replication Adapter.

Who should use this guide The IBM System Storage SAN Volume Controller Storage Replication Adapter for VM-ware SRM Installation and Users guide is intended for system administrators or others who install and use the VMware Site Recovery Manager with IBM System Storage SAN Volume Controller. Before installing and using the Storage Replication Adapter for SAN Volume Controller, you should have an understanding of storage area networks (SANs), SAN Vo-lume Controller Metro/Global Mirror Copy Services and the capabilities of your storage units. For more information on how to use Metro/Global Mirror Copy Services, refer to IBM System Storage SAN Volume Controller Administration guide that can be downloaded from http://www.ibm.com.

3

Table of Contents Functional Block Diagram 4

Installation overview 5

System requirements for the IBM System Storage SAN Volume Controller Storage Replication

Adapter software 5

Installing the IBM System Storage SAN Volume Controller Storage Replication Adapter for VMware

SRM software 6

Configuring the Storage Replication Adaptor 11

User Privileges for Storage Replication Adaptor Configurations 16

Creating the Target Volumes and Metro/Global Mirror Relationships 16

Other Important Configuration Requirements 16

Uninstalling IBM System Storage SAN Volume Controller Storage Replication Adapter Software 16

Adding Array Managers to VMware Site Recovery Manager 17

TestFailover Procedure 25

Failover Procedure 26

Failback Procedure 27

Managing Failback 27

Failback Scenario 27

To manually execute a failback scenario 27

References 28

4

Functional Block Diagram

VMware

SITE RECOVERY

MANAGER

SRM INTERFACES

command.pl

discoverArrays.pl

discoverLuns.pl

testFailover.pl

failover.pl

IBMStorageService

CIM

AGENT

(Master Console or

Embedded CIMOM)

IBM

SVC

SRA Configuration

5

Installation overview 1. The steps for implementing the IBM System Storage SAN Volume Control-

ler Storage Replication Adapter for VMware SRM software must be com-pleted in the correct sequence. Before you begin, you must have experience with or knowledge of administering a SAN Volume Controller. For more in-formation on administering IBM SAN Volume Controller refer to IBM SAN Volume Controller Best Practices and Performance Guide-lines(http://www.redbooks.ibm.com/redbooks/pdfs/sg247521.pdf)

Complete the following tasks:

1. Verify that the system requirements are met.

2. Install the SAN Volume Controller Consoles one for the protected site and one for the recovery site SAN Volume Controller, if they are not already installed. If the SAN Volume Controller nodes are running firmware v4.3.1.7 or higher, SRA can connect to the embedded CIMOM running on the SVC nodes, thus eliminating a need for separate external Master Console.

3. Install the IBM System Storage SAN Volume Controller Storage Replication Adap-ter software.

4. Verify the installation.

5. Create appropriate sized target volumes on the recovery site SAN Volume Control-ler. Create Metro/Global Mirror relationships between the source and target volumes and add the relationships to Consistency Groups as needed. For more information on volume creation and Metro/Global Mirror Copy Services follow the link on the Ref-erences page at the end of this document

6. A user created on SVC with appropriate privileges.

Note: For more information on how to install IBM SAN Volume Controller Console fol-low the link on the References page at the end of this document

System requirements for the IBM System Storage SAN Volume Con-

troller Storage Replication Adapter software Ensure that your system satisfies the following requirements before you install the IBM Sys-tem Storage™ SAN Volume Controller Storage Replication Adapter for VMware SRM software on a Windows Server 2003 operating system.

The following software is required:

6

1. SAN Volume Controller Console software version 4.3.1.613 or later installed on the IBM System Storage Productivity Center or master console.

2. If the SAN Volume Controller is at code level version 4.3.1.7 or higher, the SRA can connect to the embedded CIMOM running on the SVC device, which would eliminate the need for an external Master Console server

3. SAN Volume Controller nodes with software version 4.3.0 or later installed with the Metro/Global Mirror and FlashCopy features enabled.

4. IBM System Storage SAN Volume Controller Storage Replication Adapter software version 1.2.

5. VMware vSphere Virtual Center Server v4.0 or later with Site Recovery Manager v4.0 Plug-in must be installed before you install the SAN Volume Controller Sto-rage Replication Adapter.

Note: For more information on how to install VMware Virtual Center Server and Site Re-covery Manager Plug-in, refer VMware Virtual Center installation and administration guide.

Installing the IBM System Storage SAN Volume Controller Storage

Replication Adapter for VMware SRM software This section includes the steps to install the IBM System Storage SAN Volume Controller Storage Replication Adapter for VMware SRM software.

You must satisfy all of the prerequisites that are listed in the system requirements section before starting the installation. Perform the following steps to install the IBM System Sto-rage SAN Volume Controller Storage Replication Adapter for VMware SRM software on the Windows server.

2. Log on to Windows as an administrator.

3. Double click on IBMSVCSRA.exe that you downloaded to start the installa-tion process. The Welcome screen is displayed.

7

4. Clicking Next will display the License agreement panel. You can click Cancel at any time to exit the installation.

8

5. Read the license agreement information. Select whether you accept the terms of the license agreement, and click Next. If you do not accept, you cannot continue with the installation.

6. The Customer information page is displayed. Enter the appropriate user and organi-zation names.

7. On the next page the install location is displayed. To change the default installation location click Change and enter the installation location of your choice and click Next.

9

10

8. The installation start page is displayed. If you are ready to start the installation click Install

9. The following page indicates the progress of the install process.

11

10. When the install process is done, click Finish on the following page

Configuring the Storage Replication Adaptor The installation of IBM SAN Volume Controller SRA creates a short-cut named “IBMSVCSRAUtil.exe” on the desktop.

Important: The configuration utility must be run on recovery site VC to configure the recovery site SRA only.

Double clicking the short-cut will bring-up the window below.

12

The configuration utility has to be configured before the user configures SRM with the array. The environment can be configured to be a pre-configured environment, where the user pre-creates the snapshot target volumes (and/or R3 recovery volumes) and pre-maps the volumes to the ESX server(s) at the recovery site, a non-precreated environments where the SRA creates/deletes and maps snapshot volumes during test failover and R3 recovery operations. The configuration utility also allows the user to instruct SRA to do an automatic switch of copy direction during failover operations.

For pre-created, and no automatic switch of remote copy relationships’/consistency groups’ copy direction, select the options on the configuration utility screen as follows .

Note: For pre-created and R3 recovery configurations automatic switch of remote copy relationships’/consistency groups’ copy direction is not possible. So even if the user tries to check the “Auto. Switch Replication” check box, the utility throws a warning and unchecks the box.

13

The pre-configured environments option assumes the Metro Mirror and/or Global Mirror relationships and/or consistency groups are synchronized, the snapshot target (R3 recovery) volumes created, FC maps (with background copy greater than 0) created between the Metro Mirror/Global Mirror target and snapshot volumes, and map the snapshot volumes are mapped to the ESX server(s) at the recovery site.

The FC maps are recommended to be incremental so that SRA will just have to re-fresh the FC map(s) during test failover and R3 recovery operations.

Note: The pre-created environments will always do an R3 recovery. The status of FlashCo-py mappings (and/or ConsistencyGroups) must be “idle_or_copied”, before the user can in-itiate test failover and failover operations.

Once the user has selected the required options, click OK. To confirm/check the configured options, re-start the IBM SVC configuration utility.

For non pre-created environments, the user needs to un-check the “Pre-Configured Env.” options, and input the appropriate values for Test MDisk Group ID, Failover Policy, Failov-er MDisk Group ID and SpaceEfficient Mode options. Example configuration screen below

14

Click OK to confirm the selections. To confirm and/or change the options re-start the confi-guration utility. The current selections will be displayed under “Current Settings” as shown below.

Click OK to submit changes or click Cancel to leave the selections unchanged. If “R2” is input for Failover Policy any input in “Failover MDisk Group ID” field is ignored.

15

For R2 recovery and automatic relationships’/consistency groups’ copy direction switch, the selections should be as shown below

For R2 recovery and no automatic relationships’/consistency groups’ copy direction switch, the selections should be as shown below

16

User Privileges for Storage Replication Adaptor Configurations For R2 failover policy, where the SRA creates the snapshot volumes and maps the volumes to the ESX server(s) at the recovery site, during test failover operation(s), a “superuser” privileged user is needed. If, the replicated targets are pre-mapped to the recovery site ESX server(s), then a “CopyO-perator” privileged user will suffice for failover operation(s).

For R3 failover policy, where the SRA creates the snapshot volumes and maps the volumes to the ESX server(s) at the recovery site, during test failover and failover operation(s), a “superuser” pri-vileged user is needed.

For Pre-Configured Env, where the user pre-creates the needed volumes and maps those volumes to the recovery site ESX server(s), a “CopyOperator” privileged user will suffice.

Creating the Target Volumes and Metro/Global Mirror Relationships

You must create equal number of target VDisks (for Metro/Global Mirror targets), on the recovery site SAN Volume Controller, to source VDisks.

Important: Create Metro/Global Mirror relationships between the sources and target and VDisks, and add them to Consistency Groups as needed. For more information on Metro/Global Mirror Copy Services refer to IBM SAN Volume Controller Advanced Copy Services Implementation (http://www.redbooks.ibm.com/redbooks/pdfs/sg247574.pdf)

Important: Before you start using the SAN Volume Controller Storage Replication Adap-ter, make sure the Metro/Global Mirror relationships and/or Consistency Groups are in consistent synchronized state.

Other Important Configuration Requirements

IBM System Storage SAN Volume Controller Storage Replication Adapter only supports secure ports for CIM agents and only one SAN Volume Controller device managed by each SAN Volume Controller Console. If you choose to use the embedded CIMOM running on a SAN Volume Controller device, with firmware level 4.3.1.7 or higher, the SRA can be pointed directly to the SVC device, thus eliminating the need for an external Master Console Server

Uninstalling IBM System Storage SAN Volume Controller Storage

Replication Adapter Software You must use the Storage Replication Adapter installation executable, IBMSVCSRA.exe, to uninstall the IBM System Storage SAN Volume Controller Storage Replication Adapter software from the Windows server. Perform the following steps to uninstall the software:

17

1. Log on to the Windows server as the local administrator.

2. Double-click on the IBMSVCSRA.exe and select Remove.

3. Click Finish on the final screen to complete the un-installation. If necessary, In-stallShield will prompt the user to re-start the system.

Adding Array Managers to VMware Site Recovery Manager To add arrays to VMware Site Recovery Manager execute the following.

1. Log on to the VMware Virtual Center Server machine

2. Click Site Recovery on the “Home” page

3. Click Configure option next to Array Manager in the Setup panel. The following di-alog is displayed

18

4. Click Add in the Configure Array Manager panel.

5. Enter array manager information on the Add Array Manager screen. Reinstate the connection information for the array. Click Connect.

• Display Name – Enter the name of your array.

• Manager Type - From the pull down menu, select the type of array you are using

• CIM Server Address – Enter the IP address and the port number of the CIM agent. For example, 192.168.15.2:5989, where 5989 is the CIM agent's port number. Users can also use fully qualified domain name instead of IP address of the CIM agent.

When using an embedded CIMOM, enter the IP address of the SAN Volume Controller device with port number 5989.

Important: IBM System Storage SAN Volume Controller Storage Replica-tion Adapter only supports secure ports for CIM agents and only one SAN Volume Controller device managed by each SAN Volume Controller Con-sole

• User Name – Enter the user name configured on the CIM agent.

19

• Password - Enter the password configured for the user selected above, on the CIM agent. When using an embedded CIMOM please use the password configured for the user created on SAN Volume Controller device.

Once all the required information is input, click Connect, this initiates SRM to discover the SAN Volume Controller device at the specified IP address and if successful, the following page is displayed

Click OK, to add the protected site “Array” to SRM.

20

21

Review the protected and recovery site SAN Volume Controller ID information in the Con-figure Array Manager window and click Next to add the recovery site “Array” information

22

Click Add to input recovery SAN Volume Controller’s CIM information and click Connect

23

Confirm the recovery site “Array ID” and click OK

24

Check for a Green Icon like the one on the page above to confirm a successful configuration of Arrays on protected and recovery sites. Click Next

25

Review and confirm that all the relevant Datastore Groups are displayed correctly and click Finish

Note: All SAN Volume Controller replicated VDisks that are participating in SRM and be-long to the same Metro/Global Mirror Consistency Group, are displayed under a single Da-tastore Group. So, extra care needs to be taken while adding replicated VDisks to Consis-tency Groups such that all logically similar VDisks (for example all VDisks that are being used by a single Virtual Machine and/or an application running on the VM can be added to the same Consistency Group).

TestFailover Procedure Depending on the SRA configuration, the user might have to perform additional tasks for the test failover procedure to work.

R2/R3 Failover Policy

The IBM SystemStorage SAN Volume Controller SRA completely automates the TestFai-lover procedure. During this procedure, the SRA creates FlashCopy target volumes in the MDisk Group the user specified in the SRA configuration. The only pre-requisite this pro-cedure needs, from the Storage Replication Adapter’s perspective, is to have enough free space available in the MDisk group.

26

This procedure doesn’t require anything specific to the Storage Replication Adapter, be done by the user as long as all the steps and pre-requisites mentioned in this document are carried out properly.

Pre-Configured Environment

For this configuration, the user needs to pre-create the R3 set of volumes, create the Flash-Copy relationships between R2 and R3 volumes, and map R3 volumes to the recovery site ESX server(s).

Failover Procedure Depending on the SRA configuration, the user might have to perform additional tasks for the failover procedure to work.

R2 Failover Policy with Auto. Copy Direction Switch

This procedure doesn’t require anything specific to the Storage Replication Adapter, be done by the user as long as all the steps and pre-requisites mentioned in this document are carried out properly. After the recovery (failover) is complete, the Metro Mirror and/or Global Mirror copy direction is switched (only if the protected site SAN Volume Controller is online).

R2 Failover Policy without Auto. Copy Direction Switch

If the “Auto Switch Replication” option is not selected, the Metro Mirror and/or Global Mir-ror relationships and/or Consistency Groups are stopped and their status changed to “idl-ing”.

R3 Failover Policy

The IBM SystemStorage SAN Volume Controller SRA completely automates the failover procedure. During this procedure, the SRA creates FlashCopy target volumes in the MDisk Group the user specified in the SRA configuration. The only pre-requisite this procedure needs, from the Storage Replication Adapter’s perspective, is to have enough free space available in the MDisk group.

Pre-Configured Environment

For this configuration, the user needs to pre-create the R3 set of volumes, create the Flash-Copy relationships between R2 and R3 volumes, and map R3 volumes to the recovery site ESX server(s).

27

Failback Procedure

Managing Failback

Managing failback using SRM is a manual process given that the protection site could have completely different hardware and network configuration after a disaster occurs. Failback can be managed like any planned server migration.

Failback Scenario

The following failback scenario uses SRM as a failback tool to Site A after execut-ing a recovery plan R1 at Site B in recovery mode for recovered virtual machines.

To manually execute a failback scenario

1. Delete recovery plan R1 at Site B.

2. If Site A still has DR protection configured for the protection groups P1 in recovery plan R1, delete protection groups P1 at Site A.

3. If it is not already in place, use the vSphere Client at Site B to establish Site A as the secondary site for Site B. (If Site A does not have SRM installed, install SRM at Site A.)

4. Establish appropriate array replication from Site B to Site A for the datastores con-taining recovered virtual machines. If the Metro/Global Mirror relationships’ and/or Consistency Groups’ copy direction was switched during Failover (with protected site SAN Volume Controller online) skip ii below

i. Mask the VDisks on the SAN Volume Controller from the ESX server at Site A.

R2 Failover Policy without Auto. Copy Direction Switch

Start the Metro/Global Mirror relationships and/or Consistency Groups with “-clean” flag with primary volumes now being auxiliary i.e. “-primary aux”.

R2 Failover Policy with Auto. Copy Direction Switch

No action needed

R3 Failover Policy

a) Delete the original Metro Mirror and/or Global Mirror relationships and/or Consistency Groups between R1 and R2 volumes on the re-covery site SAN Volume Controller.

28

b) Create new Metro Mirror and/or Global Mirror relationships (and Consistency Groups) from R3 to R1 volumes.

ii. Wait till their states change to “consistent synchronized”.

5. Create protection group or groups P2 at Site B to protect recovered virtual machines to Site A.

6. At Site A, create a recovery plan R2 for the protection group or groups P2.

7. After the user has determined that the virtual machines have been fully replicated to Site A, execute recovery plan R2 at Site A in test mode.

8. If the test is successful, execute recovery plan R2 in recovery mode.

9. At this point, the user may want to re-protect recovered virtual machines to Site B:

10. Delete recovery plan R2 at Site A.

11. Delete protection group(s) P2 at Site B.

12. Mask the VDisks on the SAN Volume Controller from the ESX server at Site B.

13. Create protection group(s) P3 at Site A to protect recovered virtual machines from Site A to Site B.

Create a recovery plan R3 at Site B for the groups.

References

1. IBM SAN Volume Controller Advanced Copy Services Implementation

(http://www.redbooks.ibm.com/redbooks/pdfs/sg247574.pdf)

2. IBM SAN Volume Controller Best Practices and Performance

Guidelines (http://www.redbooks.ibm.com/redbooks/pdfs/sg247521.pdf)