Вы находитесь на странице: 1из 67

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager

A step-by-step guide

IBM Systems and Technology Group ISV Enablement October 2010

Copyright IBM Corporation, 2010

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

Using Storwize V7000 and SRM for disaster recovery......................................................... 10


Storwize V7000 Copy Services features............................................................................................10 FlashCopy ...................................................................................................................10 Metro Mirror.................................................................................................................10 Prerequisites of Using SRM and IBM Storwize V7000 .......................................................................13

Configurations for disaster recovery .................................................................................... 14


Test configuration .............................................................................................................................14 Hardware information ..................................................................................................14 Primary site ...............................................................................................................................15 Secondary site...........................................................................................................................15 Software information....................................................................................................15 Configuring the site ...........................................................................................................................17 Configuring Storwize V7000 ..............................................................................................................17 Host and volume configuration.....................................................................................18 Metro Mirror configuration............................................................................................20

Installing and configuring components for disaster recovery ............................................ 22


Configuring VMware HA....................................................................................................................22 Prerequisites ...............................................................................................................23 Network Path Redundancy ..........................................................................................23 Procedure ...................................................................................................................24 Installing SRM plug-in .......................................................................................................................25 Installing and configuring SRA for IBM Storwize V7000 .....................................................................27 Installing an SRA .........................................................................................................27
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

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

Implementing a disaster recovery plan................................................................................. 46


Testing the disaster recovery plan .....................................................................................................46 Network isolation when testing the Disaster Recovery Plan..........................................48 Running the disaster recovery plan ...................................................................................................49 Performing failback ...........................................................................................................................53 Procedures..................................................................................................................53

Troubleshooting SRM ............................................................................................................ 54


Modification of the PATH environment variable for the VMware SRM user on the SRM server...........54 Modification timeout for executing a single command using array vendor adapter..............................54 Collect SRM server log files ..............................................................................................................56 Procedure ...................................................................................................................56

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.

Overview of a disaster recovery solution


As IT systems have become increasingly critical to the smooth operation of companies, the importance of ensuring their continued operation, including rapid recovery when subsystems fail, has increased. Prior to selecting a disaster recovery strategy, a disaster recovery planner should refer to their organization's business continuity plan, which should indicate the key metrics of recovery point objective (RPO) and recovery time objective (RTO) for various business processes. The metrics specified for the business processes must then be mapped to the underlying IT systems and infrastructure that support those processes. After mapping the RTO and RPO metrics to IT infrastructure, the DR planner can determine the most suitable recovery strategy for each system. RPO This refers to the point in time to which data must be recovered as defined by the organization. This is generally a definition of what an organization determines as an acceptable loss in a disaster situation. RTO This refers to the duration of time and a service level within which a business process must be restored, following a disaster or disruption, in order to avoid unacceptable consequences associated with a break in business continuity. The ideal solution will have both: a low RPO (in minutes) and RTO (ranges from minutes to hours). It is important to test a DR solution to find whether it is suitable and efficient for business continuity.

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

Benefits of implementing Site Recovery Manager with IBM Storwize V7000


Implementing a virtualized environment using VMware technology and VMware vCenter Site Recovery Manager on Storwize V7000 storage systems provides the infrastructure for unique opportunities to implement real working DR processes that are quick and easy to test, consume less additional storage, and significantly reduce RTO and RPO duration. Site Recovery Manager helps accelerate recovery by automating the recovery process and simplifies management of disaster recovery plans through automated integration. The solution provides reliable recovery by eliminating complex manual recovery steps and helping eliminate disruptive testing of recovery plans. Site Recovery Manager integrates tightly with VMware vSphere, VMware vCenter Server, and storage replication software from IBM to process site failover to recover rapidly, reliably, and affordably. It eases disaster recovery risk, as well as protects all business critical systems and applications.

Overview of VMware vCenter Site Recovery Manager with IBM Storwize V7000
VMware Overview
VMware vSphere 4.1 - ESX Edition
VMware ESX is installed directly on the hardware and does not require any operating system. It is a virtualization platform used to create the virtual machines (VMs) as a set of configuration and disk files that together perform all the functions of a physical machine. Through ESX, you can run the virtual machines, install operating systems, run applications, and configure the virtual machines. Configuration includes identifying the virtual machine's resources, such as storage devices. Each ESX host has a vSphere Client available for management use. If the ESX host is registered with the vCenter Server, a vSphere Client that accommodates the vCenter Server features is available. An ESX system has the following key components: 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: Using a vSphere Client to connect to an ESX host directly. Using a vSphere Client to connect to a vCenter Server. The vCenter Server can manage a number of ESX hosts.

