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

Size: px
Start display at page:

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

Transcription

1 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 January 2011

2 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 V Overview of VMware vcenter Site Recovery Manager with IBM Storwize V VMware Overview... 2 VMware vsphere 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 V Storwize V7000 software... 8 Storwize V7000 hardware... 9 Using Storwize V7000 and SRM for disaster recovery Storwize V7000 Copy Services features FlashCopy Metro Mirror Prerequisites of Using SRM and IBM Storwize V Configurations for disaster recovery Test configuration Hardware information Primary site Secondary site Software information Configuring the site Configuring Storwize V Host and volume configuration Metro Mirror configuration Installing and configuring components for disaster recovery Configuring VMware HA Prerequisites Network Path Redundancy Procedure Installing SRM plug-in Installing and configuring SRA for IBM Storwize V Installing an SRA Configuring SRA... 32

3 Configuring SRM Creating site pair Prerequisites Procedure Configuring array managers Prerequisites Procedure Configuring inventory mappings Procedure Creating a protection group Prerequisites Procedure Creating a recovery plan Procedure Implementing a disaster recovery plan Testing the disaster recovery plan Network isolation when testing the Disaster Recovery Plan Running the disaster recovery plan After you instigate a failover, the failover process is irreversible, except by following the steps outlined in the rming failback in the rming failbackrming failback Procedures Troubleshooting SRM Modification of the PATH environment variable for the VMware SRM user on the SRM server Modification timeout for executing a single command using array vendor adapter Collect SRM server log files Procedure Best practices Customizing recovery plan Configuring protection for a virtual machine Conclusion Resources Glossary of terms Trademarks and special notices... 68

4 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. 1

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

6 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). Figure 1: VMware components interacting 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 3

7 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, Figure 2: Site Recovery Manager architecture, shows the Site Recovery Manager architecture. 4

8 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. 5

9 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. 6

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

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

12 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 3: Storwize V7000 with internal RAID storage and external virtualized storage systems. 9

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

14 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 4: Write update with Metro Mirror Figure 4: Write update with Metro Mirror 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. 11

15 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. 12

16 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 host 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. 13

17 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 Figure 5: Overview of test configuration shows a graphical overview of the test configuration. Hardware information Figure 5: Overview of test configuration 14

18 Primary site Server (ESX Hosts): 2 * IBM System x3650 M2 Storage: IBM Storwize V7000 Copy Services features enabled: FlashCopy MetroMirror Firmware Version: Secondary site Server (ESX Hosts): 2 * IBM System x3650 Storage: IBM Storwize V7000 Copy Services features enabled: FlashCopy MetroMirror Firmware Version: Software information VMware: VMware vsphere 4.1: VMware ESX 4.1 vcenter Server 4.1 vsphere Client 4.1 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: Version: v Database: Microsoft SQL Server

19 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 ARCTBG00SC and ARCTBG00G3. ARCTBG00SC is used at the protected site and ARCTBG00G3 at the recovery site. The following section discusses the tasks to be performed by the storage administrator to configure Storwize V7000 for Metro Mirror using Storwize V7000 management GUI 16

20 Storwize V7000 includes an easy-to-use management GUI to help you monitor, manage, and configure your system. You can easily access the management GUI by opening a supported web browser and entering a system IP addresses. You can connect from any workstation that is able to communicate with the cluster Before configuring Metro Mirror, perform the following steps to configure hosts and volumes. Create hosts on protected site storage - name vmware_wdfhv - name vmware_wdfht Create hosts on recovery site storage - name vmware_chmak - name vmware_gnxt5 Create volumes on protected site storage - name vmware_vol_1 (Used for Configuring VMware vcenter Server) - name vmware_vol_2 - name vmware_vol_3 Create volumes on recovery site storage - name vmware_vol_1 (Used for Configuring VMware vcenter Server) - name vmware_vol_2a - name vmware_vol_3a Create hosts-volumes-mapping on protected site storage. 17

21 To configure Metro Mirror, perform the following steps: Create Storwize V7000 partnership between ARCTBG00SC and ARCTBG00G3 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 - auxiliary vmware_vol_2a - auxiliary Storwize V7000 cluster ARCTBG00G3 - consistency group MMCG1 Create the Metro Mirror relationship for vmware_vol_3 - master vmware_vol_3 - auxiliary vmware_vol_3a - auxiliary Storwize V7000 cluster ARCTBG00G3 - consistency group MMCG1 18

22 Host and volume configuration The management of hosts and their connections or mappings to volumes is invoked by clicking the corresponding icon located on the left side of the main GUI window. Creating hosts To create the host on Storwize V7000, in the management GUI interface, select the Hosts Icon >> All Hosts. In the All Hosts screen, select New Host. Here we configure Fibre-Channel Host Type. When trying to define a new host, remember that the host s name must be unique in the system. Figure 6 shows the Create Host dialogue box for one of the ESX servers Figure 6 Creating Host Follow these steps to create additional hosts on Storwize V7000. Figures 7 and 8 show the hosts information on both protected and recovery sites. Figure 7 Hosts information on Protected Site 19

23 Figure 8 Hosts information on Recovery Site Creating volumes In the Storwize V7000 management interface select the Volumes Icon >> All Volumes. In the All Volumes screen select New Volume. A dialogue box as shown in Figure 9 is displayed. Figure 9 Creating Volume After selecting the desired preset for Generic, Thin Provisioned, Mirrored or Thin Mirror, you have the option to select the storage pool that these volumes will provisioned from. In this example, there is a storage pool named mdiskgrp0. Enter the desired volume name and capacity. The volume name must start with a letter and may contain numbers, spaces and underscores. 20

