Srm 10 Eval Guide[1]

8/8/2019 Srm 10 Eval Guide[1]

1/53


2/53


3/53


4/53


5/53

5 VMware, Inc.

Disaster Recovery (DR), Virtual Infrastructure (VI) and SRM abbreviations Used in this GuideThe following DR, VI and SRM abbreviations are used throughout this evaluator guide:

Abbreviation DescriptionBC/DR Business Continuity and Disaster RecoverySRM Site Recovery Manager

VC VirtualCenterVI Client Virtual Infrastructure Client used to access Virtual Center and SRMVM Virtual machines on a managed hostRP Virtual Infrastructure Resource PoolVMFS Virtual Machine File SystemSAN Storage area network type datastore shared between managed hosts

Disaster Recovery (DR) and SRM Terminology Used in this GuideThe following DR and SRM terminology is used throughout this evaluator guide:

DR and SRMTerminology

Description

array-basedreplication Replication of virtual machines that is managed and executed bythe storage subsystem itself rather than from inside the virtualmachines, the vmkernel or the Service Console.

logical unit number(LUN)

Refers to a single SCSI storage device on the SAN that can bemapped to one or more ESX Servers.

Failover Event that occurs when the recovery site takes over operation inplace of the protected site after the declaration of a disaster.

Failback Reversal of failover, returning IT operations to the primary site.datastore Storage for the managed hostHost VirtualCenter managed hostsSRM Server Manages and monitors the SRM recovery plansprotected VM A VM that is protected by SRM because it is located on a replicated datastoreun-protected VM A VM that is not protected by SRM because it is located on a non replicated

datastoreprotected site The site that contains the protected VMsrecovery site The site that contains the replicated protected VMs from the protected sitedatastore group Replicated datastores containing complete sets of protected VMprotection group A group of VMs that will be failed over together to the recovery site during test

or recoveryStorage ReplicationAdapter (SRA)

Enables SRM to interact with a storage array

shadow VM An artifact in the recovery site VC inventory that represents a protected VMfrom the protected site VC

inventory mappings Associations between protected resource pools VM folders, networks andtheir destination counterparts at the recovery site

recovery plan Contains the complete set of steps needed to recover (or test recovery of) the

protected VMs in one or more protection groups

Document FeedbackVMware welcomes your suggestions for improving our documentation. If you have comments, sendyour feedback to:

[email protected] .
mailto:[email protected]:[email protected]:[email protected]


6/53

Site Recovery Manager Evaluator Guide

6 VMware, Inc .

Technical Support and Education ResourcesThe following sections describe the technical support resources available to you.

Online Support for the Site Recovery ManagerTechnical support is available through the Support Request (SR) system. Go tohttp://www.vmware.com/support/ and click on Create Support Request.

Please note that you will need a valid VMware account in order to open a SR. If you do not alreadyhave an account, you will need to register for one here .

Support OfferingsFind out how VMware support offerings can help meet your business needs, go to

http://www.vmware.com/support/services .

VMware Education ServicesVMware courses offer extensive hands on labs, case study examples, and course materials designedto be used as on the job reference tools. For more information about VMware Education Services,go to

http://mylearn1.vmware.com/mgrreg/index.cfm .
http://www.vmware.com/support/http://www.vmware.com/support/http://www.vmware.com/vmwarestore/newstore/purchase_register.jsp?status=newhttp://www.vmware.com/vmwarestore/newstore/purchase_register.jsp?status=newhttp://www.vmware.com/vmwarestore/newstore/purchase_register.jsp?status=newhttp://www.vmware.com/support/serviceshttp://www.vmware.com/support/serviceshttp://mylearn1.vmware.com/mgrreg/index.cfmhttp://mylearn1.vmware.com/mgrreg/index.cfmhttp://mylearn1.vmware.com/mgrreg/index.cfmhttp://www.vmware.com/support/serviceshttp://www.vmware.com/vmwarestore/newstore/purchase_register.jsp?status=newhttp://www.vmware.com/support/


7/53

7 VMware, Inc.

SRM Quick Start Checklist

Before starting to work through the SRM installation and configuration workflows that are outlined in thisSRM Evaluator guide, we recommend you refer to the SRM Storage Release notes that are specific forthe SRM supported storage platform that you will be using in your protected and recovery site and workthrough the checklist to ensure your storage platforms are ready for integration with SRM. Once you haveworked through the appropriate storage checklist you should then proceed to work through the SRM Pre-Install checklist below which when completed will ensure you are ready to proceed with the setup SRM.

SRM Pre-Install Checklist

Site Description Yes / NoUsing your VMware Store Account access the URL below to download theSRM software, Storage Replication Adapter, and other relevant product andprogram information:http://www.vmware.com/download/srm/eval.html

Protected SQL Enterprise 2005 or Oracle Database server setup and ready for use.Protected A database instance has been created for Virtual CenterProtected A database user created with db owner and create table privileges Protected A system DSN created for the VC databaseProtected Virtual Center 2.5 server installed and ready for use.Protected The ability to access the Virtual Center 2.5 server via the VI ClientProtected At least one ESX Server 3.0.2 or ESX Server 3.5 installed and integrated

into Virtual Center, with access to a LUN on a SAN that has beenconfigured as a VMFS datastore and setup for data replication to acorresponding SAN in the recovery site.

Protected A database instance has been created for Site Recovery Manager (SRM)Protected A database user created with db owner and create table privileges Protected A system DSN created for the SRM databaseProtected Identify a system (physical or virtual) to install the SRM software and the

Storage Replication Adapter (SRA) for your respective arrayRecovery SQL Enterprise 2005 or Oracle Database server setup and ready for use.Recovery A database instance has been created for Virtual CenterRecovery A database user created with db owner and create table privileges Recovery A system DSN created for the VC databaseRecovery Virtual Center 2.5 server installed and ready for use.Recovery The ability to access the Virtual Center 2.5 server via the VI ClientRecovery At least on ESX Server 3.0.2 or ESX Server 3.5 installed and integrated into

Virtual Center, with access to a LUN on a SAN that has been configured asa VMFS datastore and setup for data replication to a corresponding SAN inthe recovery site.

Recovery A database instance has been created for Site Recovery Manager (SRM)Recovery A database user created with db owner and create table privileges Recovery A system DSN created for the SRM databaseRecovery Identify a system (physical or virtual) to install the SRM software and the

Storage Replication Adapter (SRA) for your respective array
http://www.vmware.com/download/srm/eval.htmlhttp://www.vmware.com/download/srm/eval.htmlhttp://www.vmware.com/download/srm/eval.html