Figure 1: VMware components interacting

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

VMware vCenter Server


VMware vCenter Server is a service that acts as a central administration point for ESX hosts connected to a network. This service directs actions on the virtual machines and the hosts. The vCenter Server is the working core of vCenter. You can have multiple vCenter Server systems joined to a Linked Mode group. This allows you to log in to any single instance of vCenter Server to view and manage the inventories of all the vCenter Server systems in the group. With vCenter, an administrator can manage every component of a virtual environment: ESX servers, VMs and extended functions such Distributed Resource Scheduler (DRS), vMotion, and so on. vCenter requires a database to store its information. A list of supported databases can be found in the database section. To connect to the vCenter service, the VMware vSphere Client is used.

VMware vSphere Client


vSphere Client software can be installed on a Microsoft Windows host and is the primary method of interacting with VMware vSphere. The vSphere Client acts as a console to operate virtual machines and as an administration interface to the vCenter Server systems and ESX hosts. You can download the vSphere Client from the vCenter Server system and ESX hosts. When using SRM, a SRM plug-in for the vSphere Client is required. It can be installed with the SRM service itself.

vCenter Site Recovery Manager


VMware vCenter Site Recovery Manager is business continuity and disaster recovery solution that helps you plan, test, and execute a scheduled migration or emergency failover of data center services from one site to another. SRM is an extension to VMware vCenter that enables integration with array-based replication, discovery, and management of replicated data stores, and automated migration of inventory from one vCenter to another. SRM servers coordinate the operations of the replicated storage arrays and vCenter servers at two sites so that when virtual machines at the protected site are shut down, virtual machines at the recovery site are started up and use the data replicated from the protected site to assume responsibility for providing the same services. Transfer of services from one site to the other is controlled by a recovery plan that specifies the order in which virtual machines are shut down and started up and the allocation of computer resources and the networks that might be accessed. SRM allows you test a recovery plan, using a temporary copy of the replicated data, in a manner that does not disrupt the ongoing operations at either site. shows the Site Recovery Manager architecture.

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

Figure 2: Site Recovery Manager architecture

Protected and recovery sites In a typical SRM installation, the protected site provides business-critical data center services, and the recovery site provides an alternative facility to which these services can be migrated. The protected site can be any site where virtual infrastructure supports a critical business need. The recovery site can be located thousands of miles away, or in the same site. In the typical case, the recovery site is located in a facility that is unlikely to be affected by any environmental, infrastructure, or other disturbances that affect the protected site. SRM has several requirements for the vSphere configurations at each site: Each site must include at least one vSphere data center. The recovery site must support array-based replication with the protected site, and must have hardware and network resources that can support the same virtual machines and workloads as the protected site. One virtual machine must be located on a replicated data store at the protected site. This datastore must be supported by a storage array that is compatible with SRM. The protected and recovery sites should be connected by a reliable IP network. Storage arrays might have additional network requirements. The recovery site should have access to the same public and private networks as the protected site, though not necessarily the same range of network addresses.

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

Storage Replication Adapter


Storage Replication Adapter (SRA) is an interface between the storage subsystem and SRM. IBM Storwize V7000 SRA provides a means for VMware SRM to control IBM Storwize V7000 features, like replication and FlashCopy without VMware SRM requiring any awareness of the storage system. The Storwize V7000 SRA should be downloaded from the VMware website and installed on the server running SRM.

VMware High Availability


VMware High Availability uses a pool of server resources to provide failover for VMs. An agent runs on each server and maintains a heartbeat with other servers in the pool. If a physical server fails or loses network connectivity for an extended period of time, the heartbeat will time-out, and the VMs will be restarted automatically on other servers in the pool. The pool of resources can include both physical servers and VMs. If there is an operating system failure for a particular VM, whilst the physical server remains operational, the VM will be restarted on the same physical server. The following requirements must be met to use VMware HA with vSphere 4: Licensing and installation of VMware vSphere Standard, of VMware vSphere Advanced or of VMware vSphere Enterprise software Note: VMware HA is not included with entry-level VMware Essentials. A minimum of two ESX 4.0 host servers. The first five hosts are added to the cluster as primary hosts, and additional hosts are added as secondary hosts. The primary hosts maintain and replicate all cluster-state information and initiate failover. If a primary host is removed from the cluster, a secondary host is automatically promoted to a primary host. Compatible processors. It is highly recommended that all hosts meet processor compatibility requirements. If necessary, processor masking can be modified to support non-compatible hosts. Shared storage for all servers in the HA pool. This is essential, as virtual disks associated with VMs act as static pivot points when VMs are transferred from a failed host to a new host. As a result, virtual files must be available to all hosts in the pool. All the adapters in the pool should be in the same zone for Fibre Channel SANs. Adapters on servers outside the pool should be in a different zone.

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.

