Professional Documents
Culture Documents
0001 - Implementing DR Solutions With IBM Storwize V7000 and VMware Site Recovery Manager
0001 - Implementing DR Solutions With IBM Storwize V7000 and VMware Site Recovery Manager
A step-by-step guide
Table of contents
Abstract..................................................................................................................................... 1
Introduction .............................................................................................................................. 1
Intended audience .................................................................................................................... 1
Overview of a disaster recovery solution ............................................................................... 1
Benefits of implementing Site Recovery Manager with IBM Storwize V7000 ....................................... 2
Overview of VMware vCenter Site Recovery Manager with IBM Storwize V7000................. 2
VMware Overview .............................................................................................................................. 2
VMware vSphere 4.1 - ESX Edition .............................................................................. 2
VMware vCenter Server ............................................................................................... 4
VMware vSphere Client ................................................................................................ 4
vCenter Site Recovery Manager ................................................................................... 4
Storage Replication Adapter ......................................................................................... 6
VMware High Availability .............................................................................................. 6
Database ........................................................................................................................................... 7
An overview of IBM Storwize V7000 ................................................................................................... 7
Storwize V7000 software .............................................................................................. 8
Storwize V7000 hardware............................................................................................. 9
Configuring SRA..........................................................................................................27
Configuring SRM...............................................................................................................................30
Creating site pair .........................................................................................................30
Prerequisites .............................................................................................................................30
Procedure .................................................................................................................................31
Configuring array managers ........................................................................................32
Prerequisites .............................................................................................................................33
Procedure .................................................................................................................................33
Configuring inventory mappings...................................................................................37
Procedure .................................................................................................................................39
Creating a protection group .........................................................................................40
Prerequisites .............................................................................................................................40
Procedure .................................................................................................................................40
Creating a recovery plan..............................................................................................42
Procedure .................................................................................................................................42
Best practices......................................................................................................................... 56
Customizing recovery plan ................................................................................................................56
Configuring protection for a virtual machine.......................................................................................57
Conclusion.............................................................................................................................. 57
Resources............................................................................................................................... 58
Glossary of terms................................................................................................................... 59
Trademarks and special notices ........................................................................................... 63
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
Abstract
This paper offers detailed configuration information regarding IBM Storwize V7000 in an ESX
environment with VMware vCenter Site Recovery Manager. The purpose of this paper is to set
appropriate expectations for customers with regard to high availability (HA) options and
automated failover using VMware vCenter Site Recovery Manager.
Introduction
This paper provides a detailed discussion around how to implement VMware vCenter Site Recovery
Manager (SRM) when used with IBM Storwize V7000. After reading this document the reader will be
able to install and configure SRM with VMware high availability (HA) and understand how to run a disaster
recovery (DR) plan and DR test. In addition, the reader will have a conceptual understanding of what is
required in a true DR scenario, which is much broader than just failover of the virtual infrastructure and
storage environment.
Intended audience
This document is intended for anyone who wants to install and use VMware Site Recovery Manager with
IBM Storwize V7000 storage system. This paper assumes that the user has some background in both
Storwize V7000 and VMware products, specifically Storwize V7000 with Metro Mirror and VMware vCenter
Server. In addition, the reader should have knowledge of DR solutions and the work flow required in a DR
scenario.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
Virtualization layer - This layer provides the idealized hardware environment and
virtualization of underlying physical resources to the virtual machines. This layer includes
the virtual machine monitor (VMM), which is responsible for virtualization, and the
VMkernel. The VMkernel manages most of the physical resources on the hardware,
including memory, physical processors, storage, and networking controllers. The
virtualization layer schedules the virtual machine operating systems and, if you are
running an ESX host, the service console. The virtualization layer manages the access
physical resources by operating systems. The VMkernel must have its own drivers to
provide access to the physical devices.
Hardware interface components - The virtual machine communicates with hardware, such
as processors or disk by using hardware interface components. These components
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
include device drivers, which enable hardware-specific service delivery while hiding
hardware differences from other parts of the system.
User interface - Administrators can view and manage ESX hosts and virtual machines in
several ways:
A VMware vSphere Client can connect directly to the ESX host. This setup is
appropriate if your environment has only one host. A vSphere Client can also
connect to vCenter Server and interact with all ESX hosts that vCenter Server
manages.
The vSphere Web Access Client allows you to perform a number of management
tasks by using a browser-based interface.
When you are required to have command-line access, you can use the VMware
vSphere command-line interface (CLI).
shows how the components interact. The ESX host has four virtual machines configured. Each virtual
machine runs its own guest operating system and applications. Administrators monitor the host and
the virtual machines in the following ways:
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
Setting up a default HA cluster is straightforward. The basic process is to connect a vSphere 4 client to
a vCenter Server, create an empty cluster, and add hosts or VMs to the cluster. Each host must be
assigned a host name, and a static IP address must be associated with each virtual network interface
card (NIC).
The default cluster settings work well in most cases, but they can be modified if required. See the
VMware vSphere documentation for more information.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
Database
Both vCenter and SRM require a database for storing information. This can be either Microsoft SQL
2005/2008 or Oracle 9i/10g/11g. For testing, you can use the Microsoft SQL Server 2008 Express, which
is free of charge for testing and development purposes.
VMware vCenter Server requires its own database to store data and at the same time the SRM server
requires its own database to store recovery plans, inventory information, and other associated data.
Before installing the vCenter and SRM server, you must configure and initialize the databases for vCenter
and SRM server.
If you are updating SRM to a new release, you may use the existing database. First, back up the
database, in case you need to revert back to it after the upgrade.
The SRM database at each site holds information about virtual machine configurations, protection groups,
and recovery plans. SRM is unable to share the vCenter database as it uses an alternative database
schema, though you may use the vCenter database server to create and support the SRM database. Each
SRM site requires its own instance of the SRM database. The database must exist before SRM can be
installed. If the SRM database at either site becomes corrupted, the SRM servers at both sites will shut
down.
For testing purposes, the team used SQL Server 2008.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
IBM Easy Tier technology can improve performance up to 200 percent, by moving as
little as 10 percent of data to solid-state storage and requires no administrator intervention
The dynamic migration function helps to speed up time-to-value from weeks or months to
days, eliminating the cost of add-on migration tools
IBM Storwize V7000 includes the following enterprise-class data protection features:
Metro Mirror and Global Mirror create exact copies of the data at remote locations, to help
systems stay up and running in case of an emergency
FlashCopy creates instant copies of data to minimize data loss
IBM Storwize V7000 can make storage infrastructure more efficient, improving businesses' accessibility to
data.
Data migration
Space management:
IBM Easy Tier, to migrate the most frequently used data to better performing
storage
Metering of service quality when combined with IBM Tivoli Storage Productivity
Center
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
Figure 1.Storwize V7000 with internal RAID storage and external virtualized storage systems.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
Automation
Non-disruptive testing
Eliminating complex manual-recovery steps
Centralizing management of recovery plans
With SRM, you can create, update, and document DR plans to meet recovery time objectives, recovery
point objectives, and compliance requirements. SRM enables you to run automated tests of recovery plans
without disrupting the IT environment.
Note: You need to set up FlashCopy on the recovery site and Metro Mirror on IBM Storwize V7000 at both
sites for use with VMware's SRM.
FlashCopy
The FlashCopy function copies the contents of a source volume to a target volume. Any data that
existed on the target volume is lost and is replaced by the copied data. After the copy operation has
been completed, the target volumes contain the contents of the source volumes as they existed at a
single point in time. The FlashCopy function is sometimes described as an instance of a time-zero
copy (T 0) or point-in-time copy technology. Although FlashCopy operation takes some time to
complete, the resulting data on the target volume is presented so that the copy appears to have
occurred immediately.
Metro Mirror
The Metro Mirror Copy Services features enable you to set up a relationship between two volumes, so
that updates made to one volume are mirrored to the other volume. The volumes can be in the same
cluster or on two different clusters.
An application needs to send only writes to a single volume and the system will maintain two copies of
the data. If the copies are separated by a significant distance, the Metro Mirror copies can be used as
a backup for disaster recovery. A prerequisite for Metro Mirror operations between clusters is that the
SAN fabric to which they are attached provides adequate bandwidth between the clusters.
For MetroMirror, one volume is designated as the primary and the other volume is designated as the
secondary. Host applications write data to the primary volume, and updates to the primary volume are
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
1
0
copied to the secondary volume. Ordinarily, host applications do not perform I/O operations to the
secondary volume.
The Metro Mirror feature provides a synchronous-copy process. When a host writes data to the
primary volume, it does not receive confirmation of I/O completion until the write operation has
completed for the write to both the primary volume and the secondary volume. This ensures that the
secondary volume is always up-to-date with the primary volume in the event that a failover has to be
performed. However, the host I/O is subject to the latency and bandwidth limitations of the
communication link to the secondary volume.
Figure 3 illustrates how a write to the master VDisk is mirrored to the cache for the auxiliary VDisk, before
an acknowledgement of the write operation is sent back to the host that issued the write command.
When the application performs a write update operation to a source volume at the production site, the
following actions occur:
1. An application requests a write operation to the source volume. The write operation is written into
cache at the production site.
2. Send the write operation to the target cache and at the recovery site.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
1
1
3. The Storwize V7000 array at the recovery site signals that the write operation has been completed
when the updated data is in its cache.
4. When Storwize V7000 array at the production site receives notification from the target storage at
the recovery site that the write operation has been completed, it returns the I/O complete status to
your application.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
1
2
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
1
3
The following environment is set up to document the process of implementing VMware SRM with Storwize
V7000 storage system:
A protected site and a recovery site, each containing (the same):
A virtual Microsoft Windows 2003 server, running VMware vCenter Server and the SRM
plug-in
Various other virtual machines
Hardware information
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
1
4
Primary site
Server (ESX Hosts):
Storage:
IBM Storwize V7000
Copy Services features enabled:
FlashCopy
MetroMirror
Secondary site
Server (ESX Hosts):
2 * IBM System x3650
Storage:
IBM Storwize V7000
Copy Services features enabled:
FlashCopy
MetroMirror
Software information
VMware:
VMware vSphere 4.1:
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
1
5
SRA:
Version: v1.20.10713
Database:
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
1
6
1. ESX Server is installed on the internal hard drives of each site's IBM x3650 host. Refer to ESX
and vCenter Server Installation Guide for more information.
2. Install a Microsoft Windows 2003 VM running on the ESX Server at both sites - This is for VMware
vCenter Server and SRM. Refer to Guest Operating System Installation Guide for more
information
3. Configure VMware HA for VMware ESX Server at both sites. Refer to vSphere Availability Guide.
4. Install Microsoft SQL Server 2008 on the VM at both sites. Refer to the Microsoft SQL Server
Installation Guide.
5. Configure Database for vCenter Server and SRM. Refer to Site Recovery Manager Administration
Guide and ESX and vCenter Server Installation Guide.
6. Install vCenter Server at both sites. Refer to ESX and vCenter Server Installation Guide.
7. Install SRM on both sites. Refer to Site Recovery Manager Administration Guide.
8. Install and enable SRM Plug-ins on both sites. Refer to Site Recovery Manager Administration
Guide.
9. Install and configuring SRA on both sites. Refer to Storage Replication Adapter for VMware SRM
Installation and Users Guide (which should be included with SRA installation package).
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
1
7
Protected site
Two hosts configured on protected site storage:
------------------------------------------------------------------------------------------------------------------------------------------StorwizeV7000_P:admin>svcinfo lshost vmware_WDFHV
id 24
name vmware_WDFHV
port_count 2
type generic
mask 1111
iogrp_count 4
WWPN 10000000C9935544
node_logged_in_count 2
state active
WWPN 10000000C9935545
node_logged_in_count 2
state active
StorwizeV7000_P:admin>svcinfo lshost vmware_WDFHT
id 25
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
1
8
name vmware_WDFHT
port_count 2
type generic
mask 1111
iogrp_count 4
WWPN 2101001B32BB8B3D
node_logged_in_count 2
state active
WWPN 2100001B329B8B3D
node_logged_in_count 2
state active
------------------------------------------------------------------------------------------------------------------------------------------Mapping volumes on protected site:
------------------------------------------------------------------------------------------------------------------------------------------StorwizeV7000_P:admin>svcinfo lshostvdiskmap vmware_WDFHT
id name
SCSI_id vdisk_id vdisk_name vdisk_UID
25 vmware_WDFHT 0
125
vmware_vol_1 600507680191814CA8000000000005DC
25 vmware_WDFHT 1
126
vmware_vol_2 600507680191814CA8000000000005DD
25 vmware_WDFHT 2
127
vmware_vol_3 600507680191814CA8000000000005DE
------------------------------------------------------------------------------------------------------------------------------------------vmware_vol_2 and vmware_vol_3 are used for virtual machine datastore and configured for Metro Mirror.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
1
9
Recovery site
Two hosts configured on recovery site storage:
------------------------------------------------------------------------------------------------------------------------------------------StorwizeV7000_S:admin>svcinfo lshost vmware_GNXT5
id 21
name vmware_GNXT5
port_count 2
type generic
mask 1111
iogrp_count 4
WWPN 10000000C9732DBB
node_logged_in_count 2
state active
WWPN 10000000C9732DBA
node_logged_in_count 2
state active
StorwizeV7000_S:admin>svcinfo lshost vmware_CHMAK
id 22
name vmware_CHMAK
port_count 2
type generic
mask 1111
iogrp_count 4
WWPN 2101001B32BB1C3F
node_logged_in_count 2
state active
WWPN 2100001B329B1C3F
node_logged_in_count 2
state active
-------------------------------------------------------------------------------------------------------------------------------------------
2
0
2
1
Configure VMware HA
Install the SRM plug-in
Install SRA
Configure the SRM plug-in
Configuring VMware HA
This section explains the prerequisites and the procedure for configuring VMware HA.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
2
2
Prerequisites
The prerequisites for configuring VMware HA are:
All virtual machines and their configuration files must reside on shared storage.
To allow the powering up of virtual machines across different hosts in the cluster, the
hosts must be configured to access the shared storage.
Each host in a VMware HA cluster must have a host name assigned and a static IP
address associated with each of the virtual NICs.
Hosts must be configured to have access to the virtual machine network.
VMware recommends redundant network connections for VMware HA. For ESX, you need to set up
redundant service console networking.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
2
3
Procedure
To connect vSphere Client to vCenter Server using an account with cluster administrator permissions:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12. Click OK to close the cluster's Settings dialog box. A configured VMware HA cluster, populated
with hosts, is created.
For more information about creating VMware HA, refer to vSphere Availability Guide.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
2
4
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
2
5
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
2
6
Installing an SRA
To install SRA:
Download SRA from the URL: http://www.vmware.com/download/srm/.
2. Install SRM, and then SRA.
3. Accept the default destination location for installation.
C:\Program Files\VMware\VMware Site Recovery Manager\scripts\SAN\IBMSVC
1.
This is the default SRA directory path based on SRM directory path. And SRM uses it to scan for scripts. If
you wish to install SRM in an alternative location, change the SRA directory path accordingly.
The default installation of IBM SAN Volume Controller SRA creates a shortcut named
IBMSVCSRAUtil.exe on the desktop.
Configuring SRA
Perform the following steps to configure SRA:
1. The configuration utility must be run at the recovery site vCenter Server to configure the recovery
site SRA only. You need to creating the target volumes and Metro Mirror relationships. The
number of target VDisks for MetroMirror on the recovery site must be equal to the number of
source VDisks at the protected site
2. Create Metro Mirror relationships between the source and target VDisks, and add them to
consistency groups, appropriately. For more information on Metro Mirror Copy Services refer to
IBM Storwize V7000 Advanced Copy Services Implementation.
3. Before using the Storage Replication Adapter, ensure that the Metro Mirror relationships and
consistency groups are in consistent synchronized state
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
2
7
Double-clicking the SRA shortcut at the recovery site should bring up the window, as shown in .
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
2
8
Pre-Configured Env - Where the user has already created the required volumes and their
mappings to the recovery site ESX servers, a user with the CopyOperator privileges will
be sufficient.
Failover Policy R2 - Where the SRA creates the snapshot volumes and mappings of these
volumes to the ESX servers at the recovery site, during test failover operations, a user
with the superuser privileges will be required. If, the replicated targets are premapped to
the recovery site ESX servers, then a user with the CopyOperator privileges will suffice
for failover operations.
Failover Policy R3 - Where the SRA creates the snapshot volumes and mappings of these
volumes to the ESX servers at the recovery site, during failover and failback operations, a
user with the superuser privileges will be required.
Auto.Switch Replication - The configuration utility allows the user to instruct SRA to
perform an automatic switch of copy direction during failover operations. For pre-created
and R3 recovery configurations, automatic switching of remote copy relationships' or
consistency groups' copy direction is not possible
Depending on the configuration of SRA, the user might need to perform additional tasks to complete the
failover procedure. Several failover procedures are available
R3 Failover Policy
Storwize V7000 SRA completely automates the failover procedure. During this procedure,
the SRA creates FlashCopy target volumes in the MDisk group that the user specified in
the SRA configuration. The only prerequisite for this procedure is from the Storage
Replication Adapter: There must be sufficient free space available in the MDisk group.
Pre-Configured Environment
For this configuration, the user should have created the R3 set of volumes, the FlashCopy
relationships between R2 and R3 volumes, and map R3 volumes to the recovery site ESX
servers.
Here the team configured R2 Failover Policy with Auto Switch Replication with Test
MDisk Group ID 4 and Space Efficient Mode set to ". This results in SRA creating the
snapshot volumes and mappings to the volumes to the ESX servers at the recovery site.
Note: VDisk mappings are not required on the recovery site.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
2
9
Configuring SRM
After SRM has been installed at the protected and recovery sites, you need to connect the two sites in
order to create a site pair, and configure the array managers and SRM at each site. The SRM client plugin is used to administer SRM. Site pairing requires vSphere administrative privileges at both sites.
Prerequisites
The following steps must be followed before connecting the protected and recovery sites:
Install the appropriate storage replication adapters on the SRM server hosts at each site.
The recovery site must be the replication target of arrays managed by the SRA at the
protected site.
Download the SRM plug-in from an SRM server on to the vSphere client to be used to
administer SRM.
1 In the vSphere client, click the Site Recovery icon to start the Site Recovery application.
2 To start the setup wizards, click "Configure", next to the required configuration option.
Connection
Array Managers
Inventory Mappings
Protection Groups
Recovery Plans
Prerequisites
Before you can connect the protected and recovery sites, you must install an SRM server at each
site. Then, install and enable the SRM plug-in on the vSphere Client from which SRM will be
administered.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
3
0
Procedure
1. In the Protection Setup area of the Summary window, navigate to the Connection line and click
Configure.
2. The Connect to Remote Site page appears.
3. On the Remote Site Information page, type the IP address or host name of the vCenter server at
the recovery site, and click Next.
4. If the certificate error screen appears, either click OK or fix the certification problem.
Note: Certificate configuration is beyond the scope of this paper.
5. On the vCenter Server Authentication page, provide the vCenter administrators user name and
password for the recovery site and click Next.
6. After completing all site pairing steps successfully, click Finish on the Complete Connections
page.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
3
1
8. After the site pairing is complete, the primary site vCenter server will display the paired site
addresses and the Connection as Connected in the Protection Setup section. Note that the SRM
plug-in at the DR site will also display the sites paired in the opposite direction.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
3
2
Prerequisites
Before configuring the array managers at the protected and recovery sites, be sure that at least one
virtual machine at the protected site is stored on a replicated device supported by an array for which
you have installed an SRA. The array manager configuration wizard does not detect replicated
devices, unless they are part of a datastore that is home to at least one virtual machine.
Procedure
1. In the Protection Setup area of the Summary window, navigate to the Array Managers line and
click Configure. The Configure Array Managers page appears.
2. Click Add to configure the new array manager.
3. On the Add Array Manager page, enter array manager information to instate the connection
information for the array. Then, click Connect to validate the information supplied and return the
list of arrays discovered by the selected array manager.
Manager Type - From the drop-down list, 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 the
fully qualified domain name instead of the IP address of the CIM agent. When using an embedded
CIMOM, enter the IP address of Storwize V7000 device with port number 5989.
Password - Enter the password configured for the CIM agent user selected earlier. When
using an embedded CIMOM, use the password configured for the user created on
Storwize V7000.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
3
3
4. Click OK to query the selected arrays and discover which of their devices are replicated.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
3
4
5. Repeat step 1 through step 4, to add the array manager for the secondary site by specifying the
storage IP addresses.
SRM ensures that the two storage subsystems are mirrored and shows the resulting LUN count in
green, with a check mark
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
3
5
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
3
6
6. On the Review Replicated Datastores page, you can expand each datastore group to see the
datastores contained within, and the devices that they use. If the list of datastore groups is
unexpected, correct it before continuing. Click Finish to complete the configuration of the array
managers.
Array managers have to be successfully created before protection groups can be configured.
Sometimes, existing array managers do not refresh correctly. If this problem occurs, click Rescan
Arrays on the final page to refresh the array managers.
When viewing the Site Recovery window for the secondary site, the array managers might be shown
as not configured. Only the primary site shows the datastores on that site. The recovery site has
read-only access to the mirrored logical drives.
3
7
reapplied as needed (for example, when new members are added). If mappings are not created, the
VDisks must be specified individually for each virtual machine that is added to a protection group. A
virtual machine cannot be protected unless it has valid inventory mappings for networks, folders, and
computer resources. Inventory mappings are not required for resources that will not be used by
protected virtual machines.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
3
8
Procedure
1. In the Protection Setup area of the Summary window, navigate to the Inventory Mappings line
and click Configure.
2. The Inventory Mappings page displays a tree of resources at the protected site and a
corresponding tree of resources at the recovery site. For any protected site resource that does not
have an inventory mapping, the corresponding item in the recovery site tree is listed as None
Selected.
3. To configure mapping for a resource, right-click the resource in the Protected Site Resources
column, and click Configure to navigate to the recovery site resource to which the protected site
resource should be mapped.
shows the resources that are in use on the primary site map, compared to the resources of the
recovery site.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
3
9
Prerequisites
Before creating a protection group, the protected site should be connected to the recovery site,
and the array managers must be configured. To be protected, a virtual machine must have folder,
network connection, and resource pool assignments that are also valid at the recovery site.
Configure inventory mappings before creating protection groups, unless intending to configure
these mappings individually for each member of the group.
Procedure
1. In the Protection Setup area of the Summary window, navigate to the Protection Groups line
and click Create.
2. The Create Protection Group page appears.
3. On the Name and Description page of the Create Protection Group window, type a name and
optional description for the protection group, and click Next.
4. On the Select a Datastore Group page, select the datastore group from the list, and click Next.
4
0
The datastores listed were discovered when you configured the array managers. Each datastore
in the list is replicated to the recovery site, and supports at least one virtual machine at the
protected site. When you select a datastore, the virtual machines that it supports are listed in the
VMs on the selected datastore group field, and are automatically included in the protection group.
5. Enter a location to hold the temporary inventory files on a local datastore that is not replicated at
the recovery site.
6. Click Finish to close the dialog, and then review the Protection Group 1 Summary tab. The Status
indicates that the Protection Group is OK.
7. At the secondary site, a placeholder virtual machine has been created for each virtual machine
that was in the Protection Group. These virtual machines have .vmx configuration files stored in
the datastore selected in Step 4, but they have no virtual disks attached.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
4
1
Procedure
1. Open a vSphere Client and connect to the vCenter server at the recovery site. Log in as a
vSphere administrator.
2. In the Recovery Setup area of the Summary window, navigate to the Recovery Plans line and
click Create.
3. The Create Recovery Plan page appears.
4. On the Recovery Plan Information page of the Create Recovery Plan wizard, type a name for
the plan and add a description (optional), and click Next.
5. On the Protection Groups page, select the protection groups for the plan to recover, and click
Next.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
4
2
6. On the Response Times page, specify how long you want the recovery plan to wait for a response
from a virtual machine after various recovery plan events, and then click Next.
Change Network Settings - If the virtual machine does not acquire the expected IP
address within the specified interval after a recovery step that changes network settings,
an error is reported and the recovery plan proceeds to the next virtual machine.
Wait for OS Heartbeat - If the virtual machine does not report an OS heartbeat within the
specified interval, after being powered on, an error is reported and the recovery plan
proceeds to the next virtual machine.
Note: Responses cannot be detected on virtual machines that do not have VMware tools installed.
7. On the Configure Test Networks page, select a recovery site network to which recovered virtual
machines connect during recovery plan tests, and click Next.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
4
3
8. On the Suspend Local Virtual Machines page, select the virtual machines at the recovery site
that the recovery plan should suspend.
Note: Suspending local virtual machines releases resources for use by the recovered virtual
machines. The virtual machines are suspended during a test recovery as well as during an actual
recovery. After a test recovery, they will be powered on, again.
9. Click Finish to close the dialog, and then review the Recovery Plan Summary tab. The Status
indicates that the Recovery Plan is OK.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
4
4
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
4
5
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
4
6
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
4
7
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
4
8
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
4
9
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
5
0
The protected virtual machines should now have been powered on at the recovery site. You can view their
state from the Virtual Machines tab.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
5
1
Note: You must place protection groups and the recovery plans that operate them on separate sites.
After you instigate a failover, the failover process is irreversible, except by following the steps outlined in
the Performing failback section.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
5
2
Performing failback
Failback refers to restoring applications and services back to the primary site, after the site has been
recovered. Currently, failback is not an automated process.
Procedures
5
3
0000020060215AFC StorwizeV7000_S
598
vmware_vol_2A aux 0
consistent_synchronized 50
metro
127 MMRel2 000002006460532A StorwizeV7000_P
127
vmware_vol_3
0000020060215AFC StorwizeV7000_S
599
vmware_vol_3A aux 0
consistent_synchronized 50
metro
MMCG1
MMCG1
---------------------------------------------------------------------------------------------------------------------------------6. Configure the original secondary site as the primary site, for example, configure the connection,
array managers, inventory mappings, and protection groups
7. On the original primary site, create the recovery plan.
8. On the original primary site, run the recovery plan.
Troubleshooting SRM
Modification of the PATH environment variable for the VMware SRM user on the
SRM server
IBM Storage Replication Adapter for Storwize V7000 does not include the path to the Perl binary. The
PATH environment variable needs to be modified for the VMware SRM user on the SRM server, and
include the path to the Perl binary on the VMware SRM server.
Follow the steps to set the path environment variable if the VMware SRM server is running on Windows
2003:
1.
1.
2.
3.
4.
5.
Right-click My Computer,
Click Properties, and select the Advanced tab.
Click Environment Variables.
In the System Variables window, scroll down and select PATH.
Click Edit.
In the variable value, append the string, C:\Program Files\VMware\VMware vCenter Site
Recovery Manager\external\perl-5.8.8\bin.
Modification timeout for executing a single command using array vendor adapter
When testing a recovery plan, the following error may occur when preparing storage:
Command testFailover execution timed out: 300 seconds.
This requires a change to the settings, which can be achieved through Advanced Settings for SRM
service.
5
4
1. Right-click Site Recovery on the recovery site. The Advanced Settings window appears.
2. Select SanProvider in the left panel.
3. Change the SanProvider.CommandTimeout value from the default 300 seconds to a more suitable
value.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
5
5
Procedure
To initiate the collection of SRM server log files from the Start menu:
1. Log in to the SRM server host.
2. Select Start > Programs > VMware > VMware vCenter Site Recovery Manager > Generate
vCenter Site Recovery Manager log bundle.
To initiate the collection of SRM server log files from the Windows command line:
1. Start a Windows command shell on the SRM server host.
2. Change directory to C:\Program Files (X86)\VMware\VMware vCenter Site Recovery
Manager\bin.
3. Run the following command:
cscript srm-support.wsf
The individual log files are collected in a file named srm-support-Administrator-MM-DD-YYYY-HHMM.zip, where MM-DD-YYYY-HH-MM indicates the month, day, year, hour, and minute when the log
files were created.
Best practices
Customizing recovery plan
Most recovery plans intended for production use must be customized to suit specific needs. For example,
a recovery plan for an emergency at the protected site is likely to be different from a planned migration of
services from one site to another.
A recovery plan can be customized to run commands, display messages that require a response, and
change the recovery priority of protected virtual machines. In the protection group, it is important to set
infrastructure servers at high priority and make sure they are recovered first. Also consider inserting a
message step into the recovery plan, after the step that recovers the high-priority virtual machines. This
will cause the execution of the recovery plan to be paused at this point. During a DR test or true DR
scenario, verify that the infrastructure services are available before the other servers with dependencies
are recovered.
Always perform a realistic test. Do not depend on any infrastructure or services that will not be available
during a real DR scenario.
Some recovery plan steps are executed during all recoveries, some are executed only during test
recoveries, and some are always skipped during test recoveries. Understanding these steps, their order,
and the context in which they run is important when customizing a recovery plan.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
5
6
Conclusion
This paper describes all the steps required to implement a disaster recovery configuration with IBM
Storwize V7000 and VMware SRM, and demonstrates that SRM helps to easily manage complex VMware
environments. It also describes how to configure Storwize V7000 with Copy Services features, and how
the SRA work together with SRM to implement disaster recovery.
VMware vCenter Site Recovery Manager, working in concert with IBM Storwize V7000 Copy Services
features, FlashCopy and Metro Mirror, provides a simplified disaster recovery solution. An easy-to-use
graphical user interface is all that is required to manage the task of defining, testing, and executing a
disaster recovery plan. This contrasts well with the manual scripting and complexity of more traditional
disaster recovery solutions.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
5
7
Resources
These websites provide useful references to supplement the information contained in this paper:
Site Recovery Manager Administration Guide for vCenter Site Recovery Manager 4.1
http://www.vmware.com/pdf/srm_admin_4_1.pdf
IBM Redbooks
ibm.com/redbooks
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
5
8
Glossary of terms
C
Command-line interface (CLI) - a mechanism for interacting with a computer operating system or software
by typing commands to perform specific tasks.
Consistent synchronized - A Metro Mirror state which can apply to relationships and consistency groups.
When Metro Mirror relationship is in the consistent synchronized state, it indicates that the volumes are
identical and in-step with one another. While the primary volume is accessible for read and write
operations, the secondary volume is accessible for read-only I/O operations.
D
Datastore - Virtual representation of combinations of underlying physical storage resources in the
datacenter. A datastore is the storage location (for example, a physical disk, a RAID, or a SAN) for virtual
machine files.
Disaster recovery (DR) - The process, policies, and procedures related to preparing for recovery or
continuation of technology infrastructure critical to an organization after a natural- or human-induced
disaster. Disaster recovery is a subset of business continuity. While business continuity involves planning
for keeping all aspects of a business functioning in the midst of disruptive events, disaster recovery
focuses on the IT or technology systems that support business functions.
Domain Name Server (DNS) - A distributed hierarchical naming system for computers, services, or any
resource connected to a private network or the Internet. It associates identification information with domain
names assigned to each of the participants.
G
Global Mirror (GM) - It provides an asynchronous-copy process. When a host writes data to the primary
volume, confirmation of I/O completion is received before the write operation has been completed for the
copy on the secondary volume. If a failover operation is performed, the application must recover and apply
any updates that were not committed to the secondary volume. If I/O operations on the primary volume are
paused for a small length of time, the secondary volume can become an exact match of the primary
volume.
H
High availability (HA) - A system design approach and associated service implementation that ensures a
prearranged level of operational performance will be met during a contractual measurement period.
M
Metro Mirror - A Copy Services feature of IBM Storwize V7000; it provides a synchronous-copy process.
When a host writes to the primary volume, it does not receive confirmation of I/O completion until the write
operation has been completed for the copy on both the primary and the secondary volumes. This ensures
that the secondary volume is always up-to-date with the primary volume in the event that a failover
operation must be performed. However, the host is limited to the latency and bandwidth limitations of the
communication link to the secondary volume.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
5
9
N
Network interface card (NIC)- Taken to identify the socket and associated hardware allowing access to
Ethernet local area network (LAN), and so on.
NIC teaming - NIC teaming is the grouping of two or more physical NICs into a single logical NIC, used for
network fault tolerance.
P
Primary or protected site - Is a mirror relationship that accepts host read/write I/O and stores application
data. When the mirror relationship is first created, data from the primary site is copied in its entirety to the
associated secondary site. The primary site contains the original user data in a mirroring relationship.
R
Recovery point objective (RPO) - The point in time to which you must recover data as defined by your
organization. This is generally a definition of what an organization determines as an acceptable loss in a
disaster situation. If the RPO of a company is 2 hours and the time it takes to get the data back into
production is 5 hours, the RPO is still 2 hours. Based on this RPO, the data must be restored within 2
hours of the disaster.
Recovery time objective (RTO) - The duration of time and a service level within which a business process
must be restored after a disaster in order to avoid unacceptable consequences associated with a break in
business continuity.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
6
0
S
Storage area network (SAN) - An architecture allowing remote data storage devices to be connected to
servers in such a way that the devices appear to be locally attached to the system. A SAN typically has its
own network of storage devices that are generally not accessible through the regular network by regular
devices. The cost and complexity of SANs dropped in the late 2000s, allowing wider adoption across both
enterprise and small- to medium-sized business environments.
Serial-attached SCSI (SAS) - A computer bus used to move data to and from computer storage devices,
such as hard drives and tape drives.
Secondary or recovery site - In a mirror relationship that maintains a mirror (or copy) of the data from its
associated primary site. The secondary site is available for host read requests only. Write requests to the
secondary site are not permitted. In the event of a disaster failure of the primary site, the secondary site
can be promoted to the primary role. The secondary site is also referred to as the disaster recovery (DR)
site.
Storage Replication Adapter (SRA) - The XML / Perl interface that acts as a communication medium
between SRM and the storage subsystem.
VMware vCenter Site Recovery Manager (SRM) - A business continuity and disaster recovery solution that
helps plan, test, and execute a scheduled migration or emergency failover of datacenter services from one
site to another.
Solid-state drives (SSD) - A data storage device that uses solid-state memory to store persistent data.
SSDs are distinguished from traditional hard disk drives (HDDs), which are electromechanical devices
containing spinning disks and movable read/write heads.
T
IBM Tivoli Storage Productivity Center (TPC) - A Storage Resource Management software offering that
provides a centralized point of control for managing large scale, complex, heterogeneous storage
environments. It provides the foundation for storage service-level management by offering storage system
and SAN performance and availability management. This includes connectivity reporting between file
systems and physical disk as well as SAN and disk subsystem failure and audit logging.
TPC/R TPC for replication - Designed to control and monitor copy services operations in storage
environments. It also provides advanced Copy Services functions for supported storage subsystems on
the SAN.
V
Virtual Machine (VM) - A virtual machine is a software computer that is similar to a physical computer, runs
an operating system and applications. Multiple virtual machines can operate on the same host system
concurrently.
Virtual machine file systems (VMFS) - A file system that is optimized for storing virtual machines. One
VMFS partition is supported for each SCSI storage device or LUN.
VMkernel - In ESX, a high-performance operating system that occupies the virtualization layer and
manages most of the physical resources on the hardware including memory, physical processors, storage,
and networking controllers.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
6
1
Virtual machine monitor (VMM) - Software that is responsible for virtualizing the processors. One VMM
runs in kernel space for each running virtual machine.
Volume - Is a logical disk that is presented by the clusters. Each volume is associated with a particular I/O
group.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
6
2
6
3
presented here to communicate IBM's current investment and development activities as a good faith effort
to help with our customers' future planning.
Performance is based on measurements and projections using standard IBM benchmarks in a controlled
environment. The actual throughput or performance that any user will experience will vary depending upon
considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the
storage configuration, and the workload processed. Therefore, no assurance can be given that an
individual user will achieve throughput or performance improvements equivalent to the ratios stated here.
Photographs shown are of engineering prototypes. Changes may be incorporated in production models.
Any references in this information to non-IBM websites are provided for convenience only and do not in
any manner serve as an endorsement of those websites. The materials at those websites are not part of
the materials for this IBM product and use of those websites is at your own risk.
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager
Copyright IBM Corporation, 2010
6
4