8/53


8 VMware, Inc .

SRM Evaluation Checklist

To aid you with your SRM evaluation please refer to the SRM Evaluation Checklist below whichprovides a high level summary of the various SRM workflows and configuration tasks that should becompleted during your SRM Evaluation.

SRM Evaluation Checklist

Site Description Yes / NoProtected Connection : This involves pairing the VirtualCenter servers at the

protected and recovery sites.CH 3 - Pg 15

Protected Array Managers: SRM leverages array based replication between aprotected site and a recovery site. When working through the Array Manager configuration wizard SRM will identify which arrays are availableincluding the datastores groups that have been setup for replicationbetween the protected and recovery site.CH 3 - Pg16

Protected Inventory Preferences : Using the Inventory Mapper wizard, the protected

VMs now need to be mapped to the Networks, Compute Resources andVirtual Machine Folders that are available at the recovery site.CH 3 - Pg 19

Protected Protection Groups : A protection group is a group of VMs that will be failedover together to the recovery site.Work through the Protection Groupsconfiguration wizard to complete the Protection Group setup.CH 3 - Pg 20

Recovery Recovery Plan . A recovery plan describes the steps necessary to recoverthe protected VMs in one or more protection groups. These steps can bepredefined (e.g. Power On VM) or user-defined callouts. When a recoveryplan is defined, the basic steps necessary to recover the protection groupsit contains are automatically generated.CH 3 - 25

Protected IP Address Network Customization to allow protected VMs to start withthe correct IP addresses and network configuration in the recovery site.CH - 3 Pg 25 Note : This task may not be required for protected VMs that use DHCP toobtain an IP address or in environments that have a Stretched VLANnetwork topology.

Recovery Test your Recovery Plan via the SRM TEST Recovery Plan option.CH 4

Recovery Run your Recovery Plan via the SRM RUN Recovery Plan option.CH 5

Note : SRM does not support an automated push one button failback viathe SRM User Interface. A failback to the original protected site is possibleand is documented in CH 6 should you want to resync the data in therecovery site back to the protected site.

RecoveryProtected

Failback (Optional) . Refer to CH 6 for the failback procedure which willinvolve you working closely with your storage team to complete failback.

ProtectedRecovery

SRM Alarms and Site Monitoring . Enable the appropriate notificationsand alarms to stay in compliance with your documented monitoring policies.CH 7

ProtectedRecovery

SRM Roles and Privileges . Assign the appropriate SRM Roles to stay incompliance with your documented security policies.CH 8


9/53

9 VMware, Inc.

Chapter 1: Overview of VMware Site Recovery Manager (SRM)

VMware Site Recovery Manager(SRM) provides business continuity and disaster recovery protectionfor virtual environments. Protection can extend from individual replicated datastores to an entire virtualsite. VMwares virtualization of the data center offers advantages that can be applied to businesscontinuity and disaster recovery:

The entire state of a virtual machine (memory, disk images, I/O and device state) isencapsulated. Encapsulation enables the state of a virtual machine to be saved to a file. Savingthe state of a virtual machine to a file allows the transfer of an entire virtual machine to anotherhost.

Hardware independence eliminates the need for a complete replication of hardware at therecovery site. Hardware running ESX at one site can provide business continuity and disasterrecovery protection for hardware running ESX at another site. This eliminates the cost ofpurchasing and maintaining a system that sits idle until disaster strikes.

Hardware independence allows an image of the system at the protected site to boot from diskat the recovery site in minutes or hours instead of days.

SRM leverages array based replication between a protected site and a recovery site. The workflow thatis built into SRM automatically discovers which datastores are setup for replication between the

protected and recovery sites. SRM can be configured to support bi-directional protection between twosites.

SRM provides protection for the operating systems and applications encapsulated by the virtualmachines running on ESX. A SRM server must be installed at the protected site and at the recoverysite. The protected and recovery sites must each be managed by their own VirtualCenter Server. TheSRM server uses the extensibility of the VirtualCenter Server to provide:

Access control

Authorization

Custom events

Event-triggered alarms

Site Recovery Manager Prerequisites

SRM has the following prerequisites:

A VirtualCenter server installed at the protected site.

A VirtualCenter server installed at the recovery site.

Pre-configured array-based replication between the protected site and the recovery site.

Network configuration that allows TCP connectivity between SRM servers and VC servers

An Oracle or SQL Server database that uses ODBC for connectivity in the protected site and inthe recovery site.

A SRM license installed on the VC license server at the protected site and the recovery site.


10/53


10 VMware, Inc .

Site Recovery Manager Configuration and Protection

Setup and configuration are accomplished by following workflows for the protected and recovery sites.SRM is installed as a plugin into a Virtual Infrastructure Client (VI Client). SRM uses the VI Client as theUser Interface (UI). The SRM UI is accessed by clicking on the Site Recovery icon in the VI clienttoolbar and is used for the setup of the SRM workflows, recovey plan testing as well as servicesfailover from the protected site to the recovery site.

It is important to complete the worklows in the order they are presented in this guide.

The recovery site configuration workflow involves the following activities:

The user installs the SRM server.

The user installs the SRM plugin into the VI Client

The protection site configuration workflow involves the following activities:

The user installs the SRM server.

If a different VI Client is used to access the protected and recovery sites, the user installs theSRM plugin into the VI Client, otherwise this activity can be skipped.

Security certificates are established between the SRM servers and the VC servers.The user pairs the SRM servers at the protected and recovery sites.

SRM identifies available arrays and replicated datastores and determines the datastore groups.

The protection site protection workflow involves the following activities:

Using the Inventory Mapper, the user maps the networks, compute resources and virtualmachine folders in the protected site to their counterparts in the recovery site.

The user creates protection groups from the datastores discovered by SRM.

For each protected VM, the user can override default values.

The recovery site protection workflow involves the following activities:

The user creates the recovery plan.

SRM creates the recovery plan steps.

Optionally the user has the ability to customize the recovery plan

Failover and Testing

SRM automates many of the tasks required at failover. With the push of one button, SRM:

will power down the protected VMs if there is connectivity between sites and they are online.

suspend data replication and Read/Write enable the replica datastores.

rescan the ESX servers at the recovery site.

registers the replicated protected VMs.shuts down non-essential VMs at the recovery site if required to free up resources for theprotected VMs being failed over.

completes power-up of replicated protected VMs in accordance with the recovery plan.


11/53

11 VMware, Inc.

SRM does not require production system downtime to run tests. This means you can test often toensure that you are protected in case of a disaster. For testing, SRM:

creates a test environment that includes network and storage infrastructure that is isolated fromthe production environment.

rescans the ESX servers.

registers the replicated VMs.

completes power-up of protected VMs in the order specified during creation of the disasterrecovery plan.

provides a report of test results.

resets everything in preparation for a disaster or next scheduled SRM Test.


12/53


12 VMware, Inc .

Chapter 2: Planning for BC/DR when using VMware SRM

This chapter will provide an overview of the site planning and preparation that should be completed toensure the SRM protected and recovery sites are prepared for the SRM Evaluation.

Figure 2.1

Figure 2.1 represents a SRM protected site which contains local services and protected services.The local services are infrastructure type services (Active Directory, Print services, Virus Managementservices and Security Camera services) and are generally bound to the data center. The protectedservices are application type services, and these are the services that need to be made available to thebusiness at time of test or disaster. This will be accomplished using SRM. Using the SRM protected sitedepicted in Figure 2.1 we will now review the planning and preparations that should be completed toensure both the SRM protected and recovery sites are ready for a successful SRM deployment.

Site planning and preparation at the protected site involves the following:

Identify which VMs will be designated as protected VMs.o app_vm1 through app_vm12

Identify which VMs will be designated as un-protected VMso ad_server , print_server , security_camera_server and virus_mgt_server

Determine the number of datastore groups that will be required to hold the protected VMs.o Based on the 12 VMs we have designated to be protected VMs and for the purposes of

the SRM configuration that will be depicted in this evaluator guide we will require 2datastore groups which will contain six complete VMs per datastore group.


13/53

13 VMware, Inc.

If existing datastores will be used for the protected VMs, identify which datastores need to beconfigured as datastore groups otherwise provision the required number of new datastores to hostthe protected VMs. Working with your SAN team ensure all the datastores that will host protectedVMs are configured as datastore groups i.e. setup for replication between the protected andrecovery site.

o Referring to Figure 2.2, we will require 2 datastore groups, shared-san-1 and shared-san-2 , which were previously configured to allow for the replication of data to therecovery site. Note : The setup and configuration of SAN replication will differ fromarray vendor to array vendor, if you are unsure of how to complete the necessaryreplication setup and configuration, consult with your array vendor who should be in aposition to provide you with all the necessary information.

Move all the designated protected VMs onto the SRM datastore groups. Storage VMotion canbe used to complete the relocation of the protected VMs with zero service downtime. If possibleensure there are only protected VMs on the datastores that are being replicated from theprotected site to the recovery site. Referring to Figure 2.2 which is a VMware topology mapview, it is clear to see that:

o app_vm1 through app_vm6 are hosted from datastore group shared-san-1 o app_vm7 through app_vm12 are hosted from datastore group shared-san-2o The non replicated infrastructure VMs are hosted from datastore vim22-storage1

Figure 2.2


14/53


14 VMware, Inc .

Figure 2.2 represents a different view of the same SRM protected site depicted in Figure 2.1 whichcontains local services being hosted from datastore vim22-storage1 and the protected serviceshosted from datastore groups shared-san-1 and shared-san-2 respectively. The protected servicesare under the control of SRM and will be made available at time of test or disaster via SRM at therecovery site.

Figure 2.3

Figure 2.3 represents a SRM recovery site which contains local services and will also service the failedover protected services which are all the protected VMs hosted from datastore groups shared-san-1and shared-san-2 in the SRM protected site depicted in Figure 2.2 . Once again the local services areinfrastructure type services (Active Directory, Print services, Virus Management services and SecurityCamera services) that are bound to the recovery site data center.


15/53

15 VMware, Inc.

Chapter 3: SRM Workflow setup at the Protected and Recovery sites

This chapter will provide an overview of the SRM workflows that have to be completed to ensure SRMis providing BC/DR services for the designated virtual machines at time of test or during an actual eventthat necessitated the declaration of a disaster.

Figure 3.1

The SRM workflows that will be outlined below will be associated with the virtual data centers vim22dcand vim23dc depicted in Figures 2.1, 2.2 and 2.3.

Figure 3.1 shows part of the VI Client window, the Site Recovery icon has been highlighted as well asthe Setup pane. The protected site SRM workflows will be completed via the VI Client by selectingConfigure and working through the configuration wizard for each of the steps identified below:

Connection : This involves pairing the VirtualCenter servers at the protected and recovery

sites.The VC server in the local data center vim22dc is dr-vc-vim22.eng.vmware.com . The VCserver in the remote data center vim23dc is dr-vc-vim23.eng.vmware.com .


16/53


16 VMware, Inc .

Figure 3.2

Once the remote VC servers information has been entered you will be presented with thefollowing Connect to Remote Site window.

Figure 3.3

Once reciprocity has been established, click Close to complete the setup. You are now readyto move onto the Array Manager configuration step.

Note: If you are using certificates that are not properly signed, the last two check marks in

Figure 3.3 may appear as yellow warning triangles when Reciprocity is established . Theuse of certificates that are not properly signed will not prevent you from moving onto the nextSRM configuration step which involves configuring the Array Managers .

Array Managers: SRM leverages array based replication between a protected site and arecovery site. When working through the Array Manager configuration wizard SRM will identifywhich arrays are available including the datastores groups that have been setup for replicationbetween the protected and recovery site.


17/53

17 VMware, Inc.

Virtual machines reside on VMFS datastores which are created on LUNs that reside on the storagearrays. SRM uses the term "datastore group" as a way of identifying a replicated datastore(s) thatprotect virtual machines. If SRM detects a virtual machine spanning more than one datastore (i.e VMhas two virtual disks one on each datastore) then to allow that whole VM to be failed over the SRMdatastore group *must* contain both datastores and SRM will enforce this, we will cover this furtherbelow. In SRM a datastore group is the basic unit of replication.

VMFSDatastore B

VMFSDatastore A

VMFSDatastore C

VMFSDatastore DE

ReplicatedLUN C

ReplicatedLUN A

ReplicatedLUN D

ReplicatedLUN E

VM4

. vmx

VM4

Disk

VM5

.vmx

VM5

Disk

VM1

. vmx

VM1

Disk

VM3

.vmx

VM3

Disk

VM2

Disk

VM2

.vmx

Datastore Group 1 Datastore Group 2

ReplicatedLUN B

Non

VM 1 isProtected by SRM

VM 2 is notProtected by SRM

VM 3, VM 4 and VM 5are Protected by SRM

SRM PROTECTED SITE - STORAGE ARRAY

Figure 3.4