An overview of IBM Storwize V7000


IBM Storwize V7000 is a powerful storage system that combines hardware and software components to provide a single point of control to help support improved storage efficiency. By enabling virtualization, consolidation, and tiering in mid-size organizations, it is designed to improve application availability and resource utilization. The system offers easy-to-use, efficient, and cost-effective management capabilities for both new and existing storage resources in IT infrastructure. IBM Storwize V7000 helps to reduce the growth of storage costs, increase storage administrator productivity, improve service levels, and reduce the risk of losing data. IBM Storwize V7000 helps reduce the growth in storage costs in several ways: Built-in storage virtualization can increase disk utilization by 30 percent Thin Provisioning is designed to reduce disk storage requirements Space-efficient IBM FlashCopy function can help in reducing disk storage needed for point-in-time copies by 75 percent

IBM Storwize V7000 helps storage administrators to work more efficiently: Storage virtualization can double the productivity of storage administrators Easy-to-use graphical user interface simplifies management tasks

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

IBM Storwize V7000 helps improve service levels: 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.

Storwize V7000 software


Storwize V7000 provides the following features to the attached host systems: A single pool of storage Logical unit virtualization Logical volumes management Logical volumes mirroring

IBM Storwize V7000 also provides the following functions: Large scalable cache Copy services: IBM FlashCopy (point-in-time copy), including thin-provisioned FlashCopy to make multiple targets more affordable Metro Mirror (synchronous copy) Global Mirror (asynchronous copy) 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 Thin-provisioned logical volumes

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

Storwize V7000 hardware


Storwize V7000 storage systems consist of a set of drive enclosures. Control enclosures contain disk drives and two node canisters. The two nodes make an I/O group that is attached to the storage area network (SAN) fabric. A single pair of nodes is responsible for serving the I/O on a given virtualized volume. Because a volume is served by two nodes, there is no loss of availability when a node fails or is taken offline. Expansion enclosures contain additional drives and are attached to control enclosures. Expansion canisters include the serial-attached SCSI (SAS) interface hardware, enabling the nodes of the control enclosure to manage the drives of the expansion enclosures. Storwize V7000 supports both regular and solid-state drives (SSD). In addition, a Storwize V7000 system, even without any internal drives, can be used as a storage virtualization solution

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

Using Storwize V7000 and SRM for disaster recovery


SRM accelerates and ensures reliable recovery, and simplifies disaster recovery through the following functions: 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.

Storwize V7000 Copy Services features


Storwize V7000 includes the following Copy Services features utilized by SRM: FlashCopy - Creates an instant, point-in-time copy from a source to target volume. Metro Mirror - Provides a consistent copy of a source volume on a target volume. Data is written to the target volume synchronously as it is written to the source volume, so that the copy is continuously updated.

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: Write update with Metro Mirror

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

Prerequisites of Using SRM and IBM Storwize V7000


Before implementing a disaster recovery environment using SRM and Storwize V7000, you must complete the following tasks: 1. At both the sites, set up and configure the applicable networking and the domain name server (DNS). You must test these infrastructure components before installing SRM. 2. Make sure that each site has its own vCenter Server host and SRM server (either physical machines or VMs). You must install VMware ESX on all the servers that hosts VMs. 3. Configure VMware HA at both sites for VMware ESX servers. 4. Configure the databases at each site to support vCenter Server and SRM. 5. Install the SRM server and plug-ins at both sites. Refer to the VMware SRM Administration Guide. See "Installing SRM plug-in ". 6. Configure FlashCopy at the recovery site only. This can also be done by SRA when testing a recovery plan. 7. Configure Metro Mirror for volumes at both sites. Both virtual machine file system (VMFS) and Raw Device Mapping (RDM) logical drives are supported. 8. Configure multipathing according to VMware's best practice configuration.

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

1 3

Configurations for disaster recovery


Test configuration

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): Two VMware ESX 4.1 hosts configured in a VMware HA / DRS cluster IBM Storwize V7000, to provide storage for VMFS datastores A virtual Microsoft Windows 2003 server, running VMware vCenter Server and the SRM plug-in Various other virtual machines

