IBM System Storage SAN Volume Controller

Storage Replication Adapter for VMware SRM Installation and Users Guide
Version 1.2

1

About this guide
The IBM System Storage SAN Volume Controller Storage Replication Adapter for VMware SRM Installation and Users Guide provides information that helps you install and configure Storage Replication Adapter.

Who should use this guide
The IBM System Storage SAN Volume Controller Storage Replication Adapter for VMware 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 Volume 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.

2

Table of Contents Functional Block Diagram Installation overview 5 4 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 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 TestFailover Procedure 25 Failover Procedure Failback Procedure Managing Failback Failback Scenario 26 27 27 27 27 17 16 To manually execute a failback scenario References 28 3 .

pl discoverArrays.pl testFailover.pl discoverLuns.Functional Block Diagram VMware SITE RECOVERY MANAGER SRM INTERFACES command.pl IBMStorageService CIM AGENT (Master Console or Embedded CIMOM) IBM SVC 4 .pl SRA Configuration failover.

The steps for implementing the IBM System Storage SAN Volume Controller Storage Replication Adapter for VMware SRM software must be completed in the correct sequence.Installation overview 1. Create appropriate sized target volumes on the recovery site SAN Volume Controller.redbooks. If the SAN Volume Controller nodes are running firmware v4. if they are not already installed. Note: For more information on how to install IBM SAN Volume Controller Console follow the link on the References page at the end of this document System requirements for the IBM System Storage SAN Volume Controller Storage Replication Adapter software Ensure that your system satisfies the following requirements before you install the IBM System Storage™ SAN Volume Controller Storage Replication Adapter for VMware SRM software on a Windows Server 2003 operating system. Verify the installation. 5. Create Metro/Global Mirror relationships between the source and target volumes and add the relationships to Consistency Groups as needed. 2.3. 4. SRA can connect to the embedded CIMOM running on the SVC nodes. Before you begin.pdf) Complete the following tasks: 1.ibm. For more information on volume creation and Metro/Global Mirror Copy Services follow the link on the References page at the end of this document 6.1.com/redbooks/pdfs/sg247521. Verify that the system requirements are met. you must have experience with or knowledge of administering a SAN Volume Controller. A user created on SVC with appropriate privileges. For more information on administering IBM SAN Volume Controller refer to IBM SAN Volume Controller Best Practices and Performance Guidelines(http://www. 3.7 or higher. thus eliminating a need for separate external Master Console. Install the IBM System Storage SAN Volume Controller Storage Replication Adapter software. Install the SAN Volume Controller Consoles one for the protected site and one for the recovery site SAN Volume Controller. The following software is required: 5 .

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. refer VMware Virtual Center installation and administration guide. SAN Volume Controller Console software version 4.0 Plug-in must be installed before you install the SAN Volume Controller Storage Replication Adapter.1.1.3. IBM System Storage SAN Volume Controller Storage Replication Adapter software version 1. which would eliminate the need for an external Master Console server 3. 5. installa- 6 .exe that you downloaded to start the tion process.0 or later with Site Recovery Manager v4. 2.3.0 or later installed with the Metro/Global Mirror and FlashCopy features enabled. The Welcome screen is displayed.1.2. 2.7 or higher. SAN Volume Controller nodes with software version 4. Note: For more information on how to install VMware Virtual Center Server and Site Recovery Manager Plug-in. Double click on IBMSVCSRA. 3. the SRA can connect to the embedded CIMOM running on the SVC device. Log on to Windows as an administrator. VMware vSphere Virtual Center Server v4. Perform the following steps to install the IBM System Storage SAN Volume Controller Storage Replication Adapter for VMware SRM software on the Windows server.3. 4. If the SAN Volume Controller is at code level version 4.613 or later installed on the IBM System Storage Productivity Center or master console.

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

If you do not accept. Read the license agreement information. To change the default installation location click Change and enter the installation location of your choice and click Next.5. 6. On the next page the install location is displayed. you cannot continue with the installation. and click Next. 7. 8 . The Customer information page is displayed. Enter the appropriate user and organization names. Select whether you accept the terms of the license agreement.

9 .

The following page indicates the progress of the install process.8. If you are ready to start the installation click Install 9. 10 . The installation start page is displayed.

exe” on the desktop. 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. Double clicking the short-cut will bring-up the window below.10. 11 . Important: The configuration utility must be run on recovery site VC to configure the recovery site SRA only. When the install process is done.

the utility throws a warning and unchecks the box. So even if the user tries to check the “Auto. and no automatic switch of remote copy relationships’/consistency groups’ copy direction. Switch Replication” check box. Note: For pre-created and R3 recovery configurations automatic switch of remote copy relationships’/consistency groups’ copy direction is not possible.The configuration utility has to be configured before the user configures SRM with the array. 12 . The environment can be configured to be a pre-configured environment. select the options on the configuration utility screen as follows . For pre-created. The configuration utility also allows the user to instruct SRA to do an automatic switch of copy direction during failover operations. 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.

and map the snapshot volumes are mapped to the ESX server(s) at the recovery site. the snapshot target (R3 recovery) volumes created. Failover MDisk Group ID and SpaceEfficient Mode options. To confirm/check the configured options. 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. re-start the IBM SVC configuration utility. Failover Policy. The status of FlashCopy mappings (and/or ConsistencyGroups) must be “idle_or_copied”. Example configuration screen below 13 . click OK. before the user can initiate test failover and failover operations. FC maps (with background copy greater than 0) created between the Metro Mirror/Global Mirror target and snapshot volumes. Note: The pre-created environments will always do an R3 recovery. Once the user has selected the required options. and input the appropriate values for Test MDisk Group ID.The pre-configured environments option assumes the Metro Mirror and/or Global Mirror relationships and/or consistency groups are synchronized. the user needs to un-check the “Pre-Configured Env.” options. For non pre-created environments.

The current selections will be displayed under “Current Settings” as shown below.Click OK to confirm the selections. 14 . If “R2” is input for Failover Policy any input in “Failover MDisk Group ID” field is ignored. Click OK to submit changes or click Cancel to leave the selections unchanged. To confirm and/or change the options re-start the configuration utility.

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

the replicated targets are pre-mapped to the recovery site ESX server(s). For R3 failover policy. then a “CopyOperator” privileged user will suffice for failover operation(s). For more information on Metro/Global Mirror Copy Services refer to IBM SAN Volume Controller Advanced Copy Services Implementation (http://www. where the user pre-creates the needed volumes and maps those volumes to the recovery site ESX server(s). Important: Create Metro/Global Mirror relationships between the sources and target and VDisks. 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. 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.redbooks. to source VDisks.com/redbooks/pdfs/sg247574. where the SRA creates the snapshot volumes and maps the volumes to the ESX server(s) at the recovery site. a “CopyOperator” privileged user will suffice. during test failover and failover operation(s).7 or higher. For Pre-Configured Env. the SRA can be pointed directly to the SVC device. and add them to Consistency Groups as needed. IBMSVCSRA. with firmware level 4.ibm. during test failover operation(s). If. If you choose to use the embedded CIMOM running on a SAN Volume Controller device.3.1. where the SRA creates the snapshot volumes and maps the volumes to the ESX server(s) at the recovery site. make sure the Metro/Global Mirror relationships and/or Consistency Groups are in consistent synchronized state.pdf) Important: Before you start using the SAN Volume Controller Storage Replication Adapter. a “superuser” privileged user is needed. on the recovery site SAN Volume Controller.User Privileges for Storage Replication Adaptor Configurations For R2 failover policy. Perform the following steps to uninstall the software: 16 . to uninstall the IBM System Storage SAN Volume Controller Storage Replication Adapter software from the Windows server. Creating the Target Volumes and Metro/Global Mirror Relationships You must create equal number of target VDisks (for Metro/Global Mirror targets). a “superuser” privileged user is needed.exe.

Log on to the Windows server as the local administrator.1. If necessary. Click Finish on the final screen to complete the un-installation. 2. The following dialog is displayed 17 .exe and select Remove. Double-click on the IBMSVCSRA. Adding Array Managers to VMware Site Recovery Manager To add arrays to VMware Site Recovery Manager execute the following. Log on to the VMware Virtual Center Server machine 2. 1. InstallShield will prompt the user to re-start the system. 3. Click Configure option next to Array Manager in the Setup panel. Click Site Recovery on the “Home” page 3.

When using an embedded CIMOM. Click Connect. Enter array manager information on the Add Array Manager screen. 18 .4. enter the IP address of the SAN Volume Controller device with port number 5989. For example. Users can also use fully qualified domain name instead of IP address of the CIM agent.168. Important: 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 • User Name – Enter the user name configured on the CIM agent. Click Add in the Configure Array Manager panel.15. where 5989 is the CIM agent's port number. 192.From the pull down menu. Reinstate the connection information for the array. select the type of array you are using CIM Server Address – Enter the IP address and the port number of the CIM agent. 5. Manager Type . • • • Display Name – Enter the name of your array.2:5989.

When using an embedded CIMOM please use the password configured for the user created on SAN Volume Controller device.• Password . click Connect. Once all the required information is input. the following page is displayed Click OK.Enter the password configured for the user selected above. on the CIM agent. this initiates SRM to discover the SAN Volume Controller device at the specified IP address and if successful. to add the protected site “Array” to SRM. 19 .

20 .

Review the protected and recovery site SAN Volume Controller ID information in the Configure Array Manager window and click Next to add the recovery site “Array” information 21 .

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

Confirm the recovery site “Array ID” and click OK 23 .

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 24 .

R2/R3 Failover Policy The IBM SystemStorage SAN Volume Controller SRA completely automates the TestFailover procedure. extra care needs to be taken while adding replicated VDisks to Consistency 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). The only pre-requisite this procedure needs. 25 . is to have enough free space available in the MDisk group. TestFailover Procedure Depending on the SRA configuration. the SRA creates FlashCopy target volumes in the MDisk Group the user specified in the SRA configuration. from the Storage Replication Adapter’s perspective.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 belong to the same Metro/Global Mirror Consistency Group. So. the user might have to perform additional tasks for the test failover procedure to work. During this procedure. are displayed under a single Datastore Group.

After the recovery (failover) is complete. R2 Failover Policy with Auto. the SRA creates FlashCopy target volumes in the MDisk Group the user specified in the SRA configuration. the user needs to pre-create the R3 set of volumes. and map R3 volumes to the recovery site ESX server(s). be done by the user as long as all the steps and pre-requisites mentioned in this document are carried out properly. the Metro Mirror and/or Global Mirror relationships and/or Consistency Groups are stopped and their status changed to “idling”. and map R3 volumes to the recovery site ESX server(s). be done by the user as long as all the steps and pre-requisites mentioned in this document are carried out properly. the user might have to perform additional tasks for the failover procedure to work. Copy Direction Switch If the “Auto Switch Replication” option is not selected.This procedure doesn’t require anything specific to the Storage Replication Adapter. Copy Direction Switch This procedure doesn’t require anything specific to the Storage Replication Adapter. create the FlashCopy relationships between R2 and R3 volumes. Pre-Configured Environment For this configuration. R2 Failover Policy without Auto. the user needs to pre-create the R3 set of volumes. 26 . from the Storage Replication Adapter’s perspective. R3 Failover Policy The IBM SystemStorage SAN Volume Controller SRA completely automates the failover procedure. The only pre-requisite this procedure needs. Pre-Configured Environment For this configuration. the Metro Mirror and/or Global Mirror copy direction is switched (only if the protected site SAN Volume Controller is online). create the FlashCopy relationships between R2 and R3 volumes. is to have enough free space available in the MDisk group. Failover Procedure Depending on the SRA configuration. During this procedure.

27 . Mask the VDisks on the SAN Volume Controller from the ESX server at Site A. R2 Failover Policy without Auto.e. If Site A still has DR protection configured for the protection groups P1 in recovery plan R1. 2. R2 Failover Policy with Auto. (If Site A does not have SRM installed. Failback Scenario The following failback scenario uses SRM as a failback tool to Site A after executing a recovery plan R1 at Site B in recovery mode for 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.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. If it is not already in place. Copy Direction Switch Start the Metro/Global Mirror relationships and/or Consistency Groups with “-clean” flag with primary volumes now being auxiliary i. delete protection groups P1 at Site A. Establish appropriate array replication from Site B to Site A for the datastores containing recovered virtual machines. Delete recovery plan R1 at Site B. To manually execute a failback scenario 1. install SRM at Site A. use the vSphere Client at Site B to establish Site A as the secondary site for Site B. 3. “-primary aux”. 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 recovery site SAN Volume Controller.) 4. Failback can be managed like any planned server migration.

ibm.com/redbooks/pdfs/sg247521. After the user has determined that the virtual machines have been fully replicated to Site A. 12. At this point. execute recovery plan R2 in recovery mode. Create protection group(s) P3 at Site A to protect recovered virtual machines from Site A to Site B. 11. 28 . 6. If the test is successful. create a recovery plan R2 for the protection group or groups P2.redbooks. ii. Delete recovery plan R2 at Site A.com/redbooks/pdfs/sg247574. Delete protection group(s) P2 at Site B. 5. 13. execute recovery plan R2 at Site A in test mode. 8. 7.pdf) IBM SAN Volume Controller Best Practices and Performance Guidelines (http://www. References 1. Create protection group or groups P2 at Site B to protect recovered virtual machines to Site A. Wait till their states change to “consistent synchronized”.pdf) 2.redbooks. Mask the VDisks on the SAN Volume Controller from the ESX server at Site B.ibm.b) Create new Metro Mirror and/or Global Mirror relationships (and Consistency Groups) from R3 to R1 volumes. Create a recovery plan R3 at Site B for the groups. 9. At Site A. IBM SAN Volume Controller Advanced Copy Services Implementation (http://www. the user may want to re-protect recovered virtual machines to Site B: 10.