24 You may create additional volumes by selecting the + symbol, to the right of the capacity. If you click Create and Map to Host, once the volumes have been created, the Modify Mappings window (as shown in Figure 8) appears. Select the host that you are working with, and from the left panel select the volume you wish to map to the host. Use the > symbol to map the volume to the host. To work with additional host mappings, click Apply instead of OK. Clicking Apply will keep the Modify Mapping window open and you can select another host in the upper-left corner of the window. Figure 10 Mapping volumes to Host After clicking OK on the Modify Mappings screen, you can check the volumes mapping information, as shown in figure 11. Figure 11 Volumes information after mapping to hosts. vmware_vol_2 and vmware_vol_3 are used for virtual machine datastore and configured for Metro Mirror. 21

25 Metro Mirror configuration Creation of Storwize V7000 partnership between ARCTBG00SC and ARCTBG00G3: To create a partnership between a pair of Storwize V7000s, in the management GUI interface, select the Copy Services Icon >> Partnerships. In the Partnerships screen, select New Partnership. Create Partnership on both protected and recovery site Storwize V7000. Create Partnership on protected site ARCTBG00SC first. Figure 12 Creating Partnership Cluster: Select the remote Storwize V7000 cluster once you have created zoning between protected and recovery site Storwize V7000 Bandwidth: (in megabytes per second) used by the background copy process between the clusters. Figure 13 shows the partnership information once it has been created on the protected site Storwize V7000. The status is Partially Configured: Local. Figure 13 Partnership information on Protected Site Storwize V

26 Figure 14 shows partnership information once it has been reciprocated on the recovery site Storwize V7000. The status becomes Fully Configured. Figure 14 Partnership information on Recovery Site Storwize V7000. Note: The partnership status on two sites should be Fully Configured once partnership creation is set up on both protected and recovery sites. Creating a Metro Mirror consistency group To create the Consistency Group on Storwize V7000, in the management GUI interface, select the Copy Services Icon >> Remote Copy. In the Remote Copy screen, select New Consistency Group. Create Consistency Group MMCG1 on protected Storwize V7000 ARCTBG00SC for volumes vmware _vol_2 and vmware_vol_3. Select auxiliary volumes located on cluster ARCTBG00G3 as shown in figure 15. Figure 15 Selecting auxiliary cluster for Consistency Group 23

27 Here we create an empty consistency group - We will add the relationships later. Figure 16 Opting to create an empty consistency group. Figure 17 shows successful creation of a Consistency Group, MMCG1, between ARCTBG00DC and ARCTBG00G3. Figure 17 Creating a Consistency Group. 24

28 Creating the Metro Mirror relationship for vmware_vol_2 and vmware_vol_3 To create the Relationship on Storwize V7000, in the management GUI interface, select Copy Services Icon >> Remote Copy. In the Remote Copy screen, select Add Relationship under Actions menu. In the Add Relationship screen, select Metro Mirror for Step 1. Figure 18 Selecting Metro Mirror type for relationships. Select the master and auxiliary volumes for the remote copy consistency group. Here we create two relationships. Figure 19 Selecting master and auxiliary volumes. 25

29 The volumes are not synchronized, so select No, the volumes are not synchronized option, as shown in figure 20. Figure 20: Selecting not synchronized option After successfully creating relationships, the MMCG1 status is Inconsistent Stopped. Figure 21: Creating Relationships 26

30 Starting a Metro Mirror consistency group (start the volume synchronization) To start a Metro Mirror consistency group on Storwize V7000, in the management GUI interface, select the Copy Services Icon >> Remote Copy. In the Remote Copy screen, select the consistency group, MMCG1, and select Start under the Actions menu. Figure 22: Starting the MetroMirror consistency group The initial relationship state will be Inconsistent Copying. After successfully synchronizing the master and auxiliary volumes, the state will become Consistent Synchronized at both sites, as shown in figure 23. Figure 23:Consistent Synchronized 27