In Figure 3.4, VM1 is contained in Replicated LUN A (Datastore Group 1) so VM1 is a protectedVM. VM2 is contained on a non replicated LUN and therefore VM2 is not protected by SRM.Datastore Group 2 consists of Datastore C and Datastore DE which contains protected VMs 3,4, and 5. It is worth noting that even though VM4 spans two datastores, it is completelycontained within Datastore Group 2 and as a result is fully protected by SRM. In SRM an entire

VM needs to be located within a datastore group which has a one to one mapping to aprotection group. Datastore groups are automatically discovered by SRM, a datastore group isdefined by the configuration of the virtual machines selected for protection by SRM. SRMprotection groups will be covered at a later stage in this guide.

It is worth noting at this time that VMware is actively working with our storage partners who areresponsible for the development of their own Storage Replication Adapaters (SRAs), which willenable their storage arrays to integrate with SRM. For this reason VMware anticipates the list ofstorage Manager Types to become more extensive over time as the storage partners completework on their respective SRAs.


18/53


18 VMware, Inc .

If you do not see a Manager Type for a storage array which you have in your environment thatyou wish to integrate with SRM, VMware strongly urges you to follow-up directly with thestorage vendor in question to enquire about the availability of their SRM storage replicationadapter as VMware is not in a position to comment on the availability of products currentlyunder development by our partners, in this case our storage partners.

Working through the Array Manager configuration wizard will take you to the Add Array

Manager window depicted in Figure 3.5, select the correct Manager Type for the SAN in yourenvironment.

Figure 3.5

Once you have selected the correct Manager Type from the drop down box, complete the entryof all the appropriate information within the Array Manager Information section and clickConnect to start the SRM Discover Storage Array process which will run for several minutes.The Array Manager configuration wizard will walk you through the configuration for the

Protection Side Array Managers and Recovery Side Array Managers .Figure 3.6 is a consolidated view of the three Configure Array Managers windows to showsan example of the information that will be presented at the end of the SRM Discover StorageArray process for the protected and recovery sites. The information shown below is for theVirtual Data Centers vim22dc and vim23dc . At this stage you are now ready to move onto theInventory Preferences configuration step.


19/53

19 VMware, Inc.

Figure 3.6

Inventory Preferences : Using the Inventory Mapper wizard, the protected VMs now need tobe mapped to the Networks , Compute Resources and Virtual Machine Folders that areavailable at the recovery site. The mappings are completed via the Inventory Preferences pane below by clicking on the respective Primary Site Resources catergory and clicking on

Edit and working through the inventory mapper wizard for the respective resource catergory.


20/53


20 VMware, Inc .

Figure 3.7

In Figure 3.7 the Inventory Preferences pane shows the configured Inventory Preferences forthe protected VMs in the virtual data center vim22dc and how they are mapped to the appropriateresources in the virtual data center vim23dc which is the designated recovery site.

Protection Groups : A protection group is a group of VMs that will be failed over together to therecovery site. A protection group is associated with a single datastore group. A datastore groupcould contain a single datastore or multiple datasotres as illustrated in Figure 3.4.

Working through the Protection Groups configuration wizard you will get to the window shownin Figure 3.8. During the creation of the Protection Groups , SRM requires a location to storesome temporary VirtualCenter inventory files for the protected VMs. SRM will present theavailable datastores at the recovery site that could be selected for the storing of thesetemporary files. It is preferable and suggested that you select a non replicated datastore forthese temporary files at the recovery site.

Figure 3.8


21/53

21 VMware, Inc.

Select the datastore that will store the temporary virtual machine files and click Next which willtake you to the next Create Protection Group window shown in Figure 3.9. You will now bepresented with the list of all the protected VMs that will be assigned to the Protection Group currently being created.

Figure 3.9

Figure 3.9 shows the six protected VMs assigned to the first protection group calledProtection Group 1 which was created in the virtual data center vim22dc .


22/53


22 VMware, Inc .

Figure 3.10

Figure 3.10 shows the six protected VMs assigned to the second protection group calledProtection Group 2 which was created in the virtual data center vim22dc .

The creation of the protection groups completes the SRM workflow activities for the protected site. Torecap we have worked through the following SRM workflow activities so far:

Connection : This involved the pairing the VirtualCenter servers at the protected and recoverysites.

Array Managers : SRM leverages array based replication between a protected site and arecovery site. The integration of array based replication with SRM is achieved by selecting thecorrect Manager Type for the SAN in your protected and recovery sites.

Inventory Preferences : Using the Inventory Mapper , the protected VMs are mapped to theNetworks , Compute Resources and Virtual Machine Folders that are available at therecovery site.

Protection Groups : A protection group is a group of VMs that will be failed over together to therecovery site. The creation of a protection group results in VC inventory updates in the recoverysite.


23/53

23 VMware, Inc.

Figure 3.11 shows the view of the recovery site virtual data center vim23dc , it is worth noting that oncethe protection groups were created, the virtual infrastructure inventory in the recovery site wasautomatically updated with new inventory objects. The first new inventory object is the nested resourcepool called recovery under the top level RP called shared . The remaining inventory objects that havebeen added are the protected VMs from the SRM protected site.

Figure 3.11

The remaining workflow activity which is the creation the SRM Recovery Plan and any subsequentcustomizations to the recovery plan are completed via the VI Client connecting to the VC server in thedesignated recovery site

The recovery site protection workflow involves the following activities:

Building a Recovery Plan . A recovery plan describes the steps necessary to recover theprotected VMs in one or more protection groups. These steps can be predefined (e.g. Power

On VM) or user-defined callouts. When a recovery plan is defined, the basic steps necessary torecover the protection groups it contains are automatically generated. These steps can then becustomized by you by re-ordering existing steps or adding new steps and callouts. When aRecovery Plan is created for one or more protection groups, the plan is automatically populatedwith the basic steps needed to failover the protected VMs to the recovery site.


24/53


24 VMware, Inc .

Figure 3.12 shows the recovery steps from a SRM recovery plan called Recovery Plan 2 Protection Group 2 required to complete a partial site failover for the local data centervim22dc which is protected by SRM. The protected VMs that will be failed over are app_vm7 through to app_vm12 from Protection Group 2 which is associated to the datastore groupshared-san-2 .

Figure 3.12


25/53

25 VMware, Inc.

In Figure 3.13 the VI Client lists three Recovery Plans that were created by working through theRecovery Plan wizard. To create a new Recovery Plan , click on the Add button on the toolbaror Add Recovery Plan under the Commands section and work through the Recovery Plan wizard.

Figure 3.13