shows a graphical overview of the test configuration.

Hardware information

Figure 4: Overview of test configuration

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 Firmware Version: <<to be confirmed>> 2 * IBM System x3650 M2

Secondary site Server (ESX Hosts): 2 * IBM System x3650 Storage: IBM Storwize V7000 Copy Services features enabled: FlashCopy MetroMirror Firmware Version: <<to be confirmed>>

Software information

VMware: VMware vSphere 4.1: VMware ESX 4.1 vCenter Server 4.1 vSphere Client 4.1

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

1 5

Site Recovery Manager 4.1 Virtual Machine Guest Operating System: Microsoft Windows Server 2003 R2 Enterprise Edition, 64 bit Red Hat Enterprise Linux AS 5 U5 x86_64

SRA: Database: Microsoft SQL Server 2008 Version: v1.20.10713

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

1 6

Configuring the site


SRM is a plug-in for VMware vSphere Client. Both SRM and vCenter Server require a database to store information necessary for operation. In order to function properly, both the protected and recovery sites require a local database. You need to decide on the one to operate as the protected site and the one to operate as the recovery site. Then perform the following steps to complete the configuration:

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

Configuring Storwize V7000


To use SRM, the following Copy Services features, FlashCopy and MetroMirror, should be configured. After setting up these, configure each of the volumes that require protection. Any VMs that are located on a protected datastore are included in the disaster recovery plan. If any VMs do not need protection, carefully consider the logical drive layouts. SRM uses Metro Mirror to mirror volumes from the protected site to the recovery site. Make sure that the sizes of the logical drives avoid unnecessary replication of large logical drives for small VMFS partitions. Smaller volumes provide faster synchronization between primary and secondary sites. In this configuration, the two Storwize V7000 clusters are named StorwizeV7000_P and StorwizeV7000_S. StorwizeV7000_P is used at the protected site and StorwizeV7000_S at the recovery site. In the following section, it is assumed that the source and target VDisks have already been created.

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

1 7

To configure Metro Mirror, perform the following steps: Create Storwize V7000 partnership between StorwizeV7000_P and StorwizeV7000_S, on both Storwize V7000 clusters - bandwidth 50 MB/s Create a Metro Mirror consistency group - name MMCG1 Create the Metro Mirror relationship for vmware_vol_2 - master vmware_vol_2 (id 126) - auxiliary vmware_vol_2A (id 598) - auxiliary Storwize V7000 cluster StorwizeV7000_S - name MMRel1 - consistency group MMCG1 Create the Metro Mirror relationship for vmware_vol_3 - master vmware_vol_3 (id 127) - auxiliary vmware_vol_3A (id 599) - auxiliary Storwize V7000 cluster StorwizeV7000_S - name MMRel2 - consistency group MMCG1

Host and volume configuration

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

Metro Mirror configuration

Creation of Storwize V7000 partnership between StorwizeV7000_P and StorwizeV7000_S: Listing candidate Storwize V7000 clusters for partnership with the protected site ------------------------------------------------------------------------------------------------------------------------------------------StorwizeV7000_P:admin>svcinfo lsclustercandidate id configured name 0000020060215AFC no StorwizeV7000_S ------------------------------------------------------------------------------------------------------------------------------------------Creating the partnership from StorwizeV7000_P to StorwizeV7000_S ------------------------------------------------------------------------------------------------------------------------------------------StorwizeV7000_P:admin>svctask mkpartnership -bandwidth 50 StorwizeV7000_S StorwizeV7000_P:admin>svcinfo lscluster id name location partnership bandwidth id_alias
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

2 0