31 Ensure that all Metro Mirror relationships complete the background copy, and the consistency group enters the consistent synchronized state before configuring SRA. (The 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. 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 28

32 sent over multiple networks. Figure 24: Network path redundancy configuration shows the network path redundancy configuration. Figure 24: Network path redundancy configuration Procedure To connect vsphere Client to vcenter Server using an account with cluster administrator permissions: Select the Hosts and Clusters view. 3. Right-click Data-center in the Inventory tree and click New Cluster. 4. Complete the New Cluster wizard. Do not enable VMware HA (or DRS) at this time. 5. Click Finish to close the wizard and create the cluster. 6. You have created an empty cluster. 7. Based on your plan for the resources and networking architecture of the cluster, use the vsphere Client to add hosts to the cluster. 8. Right-click the cluster and click Edit Settings. 9. The cluster's Settings dialog box is where you can modify the VMware HA (and other) settings for the cluster 10. On the Cluster Features page, select Turn On VMware HA 11. 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. 29

33 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. 30

34 Figure 25:SRM plug-in 31

35 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: 1. Download SRA from the URL: 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 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 will need to create 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. 32

36 Figure 26: SRA configuration Double-clicking the SRA shortcut at the recovery site should bring up the window, as shown in Figure 26: SRA configuration. 33

37 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 pre-mapped 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. 34

38 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. 35

39 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 administrator s 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 27: Pairing primary and secondary sites 36

40 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 28: 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. 37

41 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, :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 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 V

42 Figure 29: Adding an array manager 4. Click OK to query the selected arrays and discover which of their devices are replicated. 39

43 Figure 30: 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. 40

44 Figure 31: Completing array manager configuration 41

45 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 32: 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 42

46 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. 43

47 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. Figure 33: Verifying resource mapping shows the resources that are in use on the primary site map, compared to the resources of the recovery site. Figure 33: Verifying resource mapping 44

48 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 34: Creating a protection group 45

49 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 35: 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 36: Reviewing placeholder virtual machines 46

50 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 37: Creating a recovery plan for a protection group 47

51 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. 48

52 8. On the Suspend Local Virtual Machines page, select the virtual machines at the recovery site that the recovery plan should suspend. Figure 38: 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. 49

53 10. Review the recovery plan steps. Figure 39: Reviewing the recovery plan 50

54 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 non-critical 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 from 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. 51

55 Figure 40: completing test recovery 52

56 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 41: Test bubble network on recovery ESX host 53

57 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 42: Reviewing recovery plan summary 54

58 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. 55

59 Figure 43: Reviewing recovery steps 56

60 The protected virtual machines should now have been powered on at the recovery site. You can view their state from the Virtual Machines tab. Figure 44: Verifying virtual machine on recovery site Note: You must place protection groups and the recovery plans that operate them on separate sites. 57

61 After you instigate a failover, the failover process is irreversible, except by following the steps outlined in the rming failback in the rming failbackrming 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. 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. 58

62 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. Right-click My Computer, 1. Click Properties, and select the Advanced tab. 2. Click Environment Variables. 3. In the System Variables window, scroll down and select PATH. 4. Click Edit. 5. 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: 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 45: Advanced settings bout SanProvider 59

Setup for Failover Clustering and Microsoft Cluster Service

Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service ESX 4.0 ESXi 4.0 vcenter Server 4.0 This document supports the version of each product listed and supports all subsequent versions until the

More information

Veritas Storage Foundation High Availability for Windows by Symantec

Veritas Storage Foundation High Availability for Windows by Symantec Veritas Storage Foundation High Availability for Windows by Symantec Simple-to-use solution for high availability and disaster recovery of businesscritical Windows applications Data Sheet: High Availability

More information

VMware Site Recovery Manager with EMC RecoverPoint

VMware Site Recovery Manager with EMC RecoverPoint VMware Site Recovery Manager with EMC RecoverPoint Implementation Guide EMC Global Solutions Centers EMC Corporation Corporate Headquarters Hopkinton MA 01748-9103 1.508.435.1000 www.emc.com Copyright

More information

Using EonStor FC-host Storage Systems in VMware Infrastructure 3 and vsphere 4

Using EonStor FC-host Storage Systems in VMware Infrastructure 3 and vsphere 4 Using EonStor FC-host Storage Systems in VMware Infrastructure 3 and vsphere 4 Application Note Abstract This application note explains the configure details of using Infortrend FC-host storage systems

More information

Availability Guide for Deploying SQL Server on VMware vsphere. August 2009

Availability Guide for Deploying SQL Server on VMware vsphere. August 2009 Availability Guide for Deploying SQL Server on VMware vsphere August 2009 Contents Introduction...1 SQL Server 2008 with vsphere and VMware HA/DRS...2 Log Shipping Availability Option...4 Database Mirroring...

More information

Setup for Failover Clustering and Microsoft Cluster Service

Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service Update 1 ESX 4.0 ESXi 4.0 vcenter Server 4.0 This document supports the version of each product listed and supports all subsequent versions until

More information

Symantec Storage Foundation High Availability for Windows

Symantec Storage Foundation High Availability for Windows Symantec Storage Foundation High Availability for Windows Storage management, high availability and disaster recovery for physical and virtual Windows applications Data Sheet: High Availability Overview

More information

Setup for Failover Clustering and Microsoft Cluster Service

Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service Update 1 ESXi 5.1 vcenter Server 5.1 This document supports the version of each product listed and supports all subsequent versions until the

More information

VMware vsphere 5.1 Advanced Administration

VMware vsphere 5.1 Advanced Administration Course ID VMW200 VMware vsphere 5.1 Advanced Administration Course Description This powerful 5-day 10hr/day class is an intensive introduction to VMware vsphere 5.0 including VMware ESX 5.0 and vcenter.

More information

Drobo How-To Guide. Topics Drobo and vcenter SRM Basics Configuring an SRM solution Testing and executing recovery plans

Drobo How-To Guide. Topics Drobo and vcenter SRM Basics Configuring an SRM solution Testing and executing recovery plans VMware Site Recovery Manager (SRM) was designed to simplify DR by eliminating complex runbooks, orchestrating the workflow of failover, and enabling automation of parts of that workflow. VMware SRM leverages

More information

Bosch Video Management System High availability with VMware

Bosch Video Management System High availability with VMware Bosch Video Management System High availability with VMware en Technical Note Bosch Video Management System Table of contents en 3 Table of contents 1 Introduction 4 1.1 Restrictions 4 2 Overview 5 3

More information

Site Recovery Manager Installation and Configuration

Site Recovery Manager Installation and Configuration Site Recovery Manager Installation and Configuration vcenter Site Recovery Manager 5.5 This document supports the version of each product listed and supports all subsequent versions until the document

More information

Microsoft System Center 2012 SP1 Virtual Machine Manager with Storwize family products. IBM Systems and Technology Group ISV Enablement January 2014

Microsoft System Center 2012 SP1 Virtual Machine Manager with Storwize family products. IBM Systems and Technology Group ISV Enablement January 2014 Microsoft System Center 2012 SP1 Virtual Machine Manager with Storwize family products IBM Systems and Technology Group ISV Enablement January 2014 Copyright IBM Corporation, 2014 Table of contents Abstract...

More information

Disaster Recovery with EonStor DS Series &VMware Site Recovery Manager

Disaster Recovery with EonStor DS Series &VMware Site Recovery Manager Disaster Recovery with EonStor DS Series &VMware Site Recovery Manager Application Note Version: 1.0 Updated: July, 2015 Abstract: This application note provides information about Infortrend Storage Replication

More information

VMware for Bosch VMS. en Software Manual

VMware for Bosch VMS. en Software Manual VMware for Bosch VMS en Software Manual VMware for Bosch VMS Table of Contents en 3 Table of contents 1 Introduction 4 1.1 Restrictions 4 2 Overview 5 3 Installing and configuring ESXi server 6 3.1 Installing

More information

StarWind Virtual SAN Installation and Configuration of Hyper-Converged 2 Nodes with Hyper-V Cluster

StarWind Virtual SAN Installation and Configuration of Hyper-Converged 2 Nodes with Hyper-V Cluster #1 HyperConverged Appliance for SMB and ROBO StarWind Virtual SAN Installation and Configuration of Hyper-Converged 2 Nodes with MARCH 2015 TECHNICAL PAPER Trademarks StarWind, StarWind Software and the

More information

SAN Conceptual and Design Basics

SAN Conceptual and Design Basics TECHNICAL NOTE VMware Infrastructure 3 SAN Conceptual and Design Basics VMware ESX Server can be used in conjunction with a SAN (storage area network), a specialized high speed network that connects computer

More information

Setup for Failover Clustering and Microsoft Cluster Service

Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service ESX 4.1 ESXi 4.1 vcenter Server 4.1 This document supports the version of each product listed and supports all subsequent versions until the

More information

Downtime, whether planned or unplanned,

Downtime, whether planned or unplanned, Deploying Simple, Cost-Effective Disaster Recovery with Dell and VMware Because of their complexity and lack of standardization, traditional disaster recovery infrastructures often fail to meet enterprise

More information

EMC Virtual Infrastructure for SAP Enabled by EMC Symmetrix with Auto-provisioning Groups, Symmetrix Management Console, and VMware vcenter Converter

EMC Virtual Infrastructure for SAP Enabled by EMC Symmetrix with Auto-provisioning Groups, Symmetrix Management Console, and VMware vcenter Converter EMC Virtual Infrastructure for SAP Enabled by EMC Symmetrix with Auto-provisioning Groups, VMware vcenter Converter A Detailed Review EMC Information Infrastructure Solutions Abstract This white paper

More information

Violin Memory Arrays With IBM System Storage SAN Volume Control

Violin Memory Arrays With IBM System Storage SAN Volume Control Technical White Paper Report Best Practices Guide: Violin Memory Arrays With IBM System Storage SAN Volume Control Implementation Best Practices and Performance Considerations Version 1.0 Abstract This

More information

IMPROVING VMWARE DISASTER RECOVERY WITH EMC RECOVERPOINT Applied Technology

IMPROVING VMWARE DISASTER RECOVERY WITH EMC RECOVERPOINT Applied Technology White Paper IMPROVING VMWARE DISASTER RECOVERY WITH EMC RECOVERPOINT Applied Technology Abstract EMC RecoverPoint provides full support for data replication and disaster recovery for VMware ESX Server

More information

VMware vsphere Replication Administration

VMware vsphere Replication Administration VMware vsphere Replication Administration vsphere Replication 6.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new

More information

Setup for Failover Clustering and Microsoft Cluster Service

Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service ESXi 5.0 vcenter Server 5.0 This document supports the version of each product listed and supports all subsequent versions until the document

More information

VMware vsphere 5.0 Boot Camp

VMware vsphere 5.0 Boot Camp VMware vsphere 5.0 Boot Camp This powerful 5-day 10hr/day class is an intensive introduction to VMware vsphere 5.0 including VMware ESX 5.0 and vcenter. Assuming no prior virtualization experience, this

More information

IBM Tivoli Storage Manager for Virtual Environments Version 7.1.6. Data Protection for VMware User's Guide IBM

IBM Tivoli Storage Manager for Virtual Environments Version 7.1.6. Data Protection for VMware User's Guide IBM IBM Tivoli Storage Manager for Virtual Environments Version 7.1.6 Data Protection for VMware User's Guide IBM IBM Tivoli Storage Manager for Virtual Environments Version 7.1.6 Data Protection for VMware

More information

VMware@SoftLayer Cookbook Disaster Recovery (DR)

VMware@SoftLayer Cookbook Disaster Recovery (DR) VMware@SoftLayer Cookbook Disaster Recovery (DR) IBM Global Technology Services: Khoa Huynh (khoa@us.ibm.com) Daniel De Araujo (ddearaujo@us.ibm.com) Bob Kellenberger (kellenbe@us.ibm.com) VMware: Merlin

More information

VMware vcloud Air - Disaster Recovery User's Guide

VMware vcloud Air - Disaster Recovery User's Guide VMware vcloud Air - Disaster Recovery User's Guide vcloud Air This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition.

More information

Site Recovery Manager Administration Guide

Site Recovery Manager Administration Guide Site Recovery Manager Administration Guide vcenter Site Recovery Manager 5.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

Advanced VMware Training

Advanced VMware Training Goals: Demonstrate VMware Fault Tolerance in action Demonstrate Host Profile Usage How to quickly deploy and configure several vsphere servers Discuss Storage vmotion use cases Demonstrate vcenter Server

More information

Veritas Cluster Server from Symantec

Veritas Cluster Server from Symantec Delivers high availability and disaster recovery for your critical applications Data Sheet: High Availability Overview protects your most important applications from planned and unplanned downtime. Cluster

More information

VMware vcenter Server 5.5 Deployment Guide TECHNICAL MARKETING DOCUMENTATION V 1.0/NOVEMBER 2013/JUSTIN KING

VMware vcenter Server 5.5 Deployment Guide TECHNICAL MARKETING DOCUMENTATION V 1.0/NOVEMBER 2013/JUSTIN KING VMware 5.5 TECHNICAL MARKETING DOCUMENTATION V 1.0/NOVEMBER 2013/JUSTIN KING Table of Contents Overview.... 3 Components of 5.5.... 3 vcenter Single Sign-On.... 3 vsphere Web Client.... 3 vcenter Inventory

More information

VMware vsphere-6.0 Administration Training

VMware vsphere-6.0 Administration Training VMware vsphere-6.0 Administration Training Course Course Duration : 20 Days Class Duration : 3 hours per day (Including LAB Practical) Classroom Fee = 20,000 INR Online / Fast-Track Fee = 25,000 INR Fast

More information

Microsoft SharePoint 2010 on VMware Availability and Recovery Options. Microsoft SharePoint 2010 on VMware Availability and Recovery Options

Microsoft SharePoint 2010 on VMware Availability and Recovery Options. Microsoft SharePoint 2010 on VMware Availability and Recovery Options This product is protected by U.S. and international copyright and intellectual property laws. This product is covered by one or more patents listed at http://www.vmware.com/download/patents.html. VMware

More information

VMware Virtual Machine File System: Technical Overview and Best Practices

VMware Virtual Machine File System: Technical Overview and Best Practices VMware Virtual Machine File System: Technical Overview and Best Practices A VMware Technical White Paper Version 1.0. VMware Virtual Machine File System: Technical Overview and Best Practices Paper Number:

More information

Acronis Backup & Recovery 10 Advanced Server Virtual Edition. Quick Start Guide

Acronis Backup & Recovery 10 Advanced Server Virtual Edition. Quick Start Guide Acronis Backup & Recovery 10 Advanced Server Virtual Edition Quick Start Guide Table of contents 1 Main components...3 2 License server...3 3 Supported operating systems...3 3.1 Agents... 3 3.2 License

More information

Setup for Microsoft Cluster Service ESX Server 3.0.1 and VirtualCenter 2.0.1

Setup for Microsoft Cluster Service ESX Server 3.0.1 and VirtualCenter 2.0.1 ESX Server 3.0.1 and VirtualCenter 2.0.1 Setup for Microsoft Cluster Service Revision: 20060818 Item: XXX-ENG-QNNN-NNN You can find the most up-to-date technical documentation on our Web site at http://www.vmware.com/support/

More information

Dell PowerVault MD32xx Deployment Guide for VMware ESX4.1 Server

Dell PowerVault MD32xx Deployment Guide for VMware ESX4.1 Server Dell PowerVault MD32xx Deployment Guide for VMware ESX4.1 Server A Dell Technical White Paper PowerVault MD32xx Storage Array www.dell.com/md32xx THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND

More information

Installing and Administering VMware vsphere Update Manager

Installing and Administering VMware vsphere Update Manager Installing and Administering VMware vsphere Update Manager Update 1 vsphere Update Manager 5.1 This document supports the version of each product listed and supports all subsequent versions until the document

More information

VMware vsphere: Install, Configure, Manage [V5.0]

VMware vsphere: Install, Configure, Manage [V5.0] VMware vsphere: Install, Configure, Manage [V5.0] Gain hands-on experience using VMware ESXi 5.0 and vcenter Server 5.0. In this hands-on, VMware -authorized course based on ESXi 5.0 and vcenter Server

More information

Implementing HP 3PAR Remote Copy with VMware vcenter Site Recovery Manager

Implementing HP 3PAR Remote Copy with VMware vcenter Site Recovery Manager Technical white paper Implementing HP 3PAR Remote Copy with VMware vcenter Site Recovery Manager Table of contents Executive summary 2 Evolution of business continuity for VMware environments 3 Overview

More information

Bosch Video Management System High Availability with Hyper-V

Bosch Video Management System High Availability with Hyper-V Bosch Video Management System High Availability with Hyper-V en Technical Service Note Bosch Video Management System Table of contents en 3 Table of contents 1 Introduction 4 1.1 General Requirements

More information

Getting Started with ESXi Embedded

Getting Started with ESXi Embedded ESXi 4.1 Embedded vcenter Server 4.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent

More information

W H I T E P A P E R. Disaster Recovery Virtualization Protecting Production Systems Using VMware Virtual Infrastructure and Double-Take

W H I T E P A P E R. Disaster Recovery Virtualization Protecting Production Systems Using VMware Virtual Infrastructure and Double-Take W H I T E P A P E R Protecting Production Systems Using VMware Virtual Infrastructure and Double-Take Contents Introduction...1 What is VMware Infrastructure?...1 What is Double-Take?...1 Data Protection

More information

VMware vsphere 4.1 with ESXi and vcenter

VMware vsphere 4.1 with ESXi and vcenter VMware vsphere 4.1 with ESXi and vcenter This powerful 5-day class is an intense introduction to virtualization using VMware s vsphere 4.1 including VMware ESX 4.1 and vcenter. Assuming no prior virtualization

More information

IBM System Storage DS5020 Express

IBM System Storage DS5020 Express IBM DS5020 Express Manage growth, complexity, and risk with scalable, high-performance storage Highlights Mixed host interfaces support (Fibre Channel/iSCSI) enables SAN tiering Balanced performance well-suited

More information

EMC Replication Manager for Virtualized Environments

EMC Replication Manager for Virtualized Environments EMC Replication Manager for Virtualized Environments A Detailed Review Abstract Today s IT organization is constantly looking for ways to increase the efficiency of valuable computing resources. Increased

More information

Veritas InfoScale Availability

Veritas InfoScale Availability Veritas InfoScale Availability Delivers high availability and disaster recovery for your critical applications Overview protects your most important applications from planned and unplanned downtime. InfoScale

More information

DS8000 Data Migration using Copy Services in Microsoft Windows Cluster Environment

DS8000 Data Migration using Copy Services in Microsoft Windows Cluster Environment DS8000 Data Migration using Copy Services in Microsoft Windows Cluster Environment By Leena Kushwaha Nagaraja Hosad System and Technology Group Lab Services India Software Lab, IBM July 2013 Table of contents

More information

IBM XIV Gen3 Storage System Storage built for VMware vsphere infrastructures

IBM XIV Gen3 Storage System Storage built for VMware vsphere infrastructures Storage built for VMware vsphere infrastructures Peter Kisich IBM Systems and Technology Group ISV Enablement October 2011 Copyright IBM Corporation, 2011 Table of contents Abstract...1 Introduction...1

More information

Efficient Storage Strategies for Virtualized Data Centers

Efficient Storage Strategies for Virtualized Data Centers Efficient Storage Strategies for Virtualized Data Centers Contents Abstract. 1 Data Center Virtualization Status Report. 2 Dell EqualLogic Virtualized iscsi SAN Solutions. 2 Seamless, non-disruptive scalability.

More information

Virtual SAN Design and Deployment Guide

Virtual SAN Design and Deployment Guide Virtual SAN Design and Deployment Guide TECHNICAL MARKETING DOCUMENTATION VERSION 1.3 - November 2014 Copyright 2014 DataCore Software All Rights Reserved Table of Contents INTRODUCTION... 3 1.1 DataCore

More information

How To Use Vcenter Site Recovery Manager 5 With Netapp Fas/Vfs Storage System On A Vcenter Vcenter 5 Vcenter 4.5 Vcenter 3.5.5 (Vmware Vcenter) Vcenter 2.

How To Use Vcenter Site Recovery Manager 5 With Netapp Fas/Vfs Storage System On A Vcenter Vcenter 5 Vcenter 4.5 Vcenter 3.5.5 (Vmware Vcenter) Vcenter 2. Technical Report Deploying VMware vcenter Site Recovery Manager 5 with NetApp FAS/V-Series Storage Systems Larry Touchette and Julian Cates, NetApp June 2012 TR-4064 NetApp Best Practices for SRM5 This

More information

SQL Server Storage Best Practice Discussion Dell EqualLogic

SQL Server Storage Best Practice Discussion Dell EqualLogic SQL Server Storage Best Practice Discussion Dell EqualLogic What s keeping you up at night? Managing the demands of a SQL environment Risk Cost Data loss Application unavailability Data growth SQL Server

More information

13.1 Backup virtual machines running on VMware ESXi / ESX Server

13.1 Backup virtual machines running on VMware ESXi / ESX Server 13 Backup / Restore VMware Virtual Machines Tomahawk Pro This chapter describes how to backup and restore virtual machines running on VMware ESX, ESXi Server or VMware Server 2.0. 13.1 Backup virtual machines

More information

vcenter Operations Manager for Horizon Supplement

vcenter Operations Manager for Horizon Supplement vcenter Operations Manager for Horizon Supplement vcenter Operations Manager for Horizon 1.6 This document supports the version of each product listed and supports all subsequent versions until the document

More information

TGL VMware Presentation. Guangzhou Macau Hong Kong Shanghai Beijing

TGL VMware Presentation. Guangzhou Macau Hong Kong Shanghai Beijing TGL VMware Presentation Guangzhou Macau Hong Kong Shanghai Beijing The Path To IT As A Service Existing Apps Future Apps Private Cloud Lots of Hardware and Plumbing Today IT TODAY Internal Cloud Federation

More information

Table of Contents. vsphere 4 Suite 24. Chapter Format and Conventions 10. Why You Need Virtualization 15 Types. Why vsphere. Onward, Through the Fog!

Table of Contents. vsphere 4 Suite 24. Chapter Format and Conventions 10. Why You Need Virtualization 15 Types. Why vsphere. Onward, Through the Fog! Table of Contents Introduction 1 About the VMware VCP Program 1 About the VCP Exam 2 Exam Topics 3 The Ideal VCP Candidate 7 How to Prepare for the Exam 9 How to Use This Book and CD 10 Chapter Format

More information

Zerto Virtual Manager Administration Guide

Zerto Virtual Manager Administration Guide Zerto Virtual Manager Administration Guide AWS Environment ZVR-ADVA-4.0U2-01-23-07-15 Copyright 2015, Zerto Ltd. All rights reserved. Information in this document is subject to change without notice and

More information

Index C, D. Background Intelligent Transfer Service (BITS), 174, 191

Index C, D. Background Intelligent Transfer Service (BITS), 174, 191 Index A Active Directory Restore Mode (DSRM), 12 Application profile, 293 Availability sets configure possible and preferred owners, 282 283 creation, 279 281 guest cluster, 279 physical cluster, 279 virtual

More information

Symantec Cluster Server powered by Veritas

Symantec Cluster Server powered by Veritas Delivers high availability and disaster recovery for your critical applications Data Sheet: High Availability Overview protects your most important applications from planned and unplanned downtime. Cluster

More information

EMC Business Continuity for VMware View Enabled by EMC SRDF/S and VMware vcenter Site Recovery Manager

EMC Business Continuity for VMware View Enabled by EMC SRDF/S and VMware vcenter Site Recovery Manager EMC Business Continuity for VMware View Enabled by EMC SRDF/S and VMware vcenter Site Recovery Manager A Detailed Review Abstract This white paper demonstrates that business continuity can be enhanced

More information

VMware vsphere: Fast Track [V5.0]

VMware vsphere: Fast Track [V5.0] VMware vsphere: Fast Track [V5.0] Experience the ultimate in vsphere 5 skills-building and VCP exam-preparation training. In this intensive, extended-hours course, you will focus on installing, configuring,

More information

AUTOMATED DISASTER RECOVERY SOLUTION USING AZURE SITE RECOVERY FOR FILE SHARES HOSTED ON STORSIMPLE

AUTOMATED DISASTER RECOVERY SOLUTION USING AZURE SITE RECOVERY FOR FILE SHARES HOSTED ON STORSIMPLE AUTOMATED DISASTER RECOVERY SOLUTION USING AZURE SITE RECOVERY FOR FILE SHARES HOSTED ON STORSIMPLE Copyright This document is provided "as-is." Information and views expressed in this document, including

More information

BEST PRACTICES GUIDE: VMware on Nimble Storage

BEST PRACTICES GUIDE: VMware on Nimble Storage BEST PRACTICES GUIDE: VMware on Nimble Storage Summary Nimble Storage iscsi arrays provide a complete application-aware data storage solution that includes primary storage, intelligent caching, instant

More information

How To Backup A Virtual Machine With Thinware Vbackup

How To Backup A Virtual Machine With Thinware Vbackup vbackup Administrator s Guide Thinware vbackup 4.0.1 Thinware vbackup Administrator s Guide Thinware vbackup Administrator s Guide Revision: 4.0.1-1 The latest product updates and most up-to-date documentation

More information

Symantec and VMware: Virtualizing Business Critical Applications with Confidence WHITE PAPER

Symantec and VMware: Virtualizing Business Critical Applications with Confidence WHITE PAPER Symantec and VMware: Virtualizing Business Critical Applications with Confidence WHITE PAPER Challenges of Using Traditional High-Availability Solutions Business-critical applications and the systems they

More information

VMWARE VSPHERE 5.0 WITH ESXI AND VCENTER

VMWARE VSPHERE 5.0 WITH ESXI AND VCENTER VMWARE VSPHERE 5.0 WITH ESXI AND VCENTER CORPORATE COLLEGE SEMINAR SERIES Date: April 15-19 Presented by: Lone Star Corporate College Format: Location: Classroom instruction 8 a.m.-5 p.m. (five-day session)

More information

NetApp OnCommand Plug-in for VMware Backup and Recovery Administration Guide. For Use with Host Package 1.0

NetApp OnCommand Plug-in for VMware Backup and Recovery Administration Guide. For Use with Host Package 1.0 NetApp OnCommand Plug-in for VMware Backup and Recovery Administration Guide For Use with Host Package 1.0 NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 USA Telephone: +1 (408) 822-6000 Fax: +1

More information

DR-to-the- Cloud Best Practices

DR-to-the- Cloud Best Practices DR-to-the- Cloud Best Practices HOW TO EFFECTIVELY CONFIGURE YOUR OWN SELF-MANAGED RECOVERY PLANS AND THE REPLICATION OF CRITICAL VMWARE VIRTUAL MACHINES FROM ON-PREMISES TO A CLOUD SERVICE PROVIDER CONTENTS

More information

Solution Brief Availability and Recovery Options: Microsoft Exchange Solutions on VMware

Solution Brief Availability and Recovery Options: Microsoft Exchange Solutions on VMware Introduction By leveraging the inherent benefits of a virtualization based platform, a Microsoft Exchange Server 2007 deployment on VMware Infrastructure 3 offers a variety of availability and recovery

More information

HP Matrix Operating Environment 7.2 Recovery Management User Guide

HP Matrix Operating Environment 7.2 Recovery Management User Guide HP Matrix Operating Environment 7.2 Recovery Management User Guide Abstract The HP Matrix Operating Environment 7.2 Recovery Management User Guide contains information on installation, configuration, testing,

More information

SanDisk ION Accelerator High Availability

SanDisk ION Accelerator High Availability WHITE PAPER SanDisk ION Accelerator High Availability 951 SanDisk Drive, Milpitas, CA 95035 www.sandisk.com Table of Contents Introduction 3 Basics of SanDisk ION Accelerator High Availability 3 ALUA Multipathing

More information

IBM Storwize V7000: For your VMware virtual infrastructure

IBM Storwize V7000: For your VMware virtual infrastructure IBM Storwize V7000: For your VMware virtual infrastructure Innovative midrange disk system leverages integrated storage technologies Highlights Complement server virtualization, extending cost savings

More information

Enterprise Manager. Version 6.2. Administrator s Guide

Enterprise Manager. Version 6.2. Administrator s Guide Enterprise Manager Version 6.2 Administrator s Guide Enterprise Manager 6.2 Administrator s Guide Document Number 680-017-017 Revision Date Description A August 2012 Initial release to support version

More information

VirtualclientTechnology 2011 July

VirtualclientTechnology 2011 July WHAT S NEW IN VSPHERE VirtualclientTechnology 2011 July Agenda vsphere Platform Recap vsphere 5 Overview Infrastructure Services Compute, Storage, Network Applications Services Availability, Security,

More information

Virtualizing your Datacenter

Virtualizing your Datacenter Virtualizing your Datacenter with Windows Server 2012 R2 & System Center 2012 R2 Part 2 Hands-On Lab Step-by-Step Guide For the VMs the following credentials: Username: Contoso\Administrator Password:

More information

VMware vsphere Data Protection Evaluation Guide REVISED APRIL 2015

VMware vsphere Data Protection Evaluation Guide REVISED APRIL 2015 VMware vsphere Data Protection REVISED APRIL 2015 Table of Contents Introduction.... 3 Features and Benefits of vsphere Data Protection... 3 Requirements.... 4 Evaluation Workflow... 5 Overview.... 5 Evaluation

More information

IBM Storwize V5000. Designed to drive innovation and greater flexibility with a hybrid storage solution. Highlights. IBM Systems Data Sheet

IBM Storwize V5000. Designed to drive innovation and greater flexibility with a hybrid storage solution. Highlights. IBM Systems Data Sheet IBM Storwize V5000 Designed to drive innovation and greater flexibility with a hybrid storage solution Highlights Customize your storage system with flexible software and hardware options Boost performance

More information

VMware Site Recovery Manager (SRM) Lessons Learned in the First 90 Days

VMware Site Recovery Manager (SRM) Lessons Learned in the First 90 Days VMware Site Recovery Manager (SRM) Lessons Learned in the First 90 Days Bob van der Werf / Jeremy van Doorn Sr. Systems Engineer BvanderWerf@vmware.com +31 (0)6 1389 9144 Agenda SRM in 10 minutes Installation

More information

Remote PC Guide Series - Volume 1

Remote PC Guide Series - Volume 1 Introduction and Planning for Remote PC Implementation with NETLAB+ Document Version: 2016-02-01 What is a remote PC and how does it work with NETLAB+? This educational guide will introduce the concepts

More information

VTrak S3000 Integrated Storage Solutions for Virtualized Infrastructures

VTrak S3000 Integrated Storage Solutions for Virtualized Infrastructures Solution Whitepaper VTrak S3000 Integrated Storage Solutions for Virtualized Infrastructures Executive Summary The paradigm shift from traditional IT environment to virtualized infrastructure is happening

More information

vsphere Replication for Disaster Recovery to Cloud

vsphere Replication for Disaster Recovery to Cloud vsphere Replication for Disaster Recovery to Cloud vsphere Replication 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

vcenter Chargeback User s Guide

vcenter Chargeback User s Guide vcenter Chargeback 1.6 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

Nimble Storage for VMware View VDI

Nimble Storage for VMware View VDI BEST PRACTICES GUIDE Nimble Storage for VMware View VDI N I M B L E B E S T P R A C T I C E S G U I D E : N I M B L E S T O R A G E F O R V M W A R E V I E W V D I 1 Overview Virtualization is an important

More information

Installing and Configuring vcenter Multi-Hypervisor Manager

Installing and Configuring vcenter Multi-Hypervisor Manager Installing and Configuring vcenter Multi-Hypervisor Manager vcenter Server 5.1 vcenter Multi-Hypervisor Manager 1.1 This document supports the version of each product listed and supports all subsequent

More information

VERITAS Storage Foundation 4.3 for Windows

VERITAS Storage Foundation 4.3 for Windows DATASHEET VERITAS Storage Foundation 4.3 for Windows Advanced Volume Management Technology for Windows In distributed client/server environments, users demand that databases, mission-critical applications

More information

VMware vcenter Operations Manager for Horizon Supplement

VMware vcenter Operations Manager for Horizon Supplement VMware vcenter Operations Manager for Horizon Supplement vcenter Operations Manager for Horizon 1.7 This document supports the version of each product listed and supports all subsequent versions until

More information

Table of Contents. Online backup Manager User s Guide

Table of Contents. Online backup Manager User s Guide Table of Contents Backup / Restore VMware Virtual Machines... Error! Bookmark not defined. Backup virtual machines running on VMware ESXi / ESX Server with VDDK / non VDDK... 2 Requirements and recommendations...

More information

vsphere Replication for Disaster Recovery to Cloud

vsphere Replication for Disaster Recovery to Cloud vsphere Replication for Disaster Recovery to Cloud vsphere Replication 5.8 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

Basic System Administration ESX Server 3.0.1 and Virtual Center 2.0.1

Basic System Administration ESX Server 3.0.1 and Virtual Center 2.0.1 Basic System Administration ESX Server 3.0.1 and Virtual Center 2.0.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a

More information

Virtual Storage Console 4.0 for VMware vsphere Installation and Administration Guide

Virtual Storage Console 4.0 for VMware vsphere Installation and Administration Guide Virtual Storage Console 4.0 for VMware vsphere Installation and Administration Guide NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 U.S.A. Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501 Support

More information

Installing and Configuring vcloud Connector

Installing and Configuring vcloud Connector Installing and Configuring vcloud Connector vcloud Connector 2.7.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new

More information

SAN System Design and Deployment Guide. Second Edition

SAN System Design and Deployment Guide. Second Edition SAN System Design and Deployment Guide Second Edition Latest Revision: August 2008 2008 VMware, Inc. All rights reserved. Protected by one or more U.S. Patent Nos. 6,397,242, 6,496,847, 6,704,925, 6,711,672,

More information

RSA Authentication Manager 8.1 Setup and Configuration Guide. Revision 2

RSA Authentication Manager 8.1 Setup and Configuration Guide. Revision 2 RSA Authentication Manager 8.1 Setup and Configuration Guide Revision 2 Contact Information Go to the RSA corporate website for regional Customer Support telephone and fax numbers: www.emc.com/domains/rsa/index.htm

More information

VMware vcenter Site Recovery Manager 5 Technical

VMware vcenter Site Recovery Manager 5 Technical VMware vcenter Site Recovery Manager 5 Technical Raj Jethnani, VCP 4/5, VCAP4-DCA / DCD Systems Engineer VMware, Inc. rjethnani@vmware.com @rajtech 2009 VMware Inc. All rights reserved Agenda Simplifying

More information

VMware vrealize Operations for Horizon Installation

VMware vrealize Operations for Horizon Installation VMware vrealize Operations for Horizon Installation vrealize Operations for Horizon 6.0 This document supports the version of each product listed and supports all subsequent versions until the document

More information

istorage Server: High Availability iscsi SAN for Windows Server 2012 Cluster

istorage Server: High Availability iscsi SAN for Windows Server 2012 Cluster istorage Server: High Availability iscsi SAN for Windows Server 2012 Cluster Tuesday, December 26, 2013 KernSafe Technologies, Inc www.kernsafe.com Copyright KernSafe Technologies 2006-2013.All right reserved.

More information

WhatsUp Gold v16.3 Installation and Configuration Guide

WhatsUp Gold v16.3 Installation and Configuration Guide WhatsUp Gold v16.3 Installation and Configuration Guide Contents Installing and Configuring WhatsUp Gold using WhatsUp Setup Installation Overview... 1 Overview... 1 Security considerations... 2 Standard

More information

ArCycle vmbackup. for VMware/Hyper-V. User Guide

ArCycle vmbackup. for VMware/Hyper-V. User Guide ArCycle vmbackup for VMware/Hyper-V User Guide 2 Copyright Copyright ArCycle Software, Ltd., 2011-2014. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system,

More information