The following section will illustrate one of the supported ways to customize settings associated with aprotected VM. By working through the steps that follow you will be able to customize the network

configuration settings for a protected VM which will allow the protected VM to start up at the recoverysite after an actual failover with an IP address that is correct for the network in the recovery site.

Referring to Figure 3.14, working from the VI Client that is connected to the recovery site complete thefollowing. From the Edit menu option, click on Customization Specifications and work through thewizard that follows.

Figure 3.14

A Customization Specification Manager window opens up, click on New , and complete theinformation being requested by the wizard. Ensure you select the correct Target Virtual Machine OS and provide a name for virtual machine customization profile in the Customization SpecificationInformation as shown in Figure 3.15.


26/53


26 VMware, Inc .

Figure 3.15

Click Next to continue to the window below which is depicted by Figure 3.16.

Figure 3.16


27/53

27 VMware, Inc.

At this point it worth noting that the only information that will be applied to the protected VM you wish tocustomize via SRM will be Network information. For the SRM 1.0 release you may need to provideinformation for all the virtual machine properties highlighted in Figure 3.16 by the two red boxes toallow you to move onto the next virtual machine property screen as the Next button will only becomeactive once you enter text into the property field currently being displayed to you.

Figure 3.17

When you get to the Network properties section as depicted in Figure 3.17, please be sure toclick on the Custom Settings radio button, and then click on the Next button to proceed to theNetwork Custom Settings window shown in Figure 3.18.

Figure 3.18


28/53


29/53

29 VMware, Inc.

Figure 3.21

Working through the Recovery Launch wizard, you will get to the Virtual Machine Customization Window that is shown in Figure 3.22. From the drop down box select the virtual machine customizationprofile you wish to assign the protected VM, in this case customization_appvm12 , and click Next toproceed onto the last two remaining customizations which are Before Power On and After Power On which will conclude Customization Specifications wizard.

Figure 3.22


30/53


30 VMware, Inc .

Once the Customization Specifications wizard closes you will be taken back to the VI Client viewdepicted in Figure 3.23. Under the Recent Tasks pane you should see an entry which will serve asconfirmation that the customization profile customization_appvm12 was successfully applied oapp_vm12 . The protected VM app_vm12 has now been customized and will start up with the networkconfiguration information assigned to the customization profile customization_appvm12 .

Figure 3.23


31/53

31 VMware, Inc.

Chapter 4: Using SRM to run a Test against a Recovery Plan

This chapter will provide an overview of how SRM enables you to Test a recovery plan by simulating afailover of virtual machines from the protected site to the recovery site. The benefit of using SRM to runa failover simulation against a recovery plan is that it allows you to confirm that the recovery plan hasbeen setup correctly for the protected VMs. You will be able to confirm that the protected VMs startup inthe correct order, taking into account the various application service dependencies for the protectedVMs in your environment.

It is worth pointing out that when you select the option to Test a recovery plan via SRM, the simulatedfailover is executed in an isolated environment that includes network and storage infrastructure at therecovery site that is isolated from the protected site (production environment) which ensures theprotected VMs at the protected site are not subject to any kind of service interruption during the testingof the recovery plan. SRM will also create a test report that can be used to demonstrate your level ofpreparedness to the business or individual business units whose services are being protected by SRMas well as to the auditors and compliance officers if required.

The simulated failover completes by resetting the environment to be ready for the next event whichcould be another simulated failover, or an actual failover for a scheduled BC/DR test or in response toan event which resulted in the business declaring a disaster.

Figure 4.1


32/53


32 VMware, Inc .

We will now work through a simulated failover leveraging the SRM Test a recovery plan option.In Figure 4.1 the VI Client lists the three Recovery Plans that were created by working through the Recovery Plan wizard. There are two ways to initiate the simulated failover, you can either click on theTest button in the toolbar or click on the Test Recovery Plan link under the Commands section, andboth are highlighted in Figure 4.1. Before the simulated failover is started you will be presented with thedialog box (Figure 4.2) that informs you the performance of local virtual machines may be impacted ifthere are insufficient compute resources at the recovery site to support the local virtual machines andprotected VMs. The dialog box also informs you that the replication of the datastore groups may besuspended during the simulated failover. Click Yes to start the Test of your recovery plan.

Figure 4.2

While the simulated failover test is running, the status of each step that makes up the recovery plan canbe monitored by going to Recovery Steps tab in the VI Client which will inform you what steps arecurrently Running as well as what steps were completed with a Success status. It is worth pointing outthat there are some steps in a recovery plan that will only be executed during a simulated test, thesesteps are identified by Test Only under the Mode column, there are also some steps that will only beexecuted during an actual failover, these steps are identified by Recovery only under the Modecolumn.

Figure 4.3


33/53


34/53


34 VMware, Inc .

Chapter 5: Using SRM to failover the Protected Site to the Recovery Site

This chapter will provide an overview of how SRM enables you to Run a recovery plan which will resultin the actual failover of virtual machines from the protected site; the failover process via SRM is rapid,repeatable, reliable, manageable and auditable.

Figure 5.1

We will now work through an actual failover leveraging the SRM Run a recovery plan option.In Figure 5.1 the VI Client lists the three Recovery Plans that were created by working through the Recovery Plan wizard. There are two ways to initiate the actual failover, you can either click on theRun button or click on the Execute Recovery Plan link under the Commands section, and both arehighlighted in Figure 5.1.

The Run Recovery Plan dialog box represented by Figure 5.2 warns you that you are about to run thea recovery plan which will result in changes to the protected virtual machines and the infrastructure ofboth the protected and recovery site datacenters. Click the radio button to confirm you understand theimplications of running your recovery plan and then click on the Run Recovery Plan button that is

highlighted in figure 5.2 to start the failover of protected VMs from the protected site to the recoverysite.

The Run Recovery Plan dialog box also provides a summary of the Recovery Plan Information , thatincludes the Recovery Plan that is going to be run, along with the names of the protected and recoverysites, the number of protected VMs that will be failed over as well as a connectivity status from therecovery site back to the protected site.


35/53

35 VMware, Inc.

Figure 5.2

While the failover is being executed, the status of each step that makes up the recovery plan can bemonitored by going to Recovery Steps tab highlighted i n Figure 5.1 of recovery sites VI Client whichwill inform you what steps are currently Running as well as what steps were completed with a Success status. Once again it is worth pointing out that there are some steps in a recovery plan that will only beexecuted during a simulated test, these steps are identified by Test Only under the Mode column,there are also some steps that will only be executed during an actual failover, these steps are identifiedby Recovery only under the Mode column.