000002006460532A StorwizeV7000_P local 000002006460532A 0000020060215AFC StorwizeV7000_S remote partially_configured_local 50 000002006020B736 ------------------------------------------------------------------------------------------------------------------------------------------Creating the partnership from StorwizeV7000_S to StorwizeV7000_P (the relationship must be reciprocated) ------------------------------------------------------------------------------------------------------------------------------------------StorwizeV7000_S:admin>svcinfo lsclustercandidate id configured name 000002006460532A yes StorwizeV7000_P StorwizeV7000_S:admin>svctask mkpartnership -bandwidth 50 StorwizeV7000_P StorwizeV7000_S:admin>svcinfo lscluster id name location partnership bandwidth id_alias 0000020060215AFC StorwizeV7000_S local 000002006020B736 000002006460532A StorwizeV7000_P remote fully_configured 50 000002006460532A ------------------------------------------------------------------------------------------------------------------------------------------Creating a Metro Mirror consistency group Creating the MetroMirror consistency group MMCG1 ------------------------------------------------------------------------------------------------------------------------------------------StorwizeV7000_P:admin>svctask mkrcconsistgrp -cluster StorwizeV7000_S -name MMCG1 RC Consistency Group, id [0], successfully created ------------------------------------------------------------------------------------------------------------------------------------------Creating the Metro Mirror relationship for vmware_vol_2 and vmware_vol_3 Creating the MetroMirror relationships MMRel1 and MMRel2 ------------------------------------------------------------------------------------------------------------------------------------------StorwizeV7000_P:admin>svctask mkrcrelationship -master vmware_vol_2 -aux vmware_vol_2A -cluster StorwizeV7000_S -consistgrp MMCG1 -name MMRel1 RC Relationship, id [126], successfully created StorwizeV7000_P:admin>svctask mkrcrelationship -master vmware_vol_3 -aux vmware_vol_3A -cluster StorwizeV7000_S -consistgrp MMCG1 -name MMRel2 RC Relationship, id [127], successfully created StorwizeV7000_P:admin>svcinfo lsrcrelationship id name master_cluster_id master_cluster_name master_vdisk_id master_vdisk_name aux_cluster_id aux_cluster_name aux_vdisk_id aux_vdisk_name primary consistency_group_id consistency_group_name state bg_copy_priority progress copy_type 126 MMRel1 000002006460532A StorwizeV7000_P 126 vmware_vol_2 0000020060215AFC StorwizeV7000_S 598 vmware_vol_2A master 0 MMCG1 inconsistent_stopped 50 0 metro 127 MMRel2 000002006460532A StorwizeV7000_P 127 vmware_vol_3 0000020060215AFC StorwizeV7000_S 599 vmware_vol_3A master 0 MMCG1 inconsistent_stopped 50 0 metro ------------------------------------------------------------------------------------------------------------------------------------------Starting a Metro Mirror consistency group (start the volume synchronization) Starting the MetroMirror consistency group ------------------------------------------------------------------------------------------------------------------------------------------StorwizeV7000_P:admin>svctask startrcconsistgrp MMCG1
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

2 1

StorwizeV7000_P:admin>svcinfo lsrcconsistgrp MMCG1 id 0 name MMCG1 master_cluster_id 000002006460532A master_cluster_name StorwizeV7000_P aux_cluster_id 0000020060215AFC aux_cluster_name StorwizeV7000_S primary master state inconsistent_copying relationship_count 2 freeze_time status sync copy_type metro RC_rel_id 126 RC_rel_name MMRel1 RC_rel_id 127 RC_rel_name MMRel2 StorwizeV7000_P:admin>svcinfo lsrcrelationship id name master_cluster_id master_cluster_name master_vdisk_id master_vdisk_name aux_cluster_id aux_cluster_name aux_vdisk_id aux_vdisk_name primary consistency_group_id consistency_group_name state bg_copy_priority progress copy_type 126 MMRel1 000002006460532A StorwizeV7000_P 126 vmware_vol_2 0000020060215AFC StorwizeV7000_S 598 vmware_vol_2A master 0 MMCG1 consistent_synchronized 50 metro 127 MMRel2 000002006460532A StorwizeV7000_P 127 vmware_vol_3 0000020060215AFC StorwizeV7000_S 599 vmware_vol_3A master 0 MMCG1 consistent_synchronized 50 metro ------------------------------------------------------------------------------------------------------------------------------------------Ensure that all Metro Mirror relationships complete the background copy and the consistency group enters the consistent synchronized state before configuring SRA. (The state, state inconsistent_copying, indicates that the synchronization is still only partial)

Installing and configuring components for disaster recovery


This section describes how to perform the following tasks for installing and configuring components for disaster recovery: 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.

Network Path Redundancy


Network path redundancy between cluster nodes is important for VMware HA reliability. A single service console network ends up being a single point of failure, and can result in failover, although only the network may have failed. If you have only one service console network, any failure between the host and the cluster can cause an unnecessary (or false) failover situation. Potential situations include NIC or network cable failures, network cable removal, and switch resets. Consider ways of minimizing the risk of encountering these error situations, for example, by providing network redundancy. You can implement network redundancy at the NIC level with NIC teaming, or at the service console level. In most implementations, NIC teaming provides sufficient redundancy, but you can use or add service console redundancy, if required. Redundant service console networking on ESX enables reliable detection of failures and prevents the occurrence of isolation conditions, a heartbeat can be sent over multiple networks. shows the network path redundancy configuration.