Once all the protected VMs have been failed over and reported to be powered, which can be confirmedin several places from within the VI Client you are now ready to start validating that all applicationservices restarted cleanly at the recovery site, in this case we are referring to the protected VMsapp_vm7 through app_vm12 from Protection Group 2 which is associated to the datastore groupshared-san-2 . Once you have completed the validation of the failed over application services at therecovery site you are now in a position to report the successful failover to the business and allow therespective business users to access the application services which are now being hosted out of therecovery site.

Figure 5.3 shows a VMware topology map view, it is clear to see that app_vm7 through app_vm12were successfully failed over to the recovery site and that they are being hosted from a datastoreconnected to a host in the recovery site. The non replicated infrastructure VMs ( ad_server ,print_server , security_camera_server and virus_mgt_server ) are hosted from datastore vim23-storage1 in the recovery site.

Note: SRM will automatically perform a re-signature of the replicated datastore in the recovery site, whichmeans LVM.EnableResignature will be set to 1 on the ESX host/s that have access to the replicateddatastores in the recovery site. The re-signature that is initiated by SRM will result in the replicateddatastores being presented with a prefix of snap-0000000X- where X is a number, this is evident inFigure 5.3 which shows the replicated datastore presented as snap-000000020-shared-san-2 .


36/53


36 VMware, Inc .

Figure 5.3

As pointed out in the previous chapter SRM will automatically generate a report, in this instance thereport is for a SRM Run operation against the recovery plan we selected. The report is acessible viathe History tab and can be viewed by clicking on the View link under the Actions column.

The steps to failback services from the recovery site back to the protected site once the disaster eventis over will be outlined in the next chapter of this guide.

The following is a recap of the highlevel tasks excecuted by SRM when performing a failover of virtualmachines from the protected site to the recovery site via t he Run a recovery plan option that is availblevia SRM enabled VI Client. SRM automates many of the tasks required at time of failover. With thepush of one button, SRM:

will power down the protected VMs if there is connectivity between sites and they are online.

suspend data replication and Read/Write enable the replica datastores.

rescan the ESX servers at the recovery site.

registers the replicated protected VMs.

shuts down non-essential VMs at the recovery site if required to free up resources for theprotected VMs being failed over.

completes power-up of replicated protected VMs in accordance with the recovery plan.


37/53


38/53


38 VMware, Inc .

Site A - Protected Site

Source LUN(shared-san-2)

Protected VMs(app_vm7 to app_vm12)All powered off by SRM

at start of SRM Recovery

Site B - Recovery Site

Target LUN(shared-san-2)

Write Disabled(read only)

Read WriteEnabled

Protected VMs(app_vm7 to app_vm12)All powered on by SRM

during the SRM RecoveryNote: Datastore shared-san-1 will be in the same configuration state as shared-san-2

A Clone LUN is not used during a Recovery in SRM.

Storage configuration after running a Recovery in SRM (Actual Failover)from Site A to Site B for datastore shared -san-2

Data Replication is suspendedSource LUN in Site A with Target LUN in Site B

Figure 6.1

1. Ensure all users that were involved with the BC/DR test have completed their testscripts and are no longer accessing any of the protected VMs that were recovered fromSite A for the BC/DR test.

2. Shutdown all of the protected VMs that were recovered to Site B for the BC/DR test.3. Ensure you have created a list of all the Protected VMs that were recovered to Site B.4. Perform a cleanup of the directory in Site B that contained the VM configuration files

created during protection group creation in Site A (this is the location selected during

the creation of the original protection group/s in Site A - Protection Group 1 andProtection Group 2 , refer to Figure 3.8). Refer to Figure 6.2 for an example of theplaceholder VM configuration file information that was written to vim23-storage1 during the creation of the protection groups in Site A. You can use your list you createdin Step 3 above as a reference during this clean-up step.

Figure 6.2


39/53

39 VMware, Inc.

5. Connect to the VC instance in Site A and delete PG 1 ( Protection Group 1 andProtection Group 2 ). Refer to Figure 6.3, a protection group can be removed by rightclicking on the protection group in the right hand side Site Recovery pane.

Figure 6.3

6. Connect to the VC instance in Site A and perform a remove from inventory operationon all the protected VMs in Site A that were recovered to Site B. In Figure 6.4 all theprotected VMs in Site A have been selected, by right clicking on the selected VMsyou will be presented with a menu box, click on Remove from Inventory , which willthen remove the all the highlighted protected VMs from the VC inventory in Site A.

Figure 6.4


40/53


40 VMware, Inc .

7. Work with your Storage team to complete a storage configuration change personalityswap whereby the Source LUN is now associated with Site B and the Target LUN isassociated with Site A , as depicted in Figure 6.5. Rescan the ESX servers at theprotected and recovery site to ensure they become aware of the underlying storagechanges.

Site A - Recovery Site


Protected VMs(app_vm7 to app_vm12)

Protected VMs offlinein Site A

Site B - Protected Site



Read WriteEnabled


Protected VMs that will berecovered to Site A

Note: A Clone LUN is not configured in Site A and will not be used duringthe Failback from Site B back to Site A

Storage configuration prior to running a Recovery in SRM from Site B toSite A (Failback) after a storage configuration change personality swap

Data Replication is now configured from Site B to Site ASource LUN is in Site B with Target LUN in Site A

Figure 6.5

8. Complete the Array Manager configuration wizard from Site B. After the storage

configuration work is completed in Step 7, the Source LUN is now assigned to Site Band the Target LUN is assigned to Site A as depicted in Figure 6.6.

Figure 6.6


41/53

41 VMware, Inc.

9. Configure the Inventory Preferences in Site B, these inventory preferences will beassigned to the protected VMs when they are restarted in Site A after the failback.Figure 6.7 shows the inventory preferences that will be mapped to the protected VMs inSite A after the failback from Site B.

Figure 6.7

10. Connect to the VC instance in Site B and configure PG 2 ( Failback Protection Group1 and Failback Protection Group 2 ) in Site B as depicted in Figure 6.8 for theprotected VMs you wish to failback to Site A.

Figure 6.8

11. Connect to the VC instance in Site A and configure RP 2 in Site A. Note : You shouldnot delete RP 1 ( Recovery Plan 3 Complete Site Failover , refer to Figure 6.8) thatwas created in Site B during the initial SRM workflows that were completed to protect


42/53


42 VMware, Inc .

the designated VMs in Site A. Refer to Figure 6.9 which shows RP 2 ( FailbackRecovery Plan 3 ) which was created in Site A.

Figure 6.9

12. Using SRM complete the Failback of the original protected VMs back to Site A. This isaccomplished by performing a Recovery against RP 2 ( Failback Recovery Plan 3 )shown in Figure 6.9. Figure 6.10 depicts the storage configuration once the SRMRecovery against RP 2 completes.

Site A - Recovery Site


Site B - Protected Site



Read WriteEnabled

Note: A Clone LUN is not used during a Recovery in SRM (Actual Failover) in SRM.

Storage configuration after running a Recovery in SRM (Actual Failover)from Site B to Site A for datastore shared -san-2

Protected VMs(app_vm7 to app_vm12)All powered off by SRM

at start of SRM Recovery

Protected VMs(app_vm7 to app_vm12)All powered on by SRM

during the SRM Recovery

Data Replication is suspendedSource LUN in Site B with Target LUN in Site A

Figure 6.10


43/53

43 VMware, Inc.

13. Shutdown all of the protected VMs in Site A that were failed back from Site B during theSRM Recovery operation performed in Step 12.

14. Perform a cleanup of the directory in Site A that contained the VM configuration filescreated during protection group creation in Site B (this is the location selected duringthe creation of PG 2 in Site B, refer to Figure 3.8). Refer to Step 4 above for guidance ifrequired.

15. Connect to the VC instance in Site B and delete PG 2 ( Failback Protection Group 1 and Failback Protection Group 2 ) that were created in Site B. Refer to Step 5 abovefor guidance if required.

16. Connect to the VC instance in Site B and perform a remove from inventory operationon all the protected VMs in Site B that were recovered to Site A, in this scenario thiswould be app_vm1 to app_vm12 . Refer to Step 6 above for guidance if required.

17. Work with your Storage team to complete a second storage configuration changepersonality s wap whereby the Source LUN is now re-associated with Site A, theTarget LUN is re-associated with Site B along with the Clone LUN as depicted inFigure 6.11. Rescan the ESX servers at the protected and recovery site to ensure theybecome aware of the underlying storage changes. Note: The Storage configurationhas now been reverted back to the original configuration that was handed over to theVirtualization team prior to the setup of SRM and for this reason we depict the storageconfiguration in Figure 6.11 with the Clone LUN in Site B. The data synchronizationmethod (snapshot at intervals or continuous synchronization) of the Target LUN to theClone LUN is determined by the Storage Array vendor. When a simulated failover isinitiated via the Test option in SRM , final data synchronization is performed from theTarget LUN to the Clone LUN.

Site A - Protected Site


Site B - Recovery Site

Clone LUN(shared-san-2)

Read WriteEnabled

Data Replication continues between the Source LUN and Target LUNThe data synchronization between the Target LUN and the Clone LUN is suspended


Note: Datastore shared-san-1 will be in the same configuration state as shared-san-2


Protected VMs powered onin Site B during the SRM

Test failover


Protected VMs that will berecovered to Site B

Storage configuration during a SRM Test failover from Site A to Site Bfor datastore shared -san-2


Read WriteEnabled

Figure 6.11

18. Create PG 3 ( Protection Groups 1 and Protection Group 2 ) in Site A for theprotected VMs. Note: The protection groups you create here should be identical to theprotection groups that were originally associated with RP 1 ( Recovery Plan 3 Complete Site Failover ), the recovery plan that was executed in Recovery mode thatresulted in the startup of the protected VMs in Site B.


44/53


44 VMware, Inc .

19. Re-associate the protection groups created in step 19 in Site A with RP 1 ( RecoveryPlan 3 Complete Site Failover ) in Site B. Refer to Figure 6.12 which highlights thefirst part of the re-association which is initiated by right clicking on Recovery Plan 3 Complete Site Failover . Working through the Edit Recovery Plan wizard you will thenget to a screen that will require you to select which protection groups you wish to re-associate with the recovery plan, refer to Figure 6.13 which shows the two protectiongroups Protection Group 1 and Protection Group 2 that should be selected so theycan be re-associated with RP1 ( Recovery Plan 3 Complete Site Failover ) in Site B.Note : You do not need to delete the RP 2 ( Failback Recovery Plan 3 ) that wascreated in Site A to facilitate the recovery back to Site A from Site

Figure 6.12

Figure 6.13

20. Once the protection groups have been re-associated with the original recovery plan asdetailed in step 19 you have now completed the re-protection of the protected VMs inSite A with SRM. It is highly recommended to that you now complete a final Test asimulated failover against RP 1 ( Recovery Plan 3 Complete Site Failover ) toensure that Site A is protected and ready for any event that may necessitate aRecovery via SRM to Site B should the business deem it necessary to declare adisaster.


45/53

45 VMware, Inc.

Note: The SRM Failback steps 1 through 20 outlined in this Chapter did not detail the following:

Site Pairing from Site B back to Site A via the SRM Connection wizard : This step is notrequired as SRM maintains a bi-directional relationship between the paired sites, and thereforethe Connection workflow only needs to be completed once for Site A and Site B to ensure eachsite is aware of each VC and SRM instance in the respective sites.

SRM License transfer between Site A and Site B : The SRM failback steps did not discussthe transfer of SRM licenses between Site A and Site B that should be completed to ensure youare in compliance with the SRM EULA.

DNS Updates : SRM 1.0 does not provide a mechanism to update DNS. DNS updates will needto be completed by you as the virtual machines are moved between Site A and Site B withSRM and under go IP address changes to accommodate disparate networks in Site A and SiteB should they not be joined by Stretched VLANs.

Figure 6.14 shows a summary view of the SRM configuration of Site A which has now been revertedback to the original protected site. In addition to the two protection groups Protection Group 1 andProtection Group 2 which are associated with the recovery plan Recovery Plan 3 Complete SiteFailover in the designated recovery site Site B, we also have the recovery plan Failback RecoveryPlan 3 listed which was used to enable the failback procedure outlined in this chapter.

Figure 6.14


46/53


47/53

47 VMware, Inc.

Chapter 7: SRM Alarms and Site Status Monitoring

This chapter will provide an overview of some of the SRM Alarms that will be generated due to certaintypes of failures or conditions that may occur at the protected or recovery site. Awareness of the SRMalarms is an important part of understanding how SRM works across the protected and recovery sites.During the SRM product evaluation it is recommended that where possible and without impactto your production environment, failures or conditions be created in the protected and recoverysite that will result in the generation of SRM alarms . The generation of these SRM alarms will serveas validation that SRM is monitoring both the protected and recovery site correctly.

Each SRM server monitors the CPU utilization, disk space, and memory consumption of the guest onwhich it is running, and also maintains a heartbeat with its peer SRM server. VC events are sent if anyof these measures falls outside of configured bounds.

SRM will support the configuration of event-triggered alarms so that you can associate a notificationaction with any given SRM Alarm Event . These alarms are configured via the SRM UI.

SRM will support the following alarm notification actions:Send e-mail to specified addressSend SNMP trap to VC trap receiversExecute specified command on VC host

Please refer to Chapter 9 Alerting and Monitoring in the Administrators Guide for Site RecoveryManager which details how to setup the alarm actions listed above.

Failure of either site generates events which can be associated with VC alarms.Problems with the local site (e.g. resource constraints)

Problems with remote site (e.g., unable to ping remote site which may indicate a disaster)Remote site failure is reflected in the SRM Alarm Events and will not automatically trigger arecovery. This must be initiated manually.

SRM will raise VC events for the following conditions:Disk Space LowCPU use exceeded limit.Memory low.Remote Site not responding.Remote Site heartbeat failed.Recovery Plan Test started, ended, succeeded, failed, or cancelled.Virtual Machine Recovery started, ended, succeeded, failed, or reports a warning.

As a starting point during the SRM Evaluation we recommend you complete the Action setup for theSRM Alarm Events listed below for the protected and recovery sites. You should be able to triggerthese events in your environment without impacting your production environment, with the goal beingthat you see first hand how SRM responds and notifies you when subjected to one of the failure eventslisted below.

Remote Site DownRemote Site Ping FailedReplication Group RemovedRecovery Plan DestroyedLicense Server Unreachable


48/53


48 VMware, Inc .

Figure 7.1


49/53

49 VMware, Inc.

As you become more familiar with SRM, it associated workflows that allow you to Test your recoveryplans as well as Run your recovery plan which results in the failover of services from your protectedsite to your recovery site we recommend that you work through the list of SRM Alarm Events which areaccessed via the Alarms tab, as depicted in Figure 7.1 and enable the appropriate notification Actions for any additional SRM Alarm Events that you deem to be important for your environment.


50/53


50 VMware, Inc .

Chapter 8: SRM Roles and Privileges

This chapter will provide an overview of the SRM roles and the types of SRM privileges that can be set.Authorization in SRM uses the same authorization model as VirtualCenter Server.

Figure 8.1 show the default SRM roles which become available for use after the SRM plug-in has been

installed and enabled for use. To access these roles click on the Administration icon in the toolbar andclick on the Roles tab to see a list of all the roles that are available. These default SRM roles providethe ability to delegate control to a very granular level.

Figure 8.1


51/53

51 VMware, Inc.

There are two sets roles. The first set contains the roles required for the primary site user toadminister protection and the SRM roles are prefixed by Protection . The second set contains the rolesrequired for the secondary site user to administer recovery and the SRM roles are prefixed byRecovery .

Protection Side SRM Roles

Protection Virtual Machine Administrator : This role should be assigned on the protectedVirtual Machine object in the VC inventory. It grants the associated user the ability to setup andmodify the protection characteristics of the protected virtual machine.

Protection SRM Administrator : This role should be assigned on the Service Instance objectin the primary SRM inventory. It grants the associated user the ability to pair two sites,configure inventory mappings, and SAN arrays.

Protection Groups Administrator : This role should be assigned on the PrimaryConfiguration/Protection Service object in the SRM inventory. It grants the associated user theability to create and modify protection profiles/groups.

Recovery Side SRM Roles

Recovery Inventory Administrator : This role should be assigned on the root of the VCinventory. It grants the associated user the ability to view customization specifications existingon the secondary site.

Recovery Datacenter Administrator : This role should be assigned on the Datacenter objectin the VC inventory where the VMs will be recovered. It grants the associated user the ability toview available datastores and perform recovery (shadow) VM customizations.

Recovery Host Administrator : This role should be assigned on the Host or DRS cluster objectin the VC inventory where the VM will be recovered. It grants the associated user the ability toconfigure VM components during recovery.

Recovery Virtual Machine Administrator : This role should be assigned on the Folder andResource Pool objects in the VC inventory where the recovery (shadow) VMs are to be placed.It grants the associated user the ability to create and add shadow VMs to the resource pool andthe folder as well as the ability to reconfigure and customize the shadow VMs at runtime andduring the process of recovery.

Recovery SRM Administrator : This role should be assigned on the Service Instance object inthe secondary SRM inventory. It grants the associated user the ability to configure SAN arraysand create protection profiles.

Recovery Plans Administrator : This role should be assigned on the SecondaryConfiguration/Recovery Service object in the SRM inventory. It grants the associated user theability to reconfigure protection and shadow VMs and setup and run recovery.

Note : VirtualCenter already defines a Read-Only system role which can be used to grant users theability to view the Site Recovery Manager service. In addition, the Administrator role can be used togrant user complete control over both the protection and recovery SRM components.


52/53


52 VMware, Inc .

SRM also allows for the creation of custom SRM roles by allowing you to clone one of the default SRMroles and then by editing the cloned SRM role you can select which privileges should be associated tothe custom SRM role that you are creating. Figure 8.2 shows a Custom SRM Role and all the privilegesthat can be selected to complete the creation of the SRM Custom Role.

Figure 8.2


53/53

Conclusion

Site Recovery Manager will leverage your VMware Infrastructure to make disaster recovery:

Rapid - by automating the disaster recovery process for your virtual machines by eliminating thecomplexities of traditional physical disaster recovery.

Reliable - by ensuring proper execution of the recovery plan as well as the ability to enable easier,more frequent tests in an isolated environment without impacting services in the protected site.

Manageable - centrally manage recovery plans and make plans dynamic to match a dynamicvirtualized environment.

Affordable - utilize recovery site infrastructure and reduce management costs.

Site Recovery Manager will enable you to:

Expand disaster recovery protection - now any workload in a virtual machine can be protectedwith minimal incremental effort and cost.

Reduce time to recovery - as soon as a disaster is declared, SRM allows for the recovery ofprotected virtual machines with a few mouse clicks to the designated recovery site.

Increase reliability of recovery - replication of system state ensures your protected virtualmachines have all they need to startup in the protected site. Hardware independence which isrealized through your VMware Infrastructure eliminates failures due to different hardware.

Easier and more frequent testing SRM enables you to test your recovery plan in an isolatedenvironment without impacting services in the protected site while using the actual failoversequence that will be executed during a real disaster.

Date post:	10-Apr-2018
Category:	Documents
Upload:	zaq1234esz
View:	224 times
Download:	0 times

Srm 10 Eval Guide[1]

Documents