Figure 5: Network path redundancy configuration

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. Select the Hosts and Clusters view. Right-click Data-center in the Inventory tree and click New Cluster. Complete the New Cluster wizard. Do not enable VMware HA (or DRS) at this time. Click Finish to close the wizard and create the cluster. You have created an empty cluster. Based on your plan for the resources and networking architecture of the cluster, use the vSphere Client to add hosts to the cluster. Right-click the cluster and click Edit Settings. The cluster's Settings dialog box is where you can modify the VMware HA (and other) settings for the cluster On the Cluster Features page, select Turn On VMware HA Configure the VMware HA settings as appropriate for your cluster Host Monitoring Status Admission Control Virtual Machine Options VM Monitoring

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

Installing SRM plug-in


To install the Site Recovery Manager client plug-in, use a vSphere Client to connect to the vCenter Server at the protected or recovery site with SRM installed. Then, download the plug-in from the server and enable it in the vSphere Client. 1. If not already installed, install VMware vSphere client. Start the vSphere Client and connect to vCenter Server at the protected or recovery site 2. On the vSphere Client menu bar, select Plug-ins option, and then select Manage Plug-ins. 3. In the Available Plug-ins area of the Plug-in Manager window, click Download and Install if SRM Server is detected. 4. After installing the plug-in in the Installed Plug-ins area, the plug-in should set to Enabled state. A new Site Recovery icon appears in the Home page in the vSphere client.

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

2 5

Figure 6: SRM plug-in

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

2 6

Installing and configuring SRA for IBM Storwize V7000


SRA is an interface between the storage subsystem and SRM. SRA provides a means of controlling storage subsystem features, such as replication and FlashCopy. The various SRAs provide SRM with support for a range of storage subsystems, without SRM requiring any specific awareness of any given product. SRA should be provided by the storage vendor and installed on the server running SRM.

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

Figure 7: SRA configuration

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

Introduction to each item: 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 R2 Failover Policy with Auto Switch Replication This procedure does not require any specific SRA-related administration from the user, provided that the steps and prerequisites mentioned in this paper are complied with. After the recovery (failover) has been completed, the Metro Mirror copy direction should be switched (only if the protected site Storwize V7000 is online). R2 Failover Policy without Auto Switch Replication If the Auto Switch Replication option is not selected, the Metro Mirror relationships and the consistency groups are stopped and their status changes to idling. 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 an SRM server at each site. 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.

The options include: Connection Array Managers Inventory Mappings Protection Groups Recovery Plans

Set up these options in the order they are listed.

Creating site pair


Before you can use SRM, you must designate the protected site and the recovery site, and then connect them. The sites must authenticate each other.

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.

Figure 8: Pairing primary and secondary sites

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

3 1

7. To complete the pairing, enter the user name and password.

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.

Figure 9: Completed paired sites

Configuring array managers


Array managers are used to define the storage for SRM. It also enables SRM, through the SRA, to control the replication of data between the primary and secondary sites. Note: Array manager refers to the IP addresses of the two storage controllers. The two array managers are the protection site array manager and the recovery site array manager. The protection side storage subsystem is the storage subsystem on the primary site. The recovery side storage subsystem is the storage subsystem on the secondary site.

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. Display Name - Enter the name of your array. 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. Username - Enter the user name configured on the CIM agent. 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

Figure 10: Adding an array manager

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

Figure 11: Configuring an array manager

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

Figure 12: Completing array manager configuration

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.

Figure 13: Reviewing configured 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.

Configuring inventory mappings


Inventory mappings establish recovery site defaults for the folders, networks, and resource pools to which recovered virtual machines are assigned. These mappings are created at the protected site, and they should apply to all virtual machines in all protection groups at that site. Ensure that resources at the protected site are mapped to resources at the recovery site. These mappings are applied to all members of a protection group when the group is created, and can be
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

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.

Figure 14: Verifying resource mapping

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

3 9

Creating a protection group


A protection group is a group of VMs that are intended to failover together. Grouping such VMs together on a single VM file system (VMFS) LUN is convenient. This procedure is also preferred because a one-to-one relationship between a protection group and a datastore exists. Protection groups are created on the primary site vCenter server.

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.

Figure 15: Creating a protection group


Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

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.

Figure 16: Protection group summary

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.

Figure 17: Reviewing placeholder virtual machines

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

4 1

Creating a recovery plan


A recovery plan is the sequence of steps SRM performs at the secondary site when a true DR scenario occurs or when a DR plan is being tested. A recovery plan contains protection groups from the primary site. Recall that the protection groups contain VMs. All of these VMs will be recovered by the recovery plan.

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.

Figure 18: Creating a recovery plan for a protection group

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.

Figure 19: Suspend local virtual machine configuration

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

10. Review the recovery plan steps.

Figure 20: Reviewing the recovery plan

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

4 5

Implementing a disaster recovery plan


After you have configured SRM on both the protected and recovery sites, you can test your recovery plan without affecting services at either site. You can also run a recovery plan and, if necessary, configure the two sites for failback so that you can restore services at the protected site.

Testing the disaster recovery plan


When you test a recovery plan, you use a test network and a temporary copy of replicated data at the recovery site. No operations are disrupted at the protected site. Testing a recovery plan will complete all the required steps, with the exception of powering down virtual machines at the protected site and forcing devices at the recovery site to assume mastership of replicated data. If the plan requests suspension of local virtual machines at the recovery site, they are suspended during the test recovery. A test recovery makes no other changes to the production environment at either site. SRM performs this task with copy-on-write flash copies of the mirrored logical drives at the recovery site. During the recovery plan configuration, you can suspend noncritical VMs on the recovery site to make sure that you have enough resources to run the DR test. Note: The Storage Replication Adapter must have sufficient free space on the storage. To test the disaster recovery plan: 1. In the Commands area of the Summary window, click Test Recovery Plan. At the confirmation prompt, click Yes to proceed with the test. Starting the test creates flash copies of all datastores (protection groups) included in the recovery plan to the recovery site storage, and then maps these targets to the Recovery Site ESX hosts as read or write logical drives. When the logical drives are mapped to the ESX hosts, SRM starts point-in-time versions of each of the VMs that are contained on the replicated datastores. In the background, the base logical drive (secondary mirrored logical drive) is still replicating write operations rom the primary logical drive. After bringing all VMs online, the recovery plan pauses to provide verification of the VMs. 2. After verification, click Continue to proceed to Test stop. Use the Stop icon at any time in the start phase. This process starts the clean-up of the start phase. All FlashCopy datastores are unmapped and deleted. The FlashCopy datastores are removed from the recovery host. SRM rescans the host bus adapters and resets the environment to the state that the system was in before the start function was initiated.

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

4 6

Figure 21: completing test recovery

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

4 7

Network isolation when testing the Disaster Recovery Plan


When performing a disaster recovery plan, SRM creates a test bubble network on recovery side ESX host to which recovered virtual machines are connected during test. This network is not automatically connected to any physical network adapters and so provides no connectivity between ESX hosts. It is managed by its own virtual switch, and in most cases recovered virtual machines can use it without having to change network properties such as IP address, gateway, and so on.

Figure 22: Test bubble network on recovery ESX host

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

4 8

Running the disaster recovery plan


Declaring a disaster and running the applicable recovery plans requires manual intervention. You can set up SRM to notify administrators when communication with the remote site is lost. Using these notifications and other alerts, the administrator can decide when a disaster has occurred and whether to carry out a recovery plan. Running a recovery plan is also called instigating a failover. If a failure of primary site computer resources occurs, and you need to instigate a failover to the recovery site, the process is similar to the test operation but just with one key exception. Failover promotes logical drives instead of creating FlashCopy datastores. In the Site Recovery tree view, expand the Recovery Plans icon and click the required recovery plan. In the Commands area of the Summary tab, click Run Recovery Plan.

Figure 23: Reviewing recovery plan summary

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

4 9

The following activities occur when a recovery plan is running: 1. SRM attempts to shut down protected VMs by sending a shutdown command to the OS. 2. On the DR site storage subsystem, SRA promotes the secondary logical drives to primary logical drives. Promotion provides read-write capability on the recovery site and makes the primary site logical drives read-only. The newly promoted logical drives are mapped to the appropriate host or the appropriate host group. 3. VMs from the newly-promoted recovery site logical drives are started on the recovery site computer resources. To monitor the progress of the recovery and respond to messages, click the Recovery Steps tab. The Recovery Steps tab presents the progress of the individual steps. The Recent Tasks area reports the overall progress of the plan.

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

5 0

Figure 24: Reviewing recovery steps

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

Figure 25: Verifying virtual machine on recovery site

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
Review and execute post-failover cleanup tasks Before you can execute a failback, you must remove artifacts, such as invalid protection groups and place holders that are no longer required, left over from the previous configuration. Reconfigure replication Failover stops replication. Failback requires you to configure replication in reverse, from the recovery site to the formerly protected site. Restoring the protected and recovery sites to their original roles requires you to configure replication from the protected site to the recovery site, as it was before the original failover was executed. Reconfigure SRM to enable failback to the protected site Before you can run a failback, you must create the protection groups and recovery plans required to migrate protected inventory from the recovery site back to the protected site. Restore the original configuration After a failback is complete, you can restore the original configuration so that the protected and recovery sites resume the roles they had before the failover.

So the following steps need to be performed manually in order to process a failback: 1. Recover the original primary site computer and storage resources. 2. Rescan the storage subsystem adapters on the primary hosts, and remove any inaccessible VMs from the inventory. These VMs might be inaccessible because the original primary site's mirrored logical drives are set to read-only. If these VMs are not unregistered, name conflicts may occur. 3. On the original primary site, clean the protection setup which is the new secondary site. 4. On the original secondary site, remove the recovery plan which is the new primary site. 5. Establish appropriate array replication from original secondary site to original primary site for the datastores containing recovered virtual machines. Switch Metro Mirror relationships' and consistency groups' copy direction. In this paper, the SRA is configured with R2 Failover Policy with Auto Switch Replication, so the original primary site storage is automatically defined as the recovery site storage and the former recovery site storage is automatically defined as the primary site storage. This mirror relationship of the storage is automatically configured after failover is completed.

The current Metro Mirror relationship on storage: ---------------------------------------------------------------------------------------------------------------------------------StorwizeV7000_P:admin>svcinfo lsrcrelationship id name master_cluster_id master_cluster_name master_vdisk_id master_vdisk_name aux_cluster_id aux_cluster_name aux_vdisk_id aux_vdisk_name primary consistency_group_id consistency_group_name state bg_copy_priority progress copy_type 126 MMRel1 000002006460532A StorwizeV7000_P 126 vmware_vol_2
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

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.

You need to perform the following steps to change the setting:


Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

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.

Figure 26: Advanced settings bout SanProvider

Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

5 5

Collect SRM server log files


SRM creates several log files that contain information that can help VMware Support diagnose problems. SRM log collector simplifies log file collection and stores them in a compressed (zipped) folder on the host's graphical desktop.

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

Configuring protection for a virtual machine


In a protection group, virtual machine protection properties may be configured, such as resource mappings, attached storage devices, their datastores, and recovery priority. This provides the flexibility to define which specific resources need to be protected.

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: IBM Systems on PartnerWorld ibm.com/partnerworld/systems Getting Started with VMware vCenter Site Recovery Manager Technical Note http://www.vmware.com/pdf/srm_40_gettingstarted.pdf Site Recovery Manager Administration Guide for vCenter Site Recovery Manager 4.1 http://www.vmware.com/pdf/srm_admin_4_1.pdf vSphere Availability Guide for ESX 4.1 http://www.vmware.com/pdf/vsphere4/r41/vsp_41_availability.pdf ESX and vCenter Server Installation Guide for ESX 4.1 http://www.vmware.com/pdf/vsphere4/r41/vsp_41_esx_vc_installation_guide.pdf Guest Operating System Installation Guide http://www.vmware.com/pdf/GuestOS_guide.pdf IBM Redbooks ibm.com/redbooks IBM Publications Center http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi?CTY=US Microsoft SQL Server 2008 Online Books http://technet.microsoft.com/en-us/library/bb418439(SQL.10).aspx

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

Trademarks and special notices


Copyright IBM Corporation 2010. All rights Reserved. References in this document to IBM products or services do not imply that IBM intends to make them available in every country. IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. Other company, product, or service names may be trademarks or service marks of others. Information is provided "AS IS" without warranty of any kind. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Information concerning non-IBM products was obtained from a supplier of these products, published announcement material, or other publicly available sources and does not constitute an endorsement of such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly available information, including vendor announcements and vendor worldwide homepages. IBM has not tested these products and cannot confirm the accuracy of performance, capability, or any other claims related to non-IBM products. Questions on the capability of non-IBM products should be addressed to the supplier of those products. All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Contact your local IBM office or IBM authorized reseller for the full text of the specific Statement of Direction. Some information addresses anticipated future capabilities. Such information is not intended as a definitive statement of a commitment to specific levels of performance, function or delivery schedules with respect to any future products. Such commitments are only made in IBM product announcements. The information is
Implementing disaster recovery solutions with IBM Storwize V7000 and VMware Site Recovery Manager Copyright IBM Corporation, 2010

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

Вам также может понравиться