SRM 10 Admin

Administration Guide
Site Recovery Manager 1.0 Update 1

Site Recovery Manager Administration Guide

Item: EN-000096-00
You can find the most up-to-date technical documentation on the VMware Web site at:
http://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
docfeedback@vmware.com
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, 6,725,289, 6,735,601, 6,785,886, 6,789,156, 6,795,966, 6,880,022,
6,944,699, 6,961,806, 6,961,941, 7,069,413, 7,082,598, 7,089,377, 7,111,086, 7,111,145, 7,117,481,
7,149,843, 7,155,558, 7,222,221, 7,260,815, 7,260,820, 7,269,683, 7,275,136, 7,277,998, 7,277,999,
7,278,030, 7,281,102, 7,290,253, 7,356,679, 7,409,487, 7,412,492, 7,412,702, 7,424,710, 7,428,636,
7,433,951, 7,434,002, and 7,447,854; patents pending.
VMware, the VMware boxes logo and design, Virtual SMP, and VMotion are registered trademarks or
trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names
mentioned herein may be trademarks of their respective companies.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
2 VMware, Inc.
Contents
AboutThisBook 7
1 OverviewofSiteRecoveryManager 9
VMwareInfrastructureSupportsSiteRecoveryManager 9
SiteRecoveryManagerFeatures 10
SiteRecoveryManagerRequirements 11
SiteRecoveryManagerEnvironment 12
ArrayBasedReplication 13
SiteRecoveryManagerProcessOverview 14
InstallSRM 14
SetUptheProtectedandRecoverySites 15
ConfigureVirtualMachines 16
2 SystemRequirements 19
PrerequisitesforSRMInstallation 19
SRMHardwareandSoftwareRequirements 20
SRMDatabaseRequirements 21
MicrosoftSQLServerConfiguration 22
OracleServerConfiguration 23
ConfigurationMaximums 23
SRMLicensing 24
ImportLicenseFiles 24
3 InstallingorUpdatingSiteRecoveryManager 27
InstallSiteRecoveryManager 28
UpdateSiteRecoveryManager 31
InstalltheSiteRecoveryManagerPlugIn 31
UpdatingDatabaseCredentials 32
RevertingtoaPreviousRelease 32
VMware, Inc. 3
4 ManagingSRM 33
UsetheVIClienttoManageSRM 33
ConnectingtheProtectedandRecoverySites 34
CredentialBasedAuthentication 35
CertificateBasedAuthentication 36
SRMUsers,Groups,Permissions,andRoles 37
SRMPermissions 37
SRMDefaultRoles 38
AddRoles 39
AssignVirtualCenterAccessPermissions 39
AddaNewUserGroupandRoletoSRM 40
ChangeAccessPermissions 41
RemoveAccessPermissions 42
AccessSRMLogFiles 42
5 ProtectedSiteConfiguration 43
ConfiguringtheProtectedSite 43
RequirementsforVMwareInfrastructureConfiguration 44
ConfigureArrayManagers 44
RepairArrayManagers 46
ConfigureInventoryPreferences 47
CreateaProtectionGroup 48
ConfiguringVirtualMachineProperties 49
ConfigurePropertiesforProtectedVirtualMachines 50
AddMessageandCommandSteps 52
RunBatchFilesorCommands 52
IPAddressMapping 53
BatchIPPropertyCustomization 54
6 RecoverySiteConfiguration 59
CreateaRecoveryPlan 60
ManagingRecoveryPlans 61
EditaRecoveryPlan 62
TestaRecoveryPlan 63
Pausing,Resuming,orCancellingaTest 63
RunaRecoveryPlan 64
RemoveaRecoveryPlan 64
4 VMware, Inc.
Contents
ConfigureVirtualMachinesinaRecoveryPlan 65
ViewaRecoveryPlan 66
ViewRecoveryPlanHistory 67
ExportRecoveryHistoryResults 67
WorkwithCustomizationSpecifications 67
7 Failback 69
FailbackScenario 69
OtherFailbackConsiderations 74
8 AlertingandMonitoring 75
SRMAlarms 75
AboutSRMAlarmTriggers 76
EditSRMAlarmSettings 76
PrepareforAlarmNotificationbyEmail 78
9 ProtectedandRecoverySiteChanges 79
ChangestoVirtualCenterServer 79
ChangestoProtectedSites 79
ChangestoRecoverySites 80
A PreinstallationChecklist 81
B FailbackChecklist 83
C UsethesrmconfigcommandtorepairanSRMserverconnection 85
D AvoidingReplicationofPagingFilesandOtherTransientData 87
SpecifyaNonreplicatedDatastoreforSwapfiles 87
CreatingaNonreplicatedVirtualDiskforPagingFileStorage 88
Glossary 91
Index 93
VMware, Inc. 5
6 VMware, Inc.
About This Book
Thismanual,theSiteRecoveryManagerAdministrationGuide,providesinformation
aboutinstallingandconfiguringVMwareSiteRecoveryManager(SRM),adisaster
recoverypluginforVMwareVirtualCenterServer.Theinformationincludesa
conceptualoverviewofconfiguringandmanagingsites,recoveryplanning,testingand
performingfailover,alerts,systemmanagement,andtroubleshooting.
Intended Audience
ThismanualisintendedforanyonewhowantstoinstalloruseSiteRecoveryManager.
TheinformationinthismanualiswrittenforexperiencedWindowsorLinuxsystem
administratorswhoarefamiliarwithvirtualmachinetechnologyanddatacenter
operations.ThismanualalsoassumesfamiliaritywithVMwareVirtualInfrastructure,
includingVMwareESX3.x,theVirtualCenterServer2.5,andtheVIClient.Youshould
alsohaveworkingknowledgeofstoragenetworktechnology,specificallyFibreChannel
oriSCSIstorageareanetworksandhowVirtualInfrastructureinteractswiththem.
VMware Infrastructure Documentation

IfyouarenotalreadyfamiliarwiththeVIClient,consulttheVMwareInfrastructure
documentation,whichconsistsofthecombinedVirtualCenterServerandESXServer
documentationset.Documentationisavailablefrom:
http://www.vmware.com/support/pubs/
VMware, Inc. 7
Document Feedback
VMwarewelcomesyoursuggestionsforimprovingourdocumentation.Ifyouhave
comments,sendyourfeedbacktodocfeedback@vmware.com.
Technical Support and Education Resources

Thefollowingsectionsdescribethetechnicalsupportresourcesavailabletoyou.
To accessthecurrentversionofthisbookandotherbooks,goto
http://www.vmware.com/support/pubs.
Online and Telephone Support

Touseonlinesupporttosubmittechnicalsupportrequests,viewyourproductand
contractinformation,andregisteryourproducts,goto
http://www.vmware.com/support.
Customerswithappropriatesupportcontractsshouldusetelephonesupportforthe
fastestresponseonpriority1issues.Goto
http://www.vmware.com/support/phone_support.html.
Support Offerings
TofindouthowVMwaresupportofferingscanhelpmeetyourbusinessneeds,goto
http://www.vmware.com/support/services.
VMware Professional Services

VMwareEducationServicescoursesofferextensivehandsonlabs,casestudy
examples,andcoursematerialsdesignedtobeusedasonthejobreferencetools.
Coursesareavailableonsite,intheclassroom,andliveonline.Foronsitepilot
programs andimplementationbestpractices,VMwareConsultingServicesprovides
offeringsto helpyouassess,plan,build,andmanageyourvirtualenvironment.
To accessinformationabouteducationclasses,certificationprograms,andconsulting
services,gotohttp://www.vmware.com/services.
8 VMware, Inc.
1
Overview of Site Recovery

Manager 1
Adisasterisanyeventthathaltsbusinessactivityonalargescale.Adisasterthataffects
ITresourcescouldmeanbusinessdowntimewhileyourecoverdataandvalidate
systemsforuse.
Thecatastrophiceffectsofadisasteraremitigatedifyouareprepared.WithVMware
SiteRecoveryManager,youcanquicklyrestoreyourorganizationsITinfrastructure,
dramaticallyshorteningthelengthoftimethatyouexperienceabusinessoutage.
ThischapterintroducesSRMandincludesthefollowingtopics:
VMwareInfrastructureSupportsSiteRecoveryManageronpage 9
SiteRecoveryManagerFeaturesonpage 10
SiteRecoveryManagerRequirementsonpage 11
SiteRecoveryManagerEnvironmentonpage 12
SiteRecoveryManagerProcessOverviewonpage 14
VMware Infrastructure Supports Site Recovery Manager

ThefollowingfeaturesofVMwareInfrastructuresupportSRM:
EncapsulationVirtualmachinesareencapsulatedintoagroupoffilesinshared
storage.
BootfromsharedstorageReplicationofthesharedstoragemeansyouhavefully
replicatedhardwareindependentvirtualmachinesreadytopoweronasneeded.
VMware, Inc. 9
VMwareDistributedResourceScheduler(DRS)andresourcepoolsVMware
DRSallocatesandbalancescomputingcapacityacrossresourcepoolstomatch
availableITresources.Youdonotneedtodeterminetheplacementofrecovery
virtualmachinesinadvanceofafailover.
HardwareindependenceUsingvirtualmachines,recoveryfailuresarenearly
zerobecauseanyvirtualmachinecanberebootedfromanypieceofhardware
withouttheneedtofixdrivers.
InstantrepurposingWithouttheconstraintofsystemreinstallation,hardware
canperformcompletelydifferentwork,perhapsonacompletelydifferent
operatingsystem,inamatterofminutes.
VirtualLocalAreaNetworks(VLANs)VirtualLANsallowyoutoisolate
networktrafficforvirtualmachines,sotestingcanbenondisruptive.
ChangecontrolandauditabilityThechangecontrolfeaturesofVMware
Infrastructurehelpyoumanageyourdisasterrecoverystrategy.Tasktracking
allowsyoutoviewchangestoSRM.
Site Recovery Manager Features

SiteRecoveryManagerisadisasterrecoveryworkflowproductthatautomatessetup,
failover,andtestingofdisasterrecoveryplans.
PreparedresponsereduceserrorSRMhelpsyoureducethepossibilityofhuman
errorifadisasteroccurs,becauseyourrecoverystrategyismappedout,tested,and
rehearsed.
NondisruptivetestsRecoveryplantestingusingarraysnapshotsandisolated
networktrafficwithanalternateVLANallowsyoutotestwithoutinterrupting
dailyproductionworkflows.
LeveragedstorageSRMisintegratedwitharraybasedreplicationtoeliminate
configurationerrorsonsetupthatareeasytomakeotherwise,andusuallyhave
dramaticimplications.
NetworkreconfigurationofrecoveredvirtualmachinesEachvirtualmachineis
connectedtothecorrectVLANandreconfiguredwithguestIPsettingsthatare
presetinSRM,whichmeansthatyoudonothavetomanuallyreconfigureeach
virtualmachineatrecoverytime.
10 VMware, Inc.
Chapter 1 Overview of Site Recovery Manager
CPUandmemoryqualityofserviceforrecoveredvirtualmachinesEach
virtualmachineisrecoveredinareconfiguredresourcepoolatthedestinationsite
sothatithasthecorrectCPUandmemoryresourcesatrecoverytime.Thisway,
youareensuredthattherecoveredvirtualmachinescandotheworkexpectedof
themwithouthavingtoprespecifyvirtualmachinetohostmappingsforeachof
hundredsofvirtualmachines.
PredictablemanagementofrecoveredvirtualmachinesVirtualmachinesare
organizedintheVirtualCenterhierarchyattheremotesitesothatadministrators
canimmediatelyunderstandthepurposeofeachvirtualmachine.
InstantupdatesChangestoyourrecoveryplanareinstantlyreflectedinthetest
andfailoverworkflows.
MonitoringandalertsSRMmonitorseventssuchasfailureoftheremotesiteto
respondorthestartandfinishofarecoverytest.Notificationsareprovidedinan
emailmessagetotheSRMsystemadministrator.
Site Recovery Manager Requirements

TouseSRM,thefollowingarerequired:
VirtualCenterServerinstalledattheprotectedsiteandattherecoverysite
Preconfiguredarraybasedreplicationbetweentheprotectedsiteandthe
recoverysite
NetworkconfigurationthatallowsTCPconnectivitybetweentheSRM
servers,VirtualCenterservers,andVirtualInfrastructureclients
OracleorSQLServerdatabasesontheprotectedsiteandtherecoverysitethat
useODBCforconnectivitywithadedicateddatastoreforSRM
SRMlicenseinstalledintheVirtualCenterlicenseserverattheprotectedsite
andattherecoverysite
Foradescriptionofminimumconfigurationrequirements,seePrerequisitesforSRM
Installationonpage 19.
VMware, Inc. 11
Site Recovery Manager Environment

Figure 11illustratesthekeycomponentsofSRM.
Figure 1-1. Prerequisite Environment for SRM

VI Client
UI plugin
VCMS VirtualCenter VirtualCenter VCMS

DB Server Server DB
TCP
Site TCP Site
Oracle ODBC Recovery Recovery ODBC Oracle
or SQL Manager Manager or SQL
DB License License DB
Server Server
replication replication
adapter adapter
ESX ESX ESX ESX ESX

Server Server Server Server Server
VM VM VM VM VM
VM VM VM VM VM
SAN SAN
VMFS VMFS VMFS VMFS VMFS
primary site secondary site
array replication
Thesecomponentsaredescribedasfollows:
VirtualCenterServerThecentralpointforconfiguring,provisioning,and
managingvirtualizedITenvironments.
SiteRecoveryManagerServerAphysicalorvirtualhostonwhichSRMandone
ormorearraymanagersareinstalled.
LicenseServerAserverthatstoresandallocateslicenses.
OracleorSQLDatabasePersistentstorageforSRMobjects.
ESXServersA virtualization layer run on physical servers that abstracts processor,

memory, storage, and networking resources into multiple virtual machines.
12 VMware, Inc.
SANStorageareanetwork(FibreChanneloriSCSIarrays)supporting
arraybasedreplication.
VMwareFileSystem(VMFS)Aclusteredfilesystemthatisoptimizedfor
storingvirtualmachines.
Array-Based Replication
SRMsupportsarraybasedreplicationinwhichoneormorestoragearraysatthe
protectedsitereplicatetheirdatatopeerarraysattherecoverysite.Storagereplication
adapters(SRAs)arearrayspecificprogramsthatarrayvendorsprovidetosupportthe
useofarraybasedreplicationbySRM.SRAsarenotpartofanSRMrelease.Yourarray
vendorprovidesandsupportsSRAs.YoucanalsodownloadthemfromtheVMware
Website.YoumustinstallSRAsspecifictothearraysthatyouwanttousewithSRMon
theSRMserverhost.
LUN Replication and Datastores

EachstoragearraysupportsasetofLUNs(logicalstorageunitscomprisingoneor
morephysicaldevices).AgivenLUNmayormaynotbereplicated.BecauseVirtual
MachineFileSystem(VMFS)datastorescanspanmultipleLUNs,SRMmustensure
thatallLUNsinadatastorearereplicated.
Beforevirtualmachineprotectionisconfigured,SRMpresentsalistofdatastoregroups
andthevirtualmachinestheycontain.Ifthelistofdatastoregroupsisnotwhatyou
expected,correctitbeforeyoucontinue.YoucanuseStorageVMotion(ESX3.5and
higher)tomoveindividualvirtualmachines.IfthewrongsetofLUNsisreplicated,
reconfigurethereplication.
NOTEThisverificationstepisacriticalcheckpointthateliminatesoneofthebiggest
sourcesoferrorindisasterrecoveryplans.
Protection Groups
Aprotectiongroupisagroupofvirtualmachinesthatfailovertogether.Oneprotection
groupmustbecreatedforeachreplicateddatastore.Aftertheprotectiongroupsare
createdattheprotectedsite,they(andtheirvirtualmachines)mustalsobeaddedto
recoveryplansontherecoverysitetocompletetheSRMsetup.
Whennewvirtualmachinesarecreatedonreplicateddatastores,eventsarecreated
(andalarmscanbeassociatedwiththoseevents)thatnotifyyouwhentheyare
triggered.Whenthishappens,gototheprotectiongroup,findtheunconfiguredvirtual
machines,andmodifythesettingsforeachvirtualmachine.
VMware, Inc. 13
Site Recovery Manager Process Overview

WithSRM,youcansetuparecoverysitethatcontinuouslyreplicatesyourproduction
site.Youdevelopadisasterrecoveryplan,resultinginaprocessthatistestedtomeet
yourrecoveryobjectives.Ifadisasteroccurs,thefailoverprocessenablesyoutobring
resourcesbackintoserviceinorderofpriority.
Install SRM
SRMincludesaservercomponentthatmustbeinstalledateachsiteandaclientplugin
thatyoudownloadfromtheserverandinstallinaVIClientthatyouusetomanage
SRMservices.Figure 12illustratesatypicalSRMinstallation.
Figure 1-2. SRM Installation Architecture
VirtualCenter VirtualCenter
VCMS 1 DB Server 1 Server 2 VCMS 2 DB
SRM server 1 SRM server 2

SRM 1 DB SRM 2 DB
storage storage
replication replication
adapter adapter
array 1 array 2
block replication block replication
software software
protected site recovery site
EachsitehasaVirtualCenterServerhost,whichisaWindowsmachinethatrunsthe
VirtualCenterservice.TheSRMservershouldbeinstalledonadedicatedserverhostif
possible,butcanbeinstalledontheVirtualCenterServerhostifnecessary.Storage
replicationadaptersareinstalledontheSRMserverhost.TheSRMdatabaseateachsite
holdsinformationaboutvirtualmachineconfigurations,protectiongroups,and
recoveryplans.SRMcannotusetheVirtualCenterdatabasebecauseithasdifferent
databaseschemarequirements.YoucanusetheVirtualCenterdatabaseservertocreate
andsupporttheSRMdatabase.
14 VMware, Inc.
InstallingSRMincludesthefollowingtasks:
1 ConfigureSRMdatabasesatbothsites.
2 InstalltheSRMserveratbothsites,andconnecteachservertoitscorresponding
database.
3 InstallthestoragereplicationadaptersforyourarraysontheSRMserverateach
site.
4 InstalltheSRMclientpluginintooneormoreVirtualCenterclientsateachsite.
5 UsetheSRMclienttoconnecttheprotectedandrecoverysites.
6 UsetheSRMclienttoconfigurethearraymanagersateachsite.
Set Up the Protected and Recovery Sites

Afterinstallation,setuptheprotectedandrecoverysites.
Figure 1-3. Relationship of Computing Resources in the Protected Site to the

Recovery Site
Recovery Plan 1
VMFS 1
apps (whole site)

LUN 1
OS Protection Groups
Datastore Group 1 Protection Group 1 Protection Group 1
Protection Group 2
apps Protection Group 3
LUN 2
VMFS 2
OS
apps apps apps apps

LUN 3 apps OS
OS OS OS
OS
Datastore Group 2 Protection Group 2
Recovery Plan 2
(subset)
VMFS 3
Protection Groups
LUN 4
Protection Group 1
apps
OS
VMFS 4
LUN 5 apps
OS
Datastore Group 3 Protection Group 3
protected site recovery site
VMware, Inc. 15
Ontheprotectedsite,virtualmachinesareassignedtoprotectiongroups.Aprotection
groupisacollectionofvirtualmachinesthatallusethesamedatastoregroup(thesame
setofreplicatedLUNs)andfailovertogether.
Useprotectiongroupstocontroltheorderinwhichvirtualmachinesarerestoredafter
afailover.Forexample,criticalbusinessapplicationsmightbeassignedtoProtection
Group1,whilelowerpriorityapplicationsareassignedtoProtectionGroup2and
optionalapplicationsareassignedtoProtectionGroup3.Intherecoveryplan,
ProtectionGroup1failsoverfirst,followedbygroup2,andthengroup3.
Ontherecoverysite,createoneormorerecoveryplans.Arecoveryplanisanordered
setofstepsthatcontrolwhathappensduringafailover.Youcandevelopmultiple
recoveryplanstoaddressmultipledisasterscenarios.Settinguptheprotectedand
recoverysitesincludesthefollowingtasks:
1 Understandthedatastoregroupsyouhaveavailable.SRMdeterminestheseusing
informationfromthestoragereplicationadapters.
2 Createinventorymapsfortheprotectedvirtualmachines.
3 Createprotectiongroupsforeachdatastoregroup.
4 Configureprotectiongroupsettings,whichprovideconfigurationdefaultsforall
virtualmachinesintheprotectiongroup.
5 Createarecoveryplan,withprompts,scriptcallouts,andnotificationsasneeded.
Configure Virtual Machines

SRMenablesyoutospecifyinventorypreferencesthatcontrolhowvirtualmachine
resourcessuchasfolders,resourcepools,andnetworksattheprotectedsiteare
mappedtosimilarresourcesattherecoverysite.Thisinventorymappingensuresthat
protectedvirtualmachinesareconfiguredproperlytopoweronandconnecttothe
networkattherecoverysite.
16 VMware, Inc.
Figure 1-4. Mapping of Virtual Machines from Protected Site to Recovery Site
Global Inventory Mappings Between Sites
Source VC Destination VC
Folder 1 Folder 2 VM Settings at Recovery Site
Folder 3 Folder 4 Inherited Inventory Mappings

(overrides allowed)
Folder 5 Folder 6
Folder Folder 6
Resource Pool 1 Resource Pool 2
Resource Pool Resource Pool 6
Network Port Group 2
Inherited Protection Group Settings
Port Group 1 Port Group 2 (overrides allowed)
Port Group 3 Port Group 4 Temporary Files Datastore 1
Port Group 5 Port Group 6 Per VM Settings
Priority High (defaults normal)
Global Inventory Mappings Between Sites
Network Settings IP, subnet, gateway, DNS, etc.
Temporary Files Datastore 1
Globalpreferencesareappliedtoallvirtualmachinesinaprotectiongroup.Youcan
alsocanapplycustomsettings,suchasnetworkconfigurationinformationto
individualvirtualmachines.
Configuringthevirtualmachinesincludesthefollowingtasks:
1 Configureinventorymappings
2 Configureprotectiongroups
3 Configurevirtualmachinesettings
VMware, Inc. 17
18 VMware, Inc.
2
System Requirements 2
Thischapterdescribesthehardware,operatingsystem,andlicensingrequirementsfor
VMwareSiteRecoveryManager(SRM).Usetheinformationinthischaptertoensure
thatyourenvironmentmeetstherequirementsforinstallation.
SeetheSiteRecoveryManagerCompatibilityMatrixesforacompletelistofSRM
compatibilityrequirements.
Thischapterincludesthefollowingtopics:
PrerequisitesforSRMInstallationonpage 19
SRMHardwareandSoftwareRequirementsonpage 20
SRMDatabaseRequirementsonpage 21
ConfigurationMaximumsonpage 23
SRMLicensingonpage 24
Prerequisites for SRM Installation

VMwareInfrastructuremustmeetthefollowingrequirements:
TheVirtualCenterServer2.5Update1orhigherandVIClient2.5installedand
runningattheprotectedandrecoverysites.TheVirtualCenterServerhostshould
haveastaticIPaddressifpossible.
VirtualmachinesresidingonESXhoststhattheVirtualCenterServermanages,in
datastoreshostedonreplicatedarrays.
Noreplicateddatastorecanbeaccessiblefrommorethanonedatacenter.
VMware, Inc. 19
Storagearraysmustmeetthefollowingrequirements:
Arraybasedreplicationandstoragereplicationadaptersinstalledandconfigured
attheprotectedandrecoverysites.
Arraymanagementmightalsorequiretheinstallationofothervendorprovided
components.Someofthesecomponentsmightneedtobeinstalledonthesame
hostastheSRMserver;othersmightrequireonlynetworkaccessbytheSRMserver.
SRMmightoccasionallyneedtorescanstoragearrays.Youcanimprovearray
rescantimesbychangingdefaultvalueoftheScsi.RescanAllHbas onESXhosts.
IfrescantimesonESXhostsarelongerthan10minutes,youmaywanttosetthe
valueofthisoptionto1.
MaskingandzoningisconfiguredforreplicatedLUNstoremoteESXhostsfor
failover.VMwarerecommendsthatyouconfigurestoragetocreateclonesor
snapshotsofthereplicatedLUNs.Snapshotsorclonesmustbemaskedtothe
recoveryESXhosts.
UnlesstheSRMserverandVirtualCenterserverareinstalledonthesamehost,you
mustaddthefollowingportstotheWindowsFirewallexceptionlisttoenable
interprocesscommunicationbetweenSRMandVirtualCenter:
SRMCommunicationsSOAPport(default8095)
SRMClientDownloadHTTPport(default8096)
SRMExternalAPISOAPport(default9007)
SRM Hardware and Software Requirements

TheSRMhardwaremustmeetthefollowingrequirements:
Processor2.0GHzorhigherIntelorAMDx86processor.
Memory2GBminimum.
DiskStorage2GBminimum.
NetworkingGigabitrecommended.
VMwareSRMrunsonthefollowingMicrosoftWindowsoperatingsystems:
WindowsXPProfessionalwithSP2
Windows2003ServerR2
Windows2003ServerSP1(allreleasesexcept64bit)
Windows2000ServerSP4withUpdateRollup1
20 VMware, Inc.
Chapter 2 System Requirements
TheSRMpluginisinstalledintheVIClient.TheSRMpluginisdesignedtorunon
MicrosoftWindowsoperatingsystemsandisdesignedforthe32bitversionsofthe
followingoperatingsystems:
Windows2000ProfessionalwithSP4UpdateRollup1(MSIinstaller
version 3.1.4000.2435orlater)
WindowsXPProfessional32bitwithSP2(MSIinstallerversion3.1.4000.2435or
later)
Windows2003withSP1(allreleasesexcept64bit)
Windows2003ServerR2
WindowsVistaBusiness
WindowsVistaEnterprise
TheVIClientrequirestheMicrosoft .NET2.0Framework.Ifyoursystemdoesnot
haveitinstalled,theVIClientinstallerinstallsit.
NOTETheSRMserverhostshouldhaveastaticIPaddressifpossible.
SRM Database Requirements

TheSRMdatabaseateachsiteholdsinformationaboutvirtualmachineconfigurations,
protectiongroups,andrecoveryplans.SRMcannotusetheVirtualCenterdatabase
becauseithasdifferentdatabaseschemarequirements.YoucanusetheVirtualCenter
databaseservertocreateandsupporttheSRMdatabase.
EachsiterequiresitsowninstanceoftheSRMdatabase.Thedatabasemustexistbefore
SRMcanbeinstalled.YoumustnotreinitializethedatabaseafterSRMinstallationis
complete.DoingsowillcauseSRMtofail.IfyoumustreinitializetheSRMdatabase,
reinstallSRM,specifyinganewdatabaseconnection,afterthereinitializationis
complete.
Eachdatabaserequiresadditionalconfigurationafterthebasicinstallation.See
MicrosoftSQLServerConfigurationonpage 22andOracleServerConfiguration
onpage 23.
VMware, Inc. 21
Table 21liststhedatabasesthatSRMsupports.
Table 2-1. SRM Supported Databases
Database Type Service Pack, Patch, and Driver Requirements
MicrosoftSQLServer2005Enterprise SP1orSP2
(64bitversionwithSP2isalsosupported) ForWindows2000andWindowsXP,apply
MDAC2.8SP1totheclient.
UseSQLnativeclientdriverfortheclient.
MicrosoftSQLServer2005Standard UseSQLnativeclientdriverfortheclient.
MicrosoftSQLServer2005Express UseSQLnativeclientdriverfortheclient.
MicrosoftSQLServer2000Enterprise SP4
MicrosoftSQLServer2000Standard SP4
Oracle9irelease2Standard Applypatch9.2.0.8.0totheserverandclient.
Oracle9irelease2Enterprise Driverversion10.02.x.x
Oracle10gEnterpriseRelease1 Driverversion10.02.x.x
Oracle10gEnterpriseRelease2 Firstapplypatch10.2.0.3.0totheclientandserver.
(64bitversionisalsosupported) Thenapplypatch5699495totheclient.
Driverversion10.02.x.x
Microsoft SQL Server Configuration

MicrosoftSQLServerhasthefollowingconfigurationrequirementswhenusedwith
SRM:
Theschemanamemustbethesameastheusername.Youmusthaveadefault
schemaassociatedwithyouruseraccount.
Youmusthavebulkinsertadministratorprivileges.
IfyouareusingWindowsauthentication,theSRMserveranddatabaseserver
mustrunonthesamehost.
IfSQLServerisinstalledlocally,youmightneedtodisabletheSharedMemory
networksettingonthedatabaseserver.
TheSRMdatabaseusermustbegrantedthefollowingpermissions:connect,create
table,createview.
22 VMware, Inc.
Oracle Server Configuration

OracleServerhasthefollowingconfigurationrequirementswhenusedwithSRM:
IfyouareusinganOracle9iserver,theSRMBulkInsertfeaturemustbedisabled.
Editthevmware-dr.xmlconfigurationfileandchangetheEnableBulkInsert
settingtofalse.Thedefaultlocationofthisfileis:C:\Program
Files\VMware\VMware Site Recovery Manager\config\.Afteryouchange
theconfigurationfile,restarttheVMwareSiteRecoveryManagerServiceservice
foreachSRMserverthatisusingthisdatabase.
Usedriverversion10.02.x.xforallsupporteddatabaseversions.
TheSRMdatabaseusermustbegrantedthefollowingpermissions:connect,
resource,createsession,createview.
Configuration Maximums
Whenyouareselectingandconfiguringyourvirtualandphysicalequipment,you
mustnotexceedcertainlimitsimposedbySRM.Table 22liststhelimitsforprotected
virtualmachines,protectiongroups,andreplicatedLUNssupportedbyasingleSRM
server.SRMpreventsyoufromexceedingthelimitsonprotectedvirtualmachinesand
protectiongroupswhenyoucreateanewprotectiongroup.Ifaconfigurationcreated
inanearlierversionofSRMexceedstheselimits,SRMdisplaysawarning,butallows
theconfigurationtooperate.Reconfiguresuchconfigurationstobringthemwithin
supportedlimitsassoonaspossible.
Table 2-2. SRM Configuration Maximums

Item Maximum
Protectedvirtualmachines 500
Protectiongroups 150
ReplicatedLUNs 150
Runningrecoveryplans 3
LimitsonreplicatedLUNsandrunningrecoveryplansareadvisory,butnotenforced.
VMware, Inc. 23
SRM Licensing
SRMrequirestwotypesoflicensekeys:
Aprotectionenablementlicensekey(SRM_PROTECTED_HOST)thatspecifies
thenumberofESXCPUsthatcanrunprotectedvirtualmachinesatasite.Install
thiskeyattheprotectedsitetoenablefailover.Installitattherecoveryand
protectedsitestoenablebidirectionaloperation(failback).
Asiteenablementlicensekey(PROD_SRM)thatmustbeinstalledattheprotected
siteandtherecoverysite.Thesekeysaresuppliedwhenyoupurchaseyour
protectionenablementkeys.
Toobtainyourlicensekeys,gototheSiteRecoveryManagerProductInformationpage
attheVMwareWebsite.
SRMlicensingchecksforavalidlicensewhenthehostlicenseisfirstinstalledandeach
timetheSRMhostdprogramrestarts.Licensesacquiredfromalicenseserverare
checkedeveryfiveminutes.Iflicensesarenotincompliance,VirtualCentertriggersa
licensingalarm.VMwarerecommendsthatyouconfigurealertsfortriggeredlicensing
eventssothatlicensingadministratorsarenotifiedbyemail.SeeAlertingand
Monitoringonpage 75formoreinformation.
Import License Files

WhentheVMwarelicenseserverisinstalled,youcanimportSRMlicensefilesintoyour
licenseserver.Youmustinstallthepersitelicenseattheprotectedandrecoverysites.
Youmustinstalltheprotectionenablementlicenseattherecoverysitetoenablefailover,
andattherecoveryandprotectedsitestoenablebidirectionaloperation(failback).
FormoreinformationabouttheVMwarelicenseserver,seetheESXServer3Installation
Guide.
To enable an SRM license

1 Logintothecomputerthatrunsthelicenseserverapplication.
Theprotectedandrecoverysitesshouldeachhavetheirownlicenseservers.
2 CopytheSRMlicensefilethatincludesthePROD_SRMkeytoC:\Program
Files\Vmware\VMware License Server\Licenses\.
Licensefilesmusthavea.licextension.
3 Ifthisisasitewhereyouwanttoenableprotectedvirtualmachinestorun,copy
theSRMlicensefilethatincludestheSRM_PROTECTED_HOSTkeyto
C:\Program Files\Vmware\VMware License Server\Licenses\.
24 VMware, Inc.
4 LaunchVMwareLicenseServerToolsbychoosingStart>Programs>VMware>
VMwareLicenseServer>VMwareLicenseServerTools.
5 ClicktheStart/Stop/Rereadtab.
6 ClickReReadLicenseFiletoloadthenewlicensefiles.
7 RestarttheSRMserver.
VMware, Inc. 25
26 VMware, Inc.
3
Installing or Updating Site

Recovery Manager 3
YoumustinstallanSRMserverattheprotectedsiteandalsoattherecoverysite.After
theSRMservershavebeeninstalled,youcandownloadtheclientpluginfromeither
servertoanyVIClientandusethatclienttoconfigureandmanageSRMateithersite.
SRMrequiresthesupportofaVirtualCenterserverateachsite.TheSRMinstallermust
beabletoconnectwiththisserverduringinstallation.IfyoucannotinstallSRMona
dedicatedserverhost,youcaninstallitonthesamehostwheretheVirtualCenter
Serverisinstalled.
InstallingSRMincludesthefollowingtasks:
1 InstallSRMontheprotectedsite.
2 InstallSRMattherecoverysite.
3 UsingaVIClient,connecttoaVirtualCenterServerattheprotectedorrecovery
siteanddownloadtheSRMplugin.
UpdatingSRMincludesthefollowingtasks:
1 BackuptheSRMdatabaseattheprotectedandrecoverysites.
2 UpdateSRMontheprotectedsite.
3 UpdateSRMattherecoverysite.
4 UsingaVIClientonwhichtheSRMpluginisnotinstalled,connecttoa
VirtualCenterServerattheprotectedorrecoverysiteanddownloadanewSRM
plugin.
VMware, Inc. 27
InstallSiteRecoveryManageronpage 28
UpdateSiteRecoveryManageronpage 31
UpdateSiteRecoveryManageronpage 31
Install Site Recovery Manager

BeforeinstallingSRM,ensurethatyoucompletedalltherequirementslistedin
Chapter 2,SystemRequirements,onpage 19.Inparticular,youneedthefollowing
informationforeachsite:
ThehostnameorIPaddressofarunningVirtualCenterServerSRMand
VirtualCentercanresideonthesamehostorondifferenthosts.DuringSRM
installation,youmustsupplytheVirtualCenterhostnameorIPaddress.
TheusernameandpasswordoftheVirtualCenteradministratorDuringSRM
installation,youmustsupplyavalidusernameandpasswordforthe
VirtualCenteradministrator.
AusernameandpasswordfortheSRMdatabaseFormoreinformation,see
SRMDatabaseRequirementsonpage 21.
NOTEDuringinstallation,SRMstoresthehostnamesoftheSRMserverand
VirtualCenterserverhosts.Ifyouhavetochangeeitherofthesehostnames,youmust
reinstallSRM.
To install SRM
1 LogintotheserverhostonwhichtoinstallSRM.
ToinstallSRM,youmustloginasamemberofthehostsAdministratorsgroup.
2 DownloadtheSRMinstallationfiletoafolderonthehost,oropenafolderonthe
networkthatcontainsthisfile.
3 DoubleclicktheSRMinstallericontobegininstallation.
TheinstallerexaminesthesetofinstalledVMwaresoftwareonthehost.Ifitdetects
anexistinginstallationofSRM,itpromptsyoutoverifythatyouwanttoupdate
theexistinginstallation.FormoreinformationaboutupdatingSRM,seeTo
updateSRMonpage 31.
4 ClickNextontheWelcometotheinstallationwizardscreen.
5 OntheLicenseAgreementpage,clickIacceptthetermsinthelicenseagreement
andthenclickNext.
28 VMware, Inc.
Chapter 3 Installing or Updating Site Recovery Manager
6 AttheDestinationFolderscreen,choosethefolderinwhichyouwanttoinstall
SRMandclickNext.
Thepathnametotheinstallationfoldercannotbelongerthan240characters,and
cannotincludeanynonASCIIcharacters.
7 EnterthefollowinginformationabouttheVirtualCenterserveratthesitewhere
youareinstallingSRM:
VirtualCenterAddressEnterthehostnameorIPaddressofthe
VirtualCenterServer.
TheVirtualCenterServerandtheSRMservermustbeinthesamedomain.
Enterthehostnameinlowercase.Afterinstallationiscompleteandyouare
configuringtheconnectionbetweentheprotectedandrecoverysites,you
mustsupplythishostnameorIPaddressexactlyasyouenterithere.
VirtualCenterPortAcceptthedefaultorenteranotherport.
VirtualCenterUsernameEnterauserIDthathasadministratorprivilegeson
thespecifiedVirtualCenterServer.
VirtualCenterPasswordEnterthepasswordforthespecifieduserID.
ClickNext.TheinstallercontactsthespecifiedVirtualCenterserverandvalidates
theinformationyousupplied.
8 Selectasourceforthecertificateusedtoauthenticateserverconnections:
TohaveSRMcreateandinstallacertificate,selectAutomaticallygenerate
certificateandclickNext.
Entertextvaluesforyourorganizationandorganizationunit,typicallyyour
companynameandthenameofyourgroupwithinthecompany.The
maximumlengthofthecombinedvaluescannotexceed80characters.
TouseanexistingPKCS#12certificatefile,selectUseaPKCS#12certificate
fileandclickNext.
Enterthepathtothecertificatefile.Thecertificatefilemustfilecontainexactly
onecertificatewithexactlyoneprivatekeymatchingthecertificate.
Enterthecertificatepasswordifnecessary.
9 Enterthefollowingadditionalinformation:
LocalSiteNameAuniquenameforthisinstallationofSRM.Each
installationofSRMatasitemusthaveauniqueidentifier.
AdministratoremailTheemailaddressofthepersonorgroupwho
monitorsSRMandrespondstoalertsornotifications.
VMware, Inc. 29
Additionalemail(optional)Theemailaddressofanadditionalpersonor
groupwhoshouldreceiveanyalertsornotifications.
LocalHostThenameorIPaddressofthelocalhost.Thisvalueisobtained
bytheSRMinstallerandneedonlybechangedifitisincorrect(forexample,
ifthelocalhosthasmorethanonenetworkinterfaceandtheonedetectedby
theSRMinstallerisnottheoneyouwanttouse).
ListenerPortsTheSOAPandHTTPportnumbersfornetworktraffic.SOAP
isusedtoreceiverequestsfromSRM;HTTPisusedfordownloadingtheSRM
plugin.Defaultvaluesaresupplied.
APIListenerPortsTheSOAPandHTTPportnumbersfornetworktraffic
fromtheSRMAPI.Defaultvaluesareautomaticallysupplied.Formore
information,seetheSiteRecoveryManagerAPIdocumentation.
Defaultportvaluesworkwithoutmodificationaslongasthoseportsarenotbeing
usedbyotherapplicationsinthesystemwhereSRMisbeinginstalled.Youcan
modifythesevaluesifotherservicesarealreadyusingtheports,orifyournetwork
administratorpreferstoassignspecificportsforSRMtouse.
10 EnterthefollowingdatabaseconfigurationinformationandclickNext:
DatabaseClientClickthearrowontherightofthefieldandselectthe
databaseclientforyoursite.
DataSourceNameTheDSNyouwanttouseforthisinstallationofSRM.
ClickODBCDSNSetuptoviewexistingDSNsorcreateanewone.
UsernameAuserIDvalidforthespecifieddatabase.
PasswordThepasswordforthespecifieduserID.
ConnectionCountTheinitialconnectionpoolsize.Connectionsinthispool
arecreatedbytheSRMinstaller.Iftheseconnectionsareallinuseandanew
oneisneeded,itiscreatedifdoingsowouldnotcausethenumberof
connectionsspecifiedbyMaxConnectionstobeexceeded.ItisfasterforSRM
touseaconnectionfromthepoolthantocreateanewone.
MaxConnectionsThemaximumnumberofconnectionstoopentothe
databaseatonetime.Ifyourdatabaseadministratorhasrestrictedthenumber
ofconnectionsthatthedatabasecanhaveopen,thevalueyousupplyhere
mustnotexceedthatnumber.
11 ClickInstall.
12 Whenthewizardcompletes,clickFinish.
30 VMware, Inc.
Chapter 3 Installing or Updating Site Recovery Manager
Update Site Recovery Manager

WhenyouupdateSiteRecoveryManager,informationaboutVirtualCenterserver
connections,certificates,anddatabaseconfigurationisreadfromtheexisting
installationandreusedbythenewinstallation.
NOTEBeforeyoubegintheupdate,backupyourcurrentSRMdatabase.Theupdate
wizardrequiresyoutoverifythatthedatabaseisbackedup,andpausesuntilyou
confirmthatitis.
To update SRM
1 LogintotheSRMserverhost.
ToinstallSRM,youmustloginasamemberofthehostsAdministratorsgroup
2 DownloadtheSRMinstallationfiletoafolderonthehost,oropenafolderonthe
networkthatcontainsthisfile.
3 DoubleclicktheSRMinstallationfileicontobegintheupdate.
TheinstallerexaminesthesetofinstalledVMwaresoftwareonthehost.Ifitdetects
anexistinginstallationofSRM,itpromptsyoutoverifythatyouwanttoupdate
theexistinginstallation.
ClickYestocontinuewiththeupdate.
4 ClickNextontheWelcometotheupdatewizardpage.Thewizardpromptsyou
toverifythatyouhavebackeduptheSRMdatabase.
ClickNotopausetheinstallationwhileyoubackupthedatabase.
ClickYesifyouhavebackedupthedatabaseandwanttoproceedwiththe
installation.Theinstallerreadsconfigurationdatafromtheexisting
installationandusesittocompletetheupdate.
5 Whenthewizardcompletes,clickFinish.
YoumightbepromptedtoshutdownandrestartWindows.
Install the Site Recovery Manager Plug-In

AfteryouhaveinstalledorupdatedSRM,useaVIClienttoconnecttothe
VirtualCenterServerattheprotectedorrecoverysite,thendownloadthepluginfrom
theserverandenableitintheVIClient.
VMware, Inc. 31
To download and install the SRM plug-in
1 StartaVIClientandconnecttoaVirtualCenterServerattheprotectedor
recovery site.
2 OntheVIClientmenubar,selectPlugins>ManagePlugins.
3 OntheAvailabletab,locatetheVMwareVirtualCenterSiteRecoveryplugin
andclickDownloadandinstall.
4 Whenthedownloadcompletes,theplugininstallationwizardappears.Click
Nexttostartthewizard.
5 ClickIacceptthetermsinthelicenseagreement,andclickNext.
6 ClickInstall.
7 ClickFinish.
YoumightbepromptedtoshutdownandrestartWindows.
8 ClicktheInstalledtab.
9 ChecktheEnabledcheckboxfortheSiteRecoveryplugin.
TheSiteRecoveryiconappearsonthetoolbar.
Updating Database Credentials

Duringinstallation,SRMencryptsandstoresthedatabasecredentialsthatyouspecify.
Ifanyofthesecredentialschange(forexample,ifthedatabaseusernameorpassword
changes),youmustchangethestoredcredentialsbyrunningtheinstallcreds.exe
utilityfoundintheinstallationdirectory.
Reverting to a Previous Release

YoumustuninstallbothSRManditsdatabasewhenrevertingtoapreviousrelease.
To revert to a previous release
1 UninstallSRMattheprotectedandrecoverysites.
Wheresiteshavebeenpaired,SRMatbothsitesmustbeuninstalled.IfyouSRM
uninstallSRMfromonememberofapairofhosts,thedatabaseontheremaining
memberbecomesinconsistent.
2 UninstalltheSRMpluginfromaffectedVirtualCenterclients
3 Restorethedatabaseusedbythepreviousrelease,followingtheprocedures
documentedbyyourdatabasevendor.
32 VMware, Inc.
4
Managing SRM 4
ThischapterdescribestheVMwareInfrastructureClientandprovidesinformation
abouthowtousetheapplicationtomanageSRMandoperationssuchassitepairing,
managingusers,andaccessinglogfiles.
UsetheVIClienttoManageSRMonpage 33
ConnectingtheProtectedandRecoverySitesonpage 34
CredentialBasedAuthenticationonpage 35
CertificateBasedAuthenticationonpage 36
SRMUsers,Groups,Permissions,andRolesonpage 37
AccessSRMLogFilesonpage 42
Use the VI Client to Manage SRM

TheVIClientistheinterfacetoVirtualCenterServer.Whenyoulogin,onlythose
featuresandfunctionssupportedbythetypeofserveryouloggedontoappear.
After youinstalltheSRMplugin,theVIClientdisplayssiterecoveryoptions.
To log in to SRM from a VI Client session
1 UsingtheVIClient,logintotheprotectedsiteorrecoverysiteVirtualCenter
Server.
2 ClicktheSiteRecoveryicononthetoolbar.
VMware, Inc. 33
SiteRecoverycomponentsintheVIClientinclude:
InventoryLocatedontheleft,displaystheinventoryobjectsavailableforSRM,
includingprotectiongroupsandrecoveryplans.
SummarytabDisplaystherelevantinformationfortheprotectedsiteandthe
recoverysite.
SetuppaneDisplaystheoptionsusedtoconfiguresitefailover.
AlarmstabListstheconfiguredalarmsforSRM.
PermissionstabListstheusersandgroupsthathavepermissionsontheselected
objectandatwhatlevelthepermissionwasassigned.
Connecting the Protected and Recovery Sites

WhenyoustartusingSRM,establishasecureconnectionbetweentheprotectedsite
andtherecoverysite.UsetheVIClienttopairandmanagebothsites.Becausethe
VI ClientcanconnecttoonlyoneVirtualCenterServeratatime,launchoneVIClient
tomanageeachsite.Beforeyouconnecttotherecoverysite,youneedthefollowing:
TherecoverysiteVirtualCenterServernameorIPaddressandportnumber.
TheroleofProtectionSRMAdministratorontherecoverysiteifusing
credentialbasedauthentication.
Theadministratorloginfortheremoteserver.
ConnectionsbetweenSRMandeitherVirtualCenteroranotherinstanceofSRMmust
beauthenticated.Youcanuseadministrativecredentialsortrustedcertificatesto
authenticateconnections,butyoucannotmixauthenticationmethods.The
authenticationmethodyouchoosemustbeusedtosecuretheconnectionbetweenthe
VirtualCenterServerandSRMateachsite,andalsobetweentheSRMserversatthe
protectedandrecoverysites.Ifyouusetrustedcertificates,bothsitesmustusethesame
subjectname(composedfromtheorganizationandorganizationunitinformationyou
supplyduringinstallation)inthecertificate.
CredentialbasedUsesausernameandpassword.Theaccountmustbean
administratoraccount.TheprivilegesontheVirtualCenterServerspecifythese
credentials.SavethecredentialsyouspecifytocommunicatetotheVirtualCenter
Server.
CertificatebasedSpecifyacertificatethatwassignedbyatrustedcertificate
authority.Thecertificateismostcommonlysignedbyatrustedcertificate
authorityandinstalledintheVirtualCenterServerandSRMontheprotectedand
recoverysites.Thisconfigurationisthemostsecureconnection.
34 VMware, Inc.
Chapter 4 Managing SRM
Credential-Based Authentication
Byspecifyingautogeneratedcertificatesatinstallation,youareimplicitlyspecifying
credentialbasedauthentication.Inthiscase,theSRMserversavesthecredentials
specifiedduringinstallationtoauthenticateallsubsequentcommunicationwiththe
localVirtualCenterServer.WhenthisinstanceofSRMispairedtoaremoteSRMserver,
thecredentialsspecifiedaspartofthepairingprocessaresavedtoauthenticateall
subsequentcommunicationwiththeremoteSRMserver.
AllcommunicationwithSRMisprotectedusingSSLencryption,includingthetransfer
ofauthenticationcredentialstoVirtualCenterandSRMservers.
Pairing Sites with Credential-Based Authentication

Connectingprotectedandrecoverysitesusingautogeneratedcertificatesisthedefault
setupforconnectingprotectedandrecoverysites.
To connect to protected and recovery sites
1 UsingtheVIClient,logintotheprotectedsiteVirtualCenterServer.
3 IntheProtectionSetuppane,clickConfigure.
4 EntertheIPaddressorhostnameandportnumberfortheremoteVirtualCenter
ServerandclickNext.
CAUTIONWhenyouenterthehostnamefortheVirtualCenterServer,use
lowercase.TheVirtualCenterhostnamemustbeenteredexactlythesameway
(fullyqualifiedornot)duringpairingasitwasduringinstallation.
5 Accepttheremotesitecertificate.
ThiscertificatepromptappearswhentheSRMserverdoesnottrustthecertificate
fortheremoteVirtualCenterServer.
6 Entertheadministratorsusernameandpassword.
ThiscertificatepromptappearswhentheSRMserverdoesnottrustthecertificate
fortheremoteSRMserver.
8 VerifythateachstephasacheckmarkandclickFinish.
9 EntertheadministratorsusernameandpasswordfortheremoteVirtualCenter
Server.
VMware, Inc. 35
11 UsingtheVIClient,logintotherecoverysiteVirtualCenterServer.
ThissubmitstherequiredcredentialstologintotheremoteVirtualCenterServer.
TheProtectedSiteandRecoverySitepanesdisplaytheconnectioninformationaftera
successfulpairing.
Certificate-Based Authentication
Certificatebasedauthenticationrequirestheuseofcertificatessignedbyacommon
trustedcertificateauthorityonallserversinvolvedinyourSRMinstallation.This
includesbothVirtualCenterandSRMservers.Suchacertificatemaybereferredtoasa
trustedcertificate.
Byspecifyingatrustedcertificateatinstallation,youareimplicitlychoosingtouse
certificatebasedauthentication.Inthiscase,theSRMserverusesthecertificate
specifiedduringinstallationtoauthenticateallsubsequentcommunicationwiththe
localVirtualCenterServer.TheSRMserverdoesnotsavecredentialsspecifiedduring
theinitialinstallation.
Pairing Sites Using Certificate-Based Authentication

VMwarerecommendsthatyouusecertificatebasedauthentication.
To connect to protected and recovery sites
3 IntheSetuppane,clickConfigure.
4 EntertheIPaddressorhostnameandportnumberfortheremoteVirtualCenter
ServerandclickNext.
5 VerifythateachstephasacheckmarkandclickClose.
6 Fromtheprotectedsite,entertheremotecredentialsintheRemoteVirtualCenter
Serverdialogbox.
8 ClicktheSiteRecoveryicononthetoolbarandsubmittherequiredcredentialsto
completethepairing.
Theconnectioninformationappearsafterasuccessfulpairing.
36 VMware, Inc.
SRM Users, Groups, Permissions, and Roles

SRMusesthesameauthorizationmodelasVirtualCenterServer.Thesetofpermissions
appliedtoorinheritedbyanobjectdeterminetheoperationsthatareallowedonthe
objectandthelistofrolesthatcanperformthoseoperations.Managedobjectsinthe
SRMinventorycanhavespecificpermissionsapplied.Therearetwowaystocontrol
permissiontoexecuteSRMoperations:
AddingusersAssignuserstothepredefinedroles.
AddingrolesCreatearole,addtheadministrators,andthenaddtheright
permissionstotherole.
Tomanagepermissionsandroles,youmustlogintotheVirtualCenterServerwiththe
administratoraccount.
NOTEToconfigureSRM,ausermusthavebothVirtualCenterandSRMpermissions.
SRMrolessuchasSRMProtectionAdministratorandSRMRecoveryAdministratordo
nothavespecificprivilegesforVirtualCenterandthereforedonothaveadequate
permissionstoperformallSRMoperations.Theconverseisalsotrue.VirtualCenter
rolesdonotprovideanySRMprivileges.EnsurethatSRMusershaveVirtualCenter
andSRMspecificrolesasappropriate.
ThePermissionstabliststheusersandgroupsthathavepermissionsontheselected
objectandatwhatlevelthepermissionwasassigned.
YoumustbeinAdministrationviewfortheRolesmenuitemtobeenabled.
The Permissionstabdisplaysthefollowing:
User/GroupTheuserorgroupthatexistsinSRM.
RoleSetofprivilegesassignedtoanexistinguserorgroup.
DefinedinTheobjectinwhichtheuser,group,androleisdefined.
SRM Permissions
Toobtainthefullabilityofanadministratoroftheprotectedsiteandtherecoverysite,
definethefollowingpermissions:
Protectedsite:
ReadonlyattheVirtualCenterroot(donotpropagate).
ReadonlytoDatacenterinventoryobject(donotpropagate).
ProtectionVirtualMachineAdministratorroleattheVirtualMachinelevel
(propagate).
VMware, Inc. 37
ProtectionSRMAdministratorroleattheSRMSiteRecoveryrootlevel(donot
propagate).
ProtectionGroupsAdministratorroleattheSRMProtectionGroupslevel
(propagate).
Recoverysite:
RecoveryInventoryAdministratorroleattheVirtualCenterrootlevel(donot
propagate).
RecoveryDatacenterAdministratorroleattheVirtualCenterdatacenterlevel
(do notpropagate).
RecoveryHostAdministratorroleattheVirtualCenterhostlevel(donot
propagate).
RecoveryVirtualMachineAdministratorattheVirtualCenterresourcepooland
VirtualCenterfolderlevels(propagate).
RecoverySRMAdministratorattheSRMrootlevel(donotpropagate).
RecoveryPlansAdministratorattheSRMRecoveryPlanslevel(propagate).
SRM Default Roles

ThefollowingSRMspecificrolesaredefinedontheVirtualCenterServerduringSRM
installation:
ProtectionGroupsAdministratorSetupandmodifyprotectiongroups.
ProtectionSRMAdministratorPairtheprotectedandrecoverysites,and
configureinventorymappings.
ProtectionVirtualMachineAdministratorSetupandmodifytheprotection
characteristicsofaprotectedvirtualmachine.
RecoveryDatacenterAdministratorViewavailabledatastoresandperform
recoveryvirtualmachinecustomization.
RecoveryHostAdministratorConfigurevirtualmachinecomponentsduring
recovery.
RecoveryInventoryAdministratorViewcustomizationspecificationsforthe
recoverysite.
RecoveryPlansAdministratorReconfigureprotectionandrecoveryvirtual
machines.Alsograntstheabilitytosetupandrunrecovery.
38 VMware, Inc.
RecoverySRMAdministratorConfigureSANarraysandcreateprotection
profiles.
RecoveryVirtualMachineAdministratorCreaterecoveryvirtualmachinesand
addthemtotheresourcepool.Alsograntstheusertheabilitytoreconfigureand
customizetherecoveryvirtualmachineswhenarecoveryplanisrun.
TheVirtualCenterServerdefinesaReadOnlysystemrolethatcanbeusedtogrant
userstheabilitytoviewSRMproperties.Inaddition,theAdministratorrolecanbe
usedtograntuserscompletecontroloverboththeprotectionandrecovery
components.
Tosetuptheinventorymappings,aprotectedsiteusermustbeassignedthefollowing
roles:
ProtectionSRMAdministratorroleontheSRMrootobject.
ReadOnlyroleontheVirtualCenterobjectbeingmappedonboththeprimary
andtherecoverysites.
Add Roles
Someofthedefaultroles(suchasAdministrator)arepreconfiguredandcannotbe
changed.Ifyouhavesituationsthatrequireadifferentcombinationofaccessprivileges
thantheonessetup,createanadditionalroleormodifytheprovidedsamplerolesto
suityourneeds.
To add a role
1 LogintotheVIClientasauserwithAdministratorprivileges.
2 FromtheVIClient,clicktheAdministrationbuttoninthenavigationbar.
3 ClicktheRolestab.
4 ClickAddRole.
5 Typeanameforthenewrole.
6 Selecttheprivilegesforthenewroletohave(forexample,SiteRecovery)andclick
OK.Clicktheplus(+)signstoexpandthelists,asneeded.
Assign VirtualCenter Access Permissions

Assigntonewusersandgroupstherolesandpermissionstotherelevantinventory
objects.
VMware, Inc. 39
To assign a permission to a user or group
1 LogintotheVIClientasauserwithadministratorprivileges.
2 FromtheVIClient,clicktheInventorybuttoninthenavigationbar.
3 ClickthePermissionstab.
4 RightclickthePermissionstabandchooseAddPermission.
5 ClickAdd.
6 Identifytheuserorgroupthatisbeingassignedthisrole:
a FromtheDomaindropdownmenu,choosethedomainwheretheuseror
groupislocated.
b TypeanameintheSearchboxorselectanamefromtheNamelist.
Ifyouknowtheuserorgroupname,youcantypeitintheNamefield.
c ClickAddtoaddthenametotheUsersorGroupslist.
d RepeatStep athroughStep ctoaddadditionalusersorgroupsandclickOK

whenfinished.
7 Toapplythisroletoallchildobjectsoftheselectedinventoryobject,select
PropagatetoChildObjects.
8 Verifythattheusersandgroupsareassignedtotheappropriatepermissionsand
clickOK.
9 ClickOK.
Theserveraddsthepermissiontothelistofpermissionsfortheobject.
Add a New User Group and Role to SRM

AssigntonewusersandgroupstherolesandpermissionstotherelevantSRM
inventoryobjects.
To assign a user or group permission
1 LogintotheVIClientasauserwithAdministratorprivileges.
2 ClickSiteRecoveryinthenavigationbar.
Iftheprotectedandrecoverysitesarepaired,youmightneedtoenterlogin
informationfortherecoverysite.
3 ClickthePermissionstaboftheSRMInventoryobject.
40 VMware, Inc.
4 RightclickthePermissionstabandchooseAddPermission.
5 ClickAdd.
6 Identifytheuserorgroupthatisbeingassignedthisrole.
a FromtheDomaindropdownmenu,choosethedomainwheretheuseror
groupislocated.
b TypeanameintheSearchtextboxorselectanamefromtheNamelist.
c ClickAddtoaddthenametotheUsersorGroupslist.
d RepeatStep athroughStep ctoaddmoreusersorgroups.
e ClickOKwhenfinished.
7 IntheAssignedPermissionsdialogbox,selectarolefromtheAssignedRole
dropdownmenu.
Thismenudisplaysalltheavailablerolesthatarebeenassignedtothathost.
8 Toapplythisroletoallchildobjectsoftheselectedinventoryobject,select
PropagatetoChildObjects.
Performthistaskforeachuserorgroupadded.
9 ClickOK.
Theserveraddsthepermissiontothelistofpermissionsfortheobject.
Change Access Permissions

Youcanchangeaccesspermissionsforanyobjectinaninventory.
To change the permissions for a user or group
1 FromtheVIClient,clickanInventoryobject.
2 SelectanobjectandclickthePermissionstab.
3 Toselecttheuserorgroupandrolepairtochange,rightclicktheitem.
4 Toselecttheappropriaterolefortheuserorgroup,selectProperties.
5 SelectfromthedropdownmenuandclickOK.
6 Topropagatetheprivilegestothechildrenoftheassignedinventoryobject,click
thePropagatecheckbox.
VMware, Inc. 41
Remove Access Permissions

Removingapermissionforauser,grouporrolefromthelistofthoseavailableremoves
theuserorgroupandrolepairfromtheselectedinventoryobject.Itdoesnotremove
therolefromthelistofavailableitems.
To remove a permission role for a user or group
1 FromtheVIClient,selectanInventoryobject.
2 ClickthePermissionstab.
3 Toselecttheuserorgroupandrolepairtodelete,rightclickanitem.
4 SelectDelete.
TheVirtualCenterServerremovesthepermissionsetting.
Access SRM Log Files

YoucanretrieveSRMlogandconfigurationfilesfromtheserverandcollectthemina
compressed(zipped)folderonyourdesktop.
To retrieve log files when you are logged in to the SRM server host
ClickStart > Programs > VMware > VMware Site Recovery Manager >
Generate Site Recovery Manager log bundle.
Theindividuallogfilesarecollectedinafilenamed
srmsupportMMDDYYYYHHMM.zip,whereMMDDYYYYHHMMisastring
indicatingthemonth,day,year,hour,andminutewhenthelogfileswereretrieved.
To retrieve log files when you are logged in to the VI Client
1 StarttheWindowscommandprompt.
2 ChangedirectorytoC:\Program Files\VMware\VMware Site Recovery
Manager\bin.
3 Runthefollowingcommand:
C:\Program Files\VMware\VMware Site Recovery Manager\bin>cscript
srm-support.wsf
Theindividuallogfilesarecollectedinafilenamed
srm-plugin-support-MM-DD-YYYY-HH-MM.zip, whereMMDDYYYYHHMMis
astringindicatingthemonth,day,year,hour,andminutewhenthelogfileswere
retrieved.
42 VMware, Inc.
5
Protected Site
Configuration 5
ThischapterdescribesthestepsrequiredtoconfigureVMwareSiteRecovery
Manager (SRM)protectedsites,includingcreatingprotectiongroups,configuring
storagearraymanagers,inventorypreferences,andeditingvirtualmachinesettings.
ConfiguringtheProtectedSiteonpage 43
ConfigureArrayManagersonpage 44
RepairArrayManagersonpage 46
ConfigureInventoryPreferencesonpage 47
CreateaProtectionGrouponpage 48
ConfiguringVirtualMachinePropertiesonpage 49
AddMessageandCommandStepsonpage 52
IPAddressMappingonpage 53
Configuring the Protected Site

Configuringprotectionattheprotectedsiteincludesthefollowingsteps:
1 Installthestoragereplicationadapters.
Consultthedocumentationfromyourstoragevendorifyouneedassistance.You
mustaddthenecessaryarrayscriptsandrestarttheSRMservicebeforeyou
configurearraymanagers.
2 ConfigurethearraymanagerstoallowSRMtodiscoverreplicatedLUNsand
createdatastoregroups.
VMware, Inc. 43
3 Configureinventorypreferencestosettheglobalmappingsforallprotection
groupstoinherit.
4 Createprotectiongroupsthatdefinevirtualmachinesthatfailovertogether.
5 Configureindividualvirtualmachinesandsetthedefaultstoinheritfrom
inventorymappingsandthesettingsontheirprotectiongroup.
Requirements for VMware Infrastructure Configuration

Beforeyouconfigurearraymanagers,youneedthefollowingVMwareInfrastructure
configuration:
Adatacenterontheprotectedandrecoverysites.
ESXhostsattheprotectedandrecoverysites.
Ifyouneedtosupportuseofcertaintypesofsnapshotsattherecoverysite
(snapshotstakenwhenthevirtualmachineispoweredonorsuspended),theESX
hostsatbothsitesmusthavecompatibleCPUs,asdefinedintheVMware
knowledgebasearticlesVMotionCPUCompatibilityRequirementsforIntelProcessors
(article1991)andVMotionCPUCompatibilityRequirementsforAMDProcessors
(article1992).ThehostsmustalsohavethesameBIOSfeaturesenabled.Ifthe
serversBIOSconfigurationsdonotmatch,theystillshowacompatibilityerror
messageeveniftheyareotherwiseidentical.Thetwomostcommonfeaturesto
checkareNonExecuteMemoryProtection(NX/XD)andVirtualization
Technology(VT/AMDV).
Virtualmachinestobeprotectedontheprotectedsite.
Forinformationaboutconfiguringdatacenters,hosts,andresourcepools,seethe
VMwareInfrastructureServerConfigurationGuide.
Configure Array Managers

Aftertheprotectedandrecoverysitesareconnectedtoeachother,configurethearray
managerssothatSRMcanidentifyavailablearraysandreplicatedLUNs.Array
managersusestoragereplicationadapters,whicharesuppliedbyarrayvendors.When
youconfigurearraymanagers,yousupplyinformationaboutthearraysthatyouwant
touse.SRMusesthisinformationtodiscoverthearraysavailabletotheSRMserverand
thereplicatedLUNsthattheysupport.Formoreinformation,seeArrayBased
Replicationonpage 13.
44 VMware, Inc.
Chapter 5 Protected Site Configuration
Beforeyoucanconfigureanarraymanager,thestoragereplicationadapterforthe
managermustbeinstalledontheSRMserverhost.Youmustalsohavedocumentation
fromthearrayvendorthatprovidestheinformationyouneedtosupplywhen
configuringanarraymanager.
SRMrescansarraysevery24hourstodetectanyLUNsthathavebeenaddedor
removed.Afteryouconfigurethearraymanagersforasite,youtypicallydonothave
toreconfigurethemunlesschangeanyoftheinformation,suchasIPaddressor
administrativecredentials,thatthearraymanagersrequire,oryouaddorremovea
LUNandwanttheSRMtorecognizethechangebeforethenextscheduledrescan.
Toconfigurearraymanagers,thefollowingconditionsmustbeinplace:
TheVIClientmustbeconnectedtotheprotectedsite.
TheroleofProtectionSRMAdministrator.
To configure array managers
1 UsingaVIClient,logintotheprotectedsiteVirtualCenterServer.
2 ClickSiteRecoveryontheVIClienttoolbar.
3 Youarepromptedtoprovideausernameandpasswordthatarevalidatthe
recoverysite.
4 OntheSummarypageoftheSiteRecoveryfor<protectedsitehostname>
window,findtheArrayManagerslineunderProtectionSetup.ClickConfigure
toopentheConfigureArrayManagerswizard.
5 ClickAddtoopentheAddArrayManagerwindow.
6 IntheAddArrayManagerwindow,providetheinformationSRMrequiresto
connectwithastoragearray:
Typeadisplaynameforthearraymanager.Useanydescriptivenamethat
makesiteasyforyoutoidentifythearraysthatthisarraymanagermanages.
SelectastoragereplicationadapterfromtheManagerTypelist.Ifthe
managertypethatyouwanttousedoesnotappearinthelist,thestorage
replicationadapterthatsupportsithasnotbeeninstalledontheSRMhost.
Afteryouselectamanagertype,theAddArrayManagerwindowchangesto
includefieldsfortheinformationrequiredbythatmanagertype.Formore
informationaboutthevaluesforthesefields,seethedocumentationfromthe
storagearrayvendor.
VMware, Inc. 45
7 ClickConnecttovalidatetheinformationyousuppliedandreturnthelistofarrays
thatthearraymanagersupports.
Allsupportedarraysareselected.Cleartheselectionofanyarraythatyoudonot
wantSRMtouse.
8 ClickOKwhenyoufinishselectingthestoragearraysthatyouwantSRMtouse.
ThearraymanagerqueriestheselectedarraystodiscoverwhichoftheirLUNsare
replicated.Detailedinformationabouttheselectedarraysandthenumberof
replicatedLUNstheysupportappearsintheReplicatedArrayPairsareaofthe
ConfigureArrayManagerswindow.
9 ClickNexttoconfigurestoragearraysattherecoverysite.
Theprocedureforaddingthesearraysisthesameastheoneforaddingarraysat
theprotectedsite,showninStep 5throughStep 7.Whenyoufinishaddingstorage
arraysattherecoverysite,SRMverifiesthatitcancommunicatewithboth
membersofeacharraypairanddisplaysagreencheckmarkiconintheArrayID
columnoftheReplicatedArrayPairsareaoftheConfigureArrayManagers
window.Ifthegreencheckmarkisnotdisplayed,someoftheinformationyou
suppliedintheAddArrayManagerwindowmightneedtoberevised.
10 ClickNexttodisplaytheReviewReplicatedDatastorespage.
ReviewthetreetoensurethatthecorrectdatastoregroupsandreplicatedLUNs
arelisted.Onlyreplicateddatastoreswithregisteredvirtualmachinesappearon
thispage.
11 ClickFinishwhenyouaresatisfiedthatthearraymanagersareconfigured
properly.
Repair Array Managers

Ifyouneedtoeditarraymanagerdetailswhentheprotectedsiteisnotaccessible,use
theRepairArrayManagersfunction.Iftheprotectedsiteisaccessible,youcan
accomplishthesamethingbyfollowingtheproceduresinConfigureArray
Managersonpage 44.
Torepairarraymanagers,thefollowingconditionsmustbeinplace:
TheVIClientmustbeconnectedtotherecoverysite.
TheroleofRecoverySRMAdministrator.
46 VMware, Inc.
To repair array managers
1 IntheInventory,clickRecoveryPlans.
2 IntheCommandsareaoftheSummarytab,clickRepairArrayManagers.
This openstheRecoverySiteArrayManagerspageoftheConfigureArray
Managerswindow.UsetheAdd,Remove,orEditbuttonstomodifyarray
managerinformationfortherecoverysite.
Configure Inventory Preferences

Inventorypreferencesprovidemappingsbetweencomputeresources,virtualmachine
folders,andnetworksontheprotectedsiteandtheircounterpartsontherecoverysite.
Thesemappingsaresupersededbyanyvaluesspecifiedinindividualprotectedvirtual
machines.Beforeyoumap,determinewhichcomputeresources,virtualmachine
folders,andnetworksontheprotectedsiteyouwantassociatedtotherecoverysite.
Createcorrespondingcomputeresources,virtualmachinefolders,andnetworksatthe
recoverysite.
Mappingresourcesisoptional.Mapsprovidedefaultlocationsandnetworksforthe
replicatedvirtualmachinesontherecoverysite.Ifyoucreateaprotectiongroupandno
mapsexist,youmustconfigureeachprotectedvirtualmachineindividually.
Toconfigureinventorypreferences,thefollowingconditionsmustbeinplace:
TheroleofProtectionSRMAdministrator.
To configure inventory preferences
3 ClicktheInventoryMappingstab.
4 ClickConfigure.
5 SelectthenetworktomaptotherecoverysiteandclickConfigure.
6 Expandthetree,selectthedesirednetworkandclickOK.
7 ClickConfigure.
8 FromtheInventoryMappingstab,selectComputeResourcestomaptothe
recoverysiteandclickConfigure.
9 SelectthecomputeresourcesthatyoucreatedattherecoverysiteandclickOK.
VMware, Inc. 47
10 ClickConfigure.
11 Selectavirtualmachinefoldertomaptotherecoverysite.
12 Selectthevirtualmachinefolderthatyoucreatedattherecoverysiteforthisvirtual
machinefolderandclickOK.
Create a Protection Group

Aprotectiongroupisagroupofvirtualmachinesthatfailovertogetherattherecovery
siteduringtestandrecovery.Whenyoucreateaprotectiongroup,SRMcreatesa
placeholdervirtualmachineattherecoverysiteforeveryvirtualmachineinthe
protectiongroup.Youcannotpowerontheseplaceholdervirtualmachines,butyoucan
configurethemandmovethemwithintheinventory.
Aprotectiongroupprotectsonedatastoregroup.Thevirtualmachinesinthegroup
sharecertaincommoncharacteristics.Youcanprotectadditionalvirtualmachinesby
configuringthemandaddingthemtoaprotectiongroup.Datamovementtothe
recoverysiteisdelegatedtothereplicationprovidersspecifiedwhenyoucreatethe
groups.
Becauseaprotectiongroupisscopedtoadatastoregroup,useofStorageVMotionto
moveavirtualmachinesstoragecanremovethevirtualmachinefromtheprotection
groupifitsstorageismovedtoadifferentdatastore.
NOTEBecausesomeoperatingsystemscachefilesystemwrites,somefilesonthe
underlyingreplicatedstorageforarunningvirtualmachinemaynotbeuptodate
whenreplicated.Whenthishappens,therecoveredvirtualmachinepowersonusing
theresultsofthemostrecentreplication,whichmaynotincludeallchangestofiles
stateontheprotectedvirtualmachine.
Aprotectiongroupcanbepresentinoneormorerecoveryplans.
Tocreateaprotectiongroup,thefollowingconditionsmustbeinplace:
TheroleofProtectionGroupAdministrator.
Fullyconfiguredarraymanagers.
To create a protection group
3 ClickProtectionGroupsintheinventorylist.
48 VMware, Inc.
4 IntheCommandspaneontheSummarytab,clickCreateProtectionGroup.
5 IntheProtectionGroupNamefield,enteranameforthegroup.
6 ClickNext.
7 Selectthedatastoregrouptoaddtotheprotectiongroup.
Onlyonedatastoregroupcanbeassociatedwiththeprotectiongroup.
The associationcannotbemodifiedlater.
8 ClickNext.
9 Selectarecoverysitedatastoreinwhichtostorethefilesforthevirtualmachines
inthisprotectiongroup.
Thedatastorestoresmetadataforthevirtualmachineandnotthe.vmdkfileor
files.Themetadataconsistsof.vmsd,.vmxand.vmxffilesandiswrittentothe
datastoretoallowthevirtualmachinestobeaddedtotheVirtualCenterinventory
attherecoverysite.
Wheninventorymappingsaredefinedforvirtualmachinesintheselected
datastoregroup,SRMstartsprotectingthosevirtualmachines.Iftheyarenot
defined,anemptyprotectiongroupiscreatedandthevirtualmachinesstatusis
NotConfigured.
10 ClickFinish.
YourprotectiongroupisaddedtoProtectionGroupsintheinventory.
VirtualmachineconfigurationisdoneontheprotectiongroupsVirtualMachinestab.
Formoreinformation,seeConfiguringVirtualMachinePropertiesonpage 49.
Configuring Virtual Machine Properties

SRMcreatesplaceholdervirtualmachinesintherecoverysiteinventory.Eachofthese
placeholdersrepresentsavirtualmachineattheprotectedsite,andprovidesan
inventoryentryattherecoverysiteforthatvirtualmachine.
Propertycustomizationsforprotectedvirtualmachinesarerecoverysiteobjects,and
mustbeconfiguredwhileyouareconnectedtotherecoverysite.Resourcesettingsof
protectedvirtualmachinesarenotreplicated,becausetheyusearbitraryunitswhich
mayhavenomeaningattherecoverysite.
VMware, Inc. 49
UsetheVirtualMachinePropertieswizardtoperformthefollowingtasks:
Addunconfiguredvirtualmachinesfromtheprotectiongroupvirtualmachine
list.
Editvirtualmachineslistedinaprotectionorrecoverygroup.
YoucanconfigureandeditavirtualmachinefromtheVirtualMachinestabifa
protectiongroupalreadyexists.
Toconfigurevirtualmachinesontherecoverysite,seeConfigureVirtualMachinesin
aRecoveryPlanonpage 65.
Configure Properties for Protected Virtual Machines

Propertiesforprotectedvirtualmachinesareinitiallyderivedfromtheinventory
preferencesyouspecifiedforthemachinesprotectiongroup.Ifyoudidnotspecify
inventorypreferencesoryouneedtoreconfigureavirtualmachine,youcandosoin
thefollowingways:
FromtheConfigurevirtualmachinespageavailablewhenyoucreateaprotection
group.
FromtheVirtualMachinestabifaprotectiongroupalreadyexists.
Toconfigurevirtualmachineprotectionproperties,thefollowingconditionsmustbein
place:
TheroleofProtectionVirtualMachineAdministrator.
To configure all virtual machines in a protection group
3 SelectaprotectiongroupintheInventorylist.
4 OntheVirtualMachinestab,clickConfigureAll.
Thisactionappliesexistinginventorymappingstoallvirtualmachinesthathave
astatusofNotConfigured.Afterthisprocesscompletes,anyvirtualmachinesthat
couldnotbeautomaticallyconfiguredhaveastatusofMappingMissingor
MappingInvalid.Youmustconfigurethesemachinesindividually,asdescribedin
Toconfigureindividualvirtualmachinepropertiesonpage 51.
50 VMware, Inc.
To configure individual virtual machine properties
3 SelectaprotectiongroupintheInventorylist.
4 OntheVirtualMachinestab,selectamachinetoconfigureandclickConfigure
Protection.
5 SelecttheVirtualMachinefoldertolocateyourvirtualmachineontherecovery
siteandclickNext.
6 Selectthehostonwhichyouwanttomanagethevirtualmachinesontherecovery
siteandclickNext.
7 Selecttheresourcepoolattherecoverysitetolocateyourvirtualmachineandclick
Next.
8 ClickthecomponentlevelprotectiontouseforthisvirtualmachineandclickNext.
SRMcannotprotectavirtualmachineifitcannotaccessattacheddevices,suchas
virtualdisks,floppydisks,orISOimages.Eitherthevirtualmachineoperates
withoutthedevice,orthedeviceiscopiedtothedatastorewherethevirtual
machinecanattachtothedeviceduringfailover.
9 ClickthedatastoretostoretherecoveryvirtualmachinefilesandclickNext.
TheSpecifyaCustomizationSpecificationforthisVMscreenappears.A
customizationspecificationallowsyoutomodifynetworkinginformation,suchas
IPaddressorthenetworkmask,fortherecoveredvirtualmachine.Noother
virtualmachinepropertiescanbecustomized.
10 ClickBrowsetoviewtheavailablecustomizationspecificationsonthe
CustomizationSpecificationpage.
11 SelecttoapplytothevirtualmachineandclickOK.
ThedescriptionofthespecifiedcustomizationoptionappearsintheDescription
fieldontheSpecifyaCustomizationSpecificationforthisVMscreen.
Toconfigurethisoption,acustomizationspecificationmustbecreatedusingthe
VIClientontherecoverysite.Ifnospecificationsareconfigured,themessageNo
availableCustomizationSpecificationfoundappears.Ifavirtualmachinewitha
customizationspecificationdoesnothaveanoperatingsystem,thecustomization
scriptstepfailsduringarecoverytestorfailover.
SeeWorkwithCustomizationSpecificationsonpage 67.
VMware, Inc. 51
12 ClickNext.
13 SelecttherecoverypriorityfromthedropdownmenuandclickNext.
HighStartsthevirtualmachineinserialorder.
NormalandlowStartsthevirtualmachineinparallelwithothervirtual
machinesonthisESXhost.
14 ClickNext.
Adduserdefinedmessagesandcommandsstepstobeperformedbeforethis
virtualmachineispoweredon.Theseuserdesignedmessagesandcommandscan
beremovedandreordered(seeAddMessageandCommandStepsonpage 52).
15 ClickFinish.
Add Message and Command Steps

Youcanaddmessagesorcommandstoyourrecoveryplanoneithertheprotectedor
therecoverysiteasyouconfigurevirtualmachineproperties.Youcanaddmessageor
commandstepsbeforeorafteryoupoweron.
Messagestepsdisplayinformationintextformat.Whenarecoveryplanisrunningand
encountersamessagestep,therecoverypausesuntilyouacknowledgethetextofthe
message.Theplanthencontinuestorun.
Commandstepsarelivescriptsthatyoucaninsertintherecoveryplanalongwiththe
defaultstepsthatSiteRecoveryManagerprovides.Astherecoveryplanisrunningand
encountersacommandstep,thescriptruns.
Toaddmessageandcommandsteps,thefollowingconditionsmustbeinplace:
TheVIClientmustbeconnectedtoeithertheprotectedorrecoverysite.
TheroleofRecoveryVirtualMachineAdministratorroleorRecoveryPlans
Administrator.
Run Batch Files or Commands

TorunaWindowsbatchfileorcommand,starttheWindowscommandshellusingits
fullpath.Forexample,torunascriptlocatedinc:\alarmscript.bat,usethe
followingcommandline:
c:\windows\system32\cmd.exe /c c:\alarmscript.bat
52 VMware, Inc.
Whenyouaddbatchfilesorcommandstoarecoveryplan,beawareofthefollowing
requirements:
ScriptsmustresideonthehostwheretheSRMserverisinstalled.
SRMcalloutstobatchfilesorcommandsrunasthelocaladministratoroftheSRM
serverhost,andnotastheuserloggedintotheVIClient.
BatchfilesorcommandsthatproduceoutputthatcontainscharacterswithASCII
valuesgreaterthan127mustdosousingUTF8encoding.
Onlythelast4KBofscriptoutputiscapturedinlogfilesandrecoveryhistory.
Scriptsthatproducemoreoutputcanredirecttheiroutputtoafile,ratherthan
sendingittothestandardoutputtobelogged.
Arecoveryterminatesifacommandorscriptexitswithanonzerostatus.Some
commandsexitwithanonzerostatusevenwhentheyaresuccessful.Toforcea
commandtoexitwithastatusof0,append|| exit 0 toit,asinthisexample:
c:\windows\system32\cmd.exe /C chkdsk || exit 0
Change the Command-Line Time-Out on ESX Hosts

Bydefault,SRMterminatescalloutscriptsthattakemorethan300secondstocomplete.
Youmaywanttoincreasethetimeoutvalueifyourscriptstypicallyrunlonger.
To changethecommandlinetimeout,editthevmware-dr.xmlconfigurationfileand
changethevalueofthe calloutCommandLineTimeoutparametertospecifyanew
timeoutvalueinseconds.
Changing the SRM Power State Time-Out

Bydefault,SRMreportsanerrorifarequesttochangethepowerstateofavirtual
machine(powerdown,forexample)doesnotcompletewithin120seconds.Tochange
thepowerstatetimeout,editthevmware-dr.xmlconfigurationfileandchangethe
valueofthe powerStateChangeTimeoutparametertospecifyanewtimeoutvaluein
seconds.
IP Address Mapping
TheSRMIPaddressmapreportergeneratesanXMLdocumentdescribingthenetwork
structureoftheprotectedandrecoverysites.Itgivesnetworkadministratorsaviewof
howthenetworksatthetwositesrelatetoeachotherandisusedtodeterminewhich
networksandIPaddressesareavailableforusebyvirtualmachinesattherecoverysite.
VMware, Inc. 53
TheSRMIPaddressmapreporterusesinformationintheSRMserverconfigurationfile
toconnecttoVirtualCenterandSRM.Theconfigurationfileforeithertheprotectedor
recoverysitecanbeused.Thereporterconnectstothesitedefinedinthefileand
queriesboththatsiteandthepairedsite.Theutilitygeneratesafulllistofmappings
groupedfirstbysiteandthenbyrecoveryplan.
Youcanrunthetoolagainsttherecoverysitesconfigurationfileusingacommandof
theform:
dr-ip-reporter.exe -cfg <DR server configuration XML> -out <Output XML

filepath> [-plan <Recovery plan name>] [-i]
Specify-plan <Recovery plan name> tolookupaparticularrecoveryplan.
Specify-i toturnoffthumbprintconfirmationprompts.
To report mappings for all recovery plans

Manager\bin.
C:\Program Files\VMware\VMware Site Recovery Manager\bin>dr-ip-reporter.exe
-cfg ..\config\vmware-dr.xml -out c:\tmp\report.xml
To report mappings for a particular recovery plan

Manager\bin.
C:\Program Files\VMware\VMware Site Recovery Manager\bin>dr-ip-reporter.exe
-cfg ..\config\vmware-dr.xml -out c:\tmp\report.xml -plan Plan-B
Batch IP Property Customization

SRMincludesatoolthatallowsyoutospecifyIPproperties(networksettings)forany
orallofthevirtualmachinesinarecoveryplanbyeditingacommaseparatedvalue(CSV)
filethatthetoolgenerates.Initially,thisfileincludesasinglerowforeachplaceholder
virtualmachineintheplan.Youcaneditthefiletoaddarowforeachnetworkadapter
ineachplaceholdervirtualmachineandthencustomizethenetworksettingsforeach
adapter.Whenyouarefinished,youusetheeditedfileasinputtoacommandthat
createscustomizationspecificationsfortheplaceholdervirtualmachines.
54 VMware, Inc.
To generate the CSV file

Manager\bin.
C:\Program Files\VMware\VMware Site Recovery Manager\bin>dr-ip-customizer.exe
-cfg ..\config\vmware-dr.xml -csv c:\tmp\example.csv -cmd generate
InanSRMrecoveryplanconfigurationthatdefinesthreeplaceholdervirtualmachines,
thegeneratedfilelookslikethis:
VM ID,VM Name,Adapter ID,MAC Address,DNS Domain,Net BIOS,Primary
WINS,Secondary WINS,IP Address,Subnet Mask,Gateway(s),DNS Server(s), DNS
Suffix(es)
shdw3,srm3,0,,,,,,,,,,
shdw2,srm2,0,,,,,,,,,,
shdw1,srm1,0,,,,,,,,,,
Thefileconsistsofaheaderrowthatdefinesthemeaningofeachcolumn,andasingle
rowforeachplaceholdervirtualmachinefoundintherecoveryplan.Theonlycolumns
populatedwithvaluesare:
VMID(theIDfortheplaceholdervirtualmachine)
VMName(thehostnameoftheplaceholdervirtualmachine)
AdapterID(always0,whichdesignatesglobalIPsettings,notspecifictoany
adapter)
Editing the CSV file to customize IP properties
ThetableinExample 51showstheresultofopeningtheoutputofdr-ip-customizer
withaspreadsheetprogramandcreatingadditionalrowsthatdefinenetworksettings
forplaceholdervirtualmachinesintherecoveryplan.
Example 5-1.
VM Adapter DNS Primary Secon- Subnet DNS DNS
VM ID Name ID MAC Address Domain NetBIOS WINS dary WINS IP Address Mask Gateway(s) Server(s) Suffix(es)
shdw1 srm1 0 10.10.10.1 example.com
shdw1 1 00-1f-3a-38-29-9cexample.com dhcp
shdw2 srm2 0
shdw2 1 00-1f-3a-38-29-9cexample.com 10.10.10.10 10.13.99.5 255.255.0.0 10.10.10.10010.10.10.1
shdw2 1 10.10.10.2
shdw3 srm3 0
VMware, Inc. 55
Example 5-1.
VM Adapter DNS Primary Secon- Subnet DNS DNS
VM ID Name ID MAC Address Domain NetBIOS WINS dary WINS IP Address Mask Gateway(s) Server(s) Suffix(es)
shdw1 srm1 0 10.10.10.1 example.com
shdw1 1 00-1f-3a-38-29-9cexample.com dhcp
shdw2 srm2 0
shdw2 1 00-1f-3a-38-29-9cexample.com 10.10.10.10 10.13.99.5 255.255.0.0 10.10.10.10010.10.10.1
shdw2 1 10.10.10.2
shdw2 1 00-1a-3f-b8-f3-79 example.com 10.10.10.10 10.13.99.22 255.255.0.0 10.10.10.10010.10.10.1
shdw3 1 10.10.10.2
ThefollowingrulesapplywhenyoumodifyaCSVfilecreatedbythe
dr-ip-customizerutility.
TheMACAddressfieldisprovidedonlytodifferentiateadaptersonthesame
virtualmachine.Itshouldbeconsideredreadonly.AnymodificationoftheMAC
addresswillinvalidatethevirtualmachineconfigurationwhenthecustomization
isapplied.
TheVMNamefieldisintendedasareferencefortheusercustomizingthefile.It is
populatedwhentheCSVfileiscreatedbutignoredwhenthemodificationsare
appliedtotherecoveryplan.
TheonlyfieldsthatyoucanmodifyforarowwhereAdapterIDis0areDNS
Server(s)andDNSSuffix(es).Thesevalues,ifspecified,areinheritedbyallother
adaptersforthatVMID.
Todefinepropertiesforaspecificadapteronaplaceholdervirtualmachine,create
anewrowthatcontainsthatvirtualmachinesIDintheVMIDcolumnandthe
adapterID(thevirtualPCIslotinwhichtheadapterisinstalledontheplaceholder
virtualmachine)intheAdapterIDcolumn,thenspecifyvaluesfortheother
columns.
Tospecifymorethanonevalueforacolumn,createanadditionalrowforthat
adapterandincludethevalueinthecolumninthatrow.InExample 51,additional
rowsdefineasecondaryDNSserverfortheplaceholdervirtualmachinesshdw2
andshdw3.
TocreateaplaceholdervirtualmachineasaDHCPclient,enterdhcpinthe
IP Addressfield,asshowninthesecondrowofExample 51.
56 VMware, Inc.
ForanynonzeroadapterIDthatisnotaDHCPclient:
YoumustspecifyvaluesforIPAddress,SubnetMask,Gateway(s),andDNS
Server(s)unlessglobalvaluesforthesepropertiesexist(intherowforAdapter
IDzeroforthatVMID).Globalvalues,ifspecified,areoverriddenbyvalues
youspecifyforeachnonzeroadapterID.
TheNetBIOScolumn,ifnotleftempty,mustcontainoneofthefollowing
strings:
disableNetBIOS
enableNetBIOS
enableNetBIOSViaDhcp
TheMACAddresscolumnmustcontaintheMACaddressfortheadapter
specifiedintheAdapterIDcolumn,writtenaspairsofhexadecimaldigits
separatedbythedashorcoloncharacter.Charactercaseisnotconsidered.
Ifyouenteracommaintoanycolumn,anerroroccurswhenyouapplythe
customizedIPproperties.
To apply customized IP properties

Manager\bin.
-cfg ..\config\vmware-dr.xml -csv c:\tmp\example.csv -cmd create
To reset or undo customized IP properties

Manager\bin.
-cfg ..\config\vmware-dr.xml -csv c:\tmp\example.csv -cmd drop
VMware, Inc. 57
To update customized IP properties
1 EdittheCSVfiletomodifythepropertiesthatyouwanttochange.

Manager\bin.
-cfg ..\config\vmware-dr.xml -csv c:\tmp\example.csv -cmd recreate
58 VMware, Inc.
6
Recovery Site Configuration 6

Arecoveryplanisalistofstepsforswitchingoperationofyourdatacenterfromthe
protectedsitetotherecoverysite.Thischapterdescribesthestepsrequiredtocreate
andmodifyrecoveryplans.
Configuringprotectionattherecoverysiteincludesthefollowingtasks:
Createarecoveryplan.
Chooseprotectiongroupstorecoverintherecoveryplan.
SRMpopulatestherecoveryplanwithappropriaterecoverysteps.Customizethe
recoveryplanasneeded.
CreateaRecoveryPlanonpage 60
ManagingRecoveryPlansonpage 61
TestaRecoveryPlanonpage 63
RunaRecoveryPlanonpage 64
ConfigureVirtualMachinesinaRecoveryPlanonpage 65
WorkwithCustomizationSpecificationsonpage 67
VMware, Inc. 59
Create a Recovery Plan

RecoveryplansarecreatedwithaRecoveryPlanwizardthatpromptsyouforaplan
nameandtheprotectiongroupstoincludeintheplan.WithSRMrecoveryplans,
you can:
Createmorethanonerecoveryplan.Forexample,youcanspecifyoneplanfor
wholesitefailures,othersforlarge,partialfailures,oryoumaywantonerecovery
planforeachbusinessunit.
Includethesameprotectiongroupinmorethanonerecoveryplan.
Createemptyrecoveryplansfortesting.
Formoreinformation,seeCreateaProtectionGrouponpage 48.
Duringrecoveryplancreation,youchoosewhichvirtualmachinestosuspendduring
recovery.Thevirtualmachinesthataresuspendedarethelocalvirtualmachinesthat
runontherecoveryhost.SuspendingnoncriticalresourcessavesspaceandfreesCPU
andmemoryresourcesonhosts.
Themachinesthatarepoweredonarethemachinesthatarebeingfailedover.When
therecoveryruns,thevirtualmachinespowerondependingontheresponsetimesset
intheplan.VirtualmachinescanbecategorizedasHigh,Normal,Low,orNoPower
Onsothattheystartinthecorrectorderwhentheplanruns.
Tocreatearecoveryplan,thefollowingconditionsmustbeinplace:
TheroleofRecoveryPlansAdministrator.
To create a recovery plan
3 ClickRecoveryPlansintheInventorylist.
4 IntheCommandspaneontheSummarytab,clickCreateRecoveryPlan.
5 EnteranameandanoptionaldescriptionfortherecoveryplanandclickNext.
6 SelecttheprotectiongroupstoincludeintheplanandclickNext.
Youcanincludeoneormoreprotectiongroupsinarecoveryplan.
60 VMware, Inc.
Chapter 6 Recovery Site Configuration
7 Settheresponsetimesforthevirtualmachinesintheplan(responsescannotbe
detectedonvirtualmachinesthatdonothaveVMwareToolsinstalled).
ChangeNetworkSettings:Ifthevirtualmachinedoesnotacquirethe
expectedIPaddresswithinthespecifiedintervalafterarecoverystepthat
changesnetworksettings,anerrorisreportedandtherecoveryplanproceeds
tothenextvirtualmachine.
WaitforOSHeartbeat:IfthevirtualmachinedoesnotreportanOSheartbeat
withinthespecifiedintervalafterbeingpoweredon,anerrorisreportedand
therecoveryplanproceedstothenextvirtualmachine.
8 ClickNext.
9 Selectthenetworktouseduringrecoveryplantests,orselectAutotocreatean
isolatednetworkfromtheTestNetworkdropdownmenu.
IftherecoveryplanincludesvirtualmachinesthatrunLinuxandareDHCP
clients,besurethatthetestnetworkincludesaDHCPserver.
IfyourVIclusterattherecoverysiteusesVMwareHA,youmustcreateanduse
useatestVLANthatspansESXhosts.HAclustersdonotworkcorrectlyonother
testnetworkconfigurations.
10 ClickNext.
11 ExpandVirtualMachinesandtheDatacenter.
12 Selectthelocalvirtualmachinestosuspendwhentheplanistestedorrun,and
clickFinish.
Managing Recovery Plans

Whenyouselectarecoveryplaninthenavigationpane,yourrecoveryplandetails
appearinthemainviewingareaofthepage.Thefollowingtabsappearonthepage:
SummaryProvidesasummaryoftherecoveryplan,includingname,
description,andcommandsyoucanrunfortheplan,suchaseditingortestingthe
plan.Thesummarytabisthedefault.
VirtualMachinesDisplaysthevirtualmachinesthatthisrecoveryplanprotects.
RecoveryStepsListsthestepsoftherecoveryplan.
HistoryDisplayswhethertherecoveryplanwasrun,thedatewhenitran,the
durationoftherun,thestatus,andtheresultsoftheplan.Providesanoptionto
exportacopyoftheresultsinXML,HTML,orCSVformats.
PermissionsListstheuserswhoareauthorizedtomaintaintherecoveryplan.
VMware, Inc. 61
Whenyouselectarecoveryplaninthenavigationpane,thefollowingcommands
appearontheSummarytab:
EditRecoveryPlanModifytheplannameanddescription,protectiongroups
thatareincludedintheplan,virtualmachineresponsetimes,networktouse
duringplantesting,andlocalmachinestobesuspendedaspartoftherecovery
plan.
RemoveRecoveryPlanDeletetherecoveryplan.
TestRecoveryPlanRunatestoftherecoveryplan.
RunRecoveryPlanRuntherecoveryplan.
Edit a Recovery Plan

Youcanmodifytheplannameanddescription,protectiongroupsthatareincludedin
theplan,virtualmachineresponsetimes,networktouseduringplantesting,local
machinestobesuspendedaspartoftherecoveryplan,andmessagesandcommands.
Toeditarecoveryplan,thefollowingconditionsmustbeinplace:
To edit a recovery plan
1 OntheSummarytab,clickEditRecoveryPlan.
2 ModifytheplannameordescriptionandclickNext.
3 Modifytheprotectiongroupsincludedintherecoverysiteifneededandclick
Next.
4 Modifytheresponsetimesforthevirtualmachinesintherecoveryplanifneeded
andclickNext.
5 Modifythenetworksyouoriginallyspecifiedfortestingtheplan.
Whenyouarefinished,clickNext.
6 Modifythelocalvirtualmachinestosuspendifarecoveryoccursorduringa
recoverytest.
7 ClickFinish.
Therecoveryplanismodified.WhenyouselecttheplanagainintheInventory,
yourchangesarereflectedintheSummarytab,Historytab,andRecoverySteps
tab.
62 VMware, Inc.
Test a Recovery Plan

Youcanrunfrequenttests,whichsimulateanactualrecovery.Youcanruntest
recoveriesandedittherecoveryplantofixanyproblemswhenyourunthetests.SRM
runsexactlythesameplanthatisrunforbothtestsandactualrecoverieswiththe
followingexceptions:
Recoverytestsdonotconnecttotheprotectedsiteandshutdownvirtual
machines.
Recoverytestscreatetestnetworkssothattheinfrastructureoftheprotectionand
recoverysiteisprotected.Thetestnetworkisremovedafterthetestiscompleted.
Thisactionensuresthattheinfrastructureofbothsitesisprotected.Youcan,
however,selectanactualnetworktotestrecovery.
Thevirtualmachinesintherecoverysitetypicallystartfromadatastorethatis
clonedfromthetargetdatastoreintherecoverysitetoensurethatthetestisrun
againstastorageinfrastructurethatisisolatedfromtheproductionenvironment.
Totestarecoveryplan,thefollowingconditionsmustbeinplace:
To test a recovery plan
1 Inthenavigationbar,selecttheplantotest.
2 OntheSummarytab,clickTestRecoveryPlan.
3 ClickContinuetocontinuetherecoverytest.
IntheRecentTasksareaofthepage(ifitisopen),RunTestModeRecoveryPlan
appearsintheNamefield,andtheStatusfielddisplaysthepercentagecomplete.
Pausing, Resuming, or Cancelling a Test

Youcanpause,resume,orcancelarecoveryplantestatanytime.Whenyoupauseor
cancelatest,nonewstepsarestarted,andinprogressstepsaresubjecttothefollowing
rules:
Stepsthatcannotbestopped,suchaspoweringonorwaitingforaheartbeat,run
tocompletionbeforethepauseorcancellationcompletes.
Stepsthataddorremovestoragedevicesareundonebycleanupoperationsifyou
cancelorbysubsequentstepsifyoupauseandresume.
VMware, Inc. 63
Thetimeittakestopauseorcancelatestdependsonthetypeandnumberofstepsthat
areinprogresswhentherequestismade.Thetimeittakestoresumeatestdependson
thetypeandnumberofstepsthatwereinprogresswhenthepausewasrequested.
Run a Recovery Plan

Runninganactualrecoveryplanstartsthevirtualmachinesontherecoverysiteonthe
recoverysitenetwork.Thisprocesscannotbeundoneeasilyorautomatically.Ifyourun
arecoveryplan,itpermanentlyaltersthevirtualmachinesandinfrastructureofthe
protectedandrecoverysites.Thefollowingchangesoccurifyourunarecoveryplan:
Duringarecovery,iftheprotectedsiteisconnectedtotherecoverysite,virtual
machinesshutdowngracefullyontheprotectedsite.
Iftheconnectionbetweensitesislost,noactionistakenbySRMagainstthe
protectedvirtualmachinesintheprotectedsite.Thedatastoresintherecoverysite
areenabledforreadandwritecapabilitiesandSRMinitiatesthepowerupofthe
virtualmachinesintherecoverysiteaccordingtothestartuporderintherecovery
plan.
Iftheconnectionbetweenthesitesislostandtheprotectedsiteisdown,thevirtual
machinesarealreadyinashutdownstate.
Torunarecoveryplan,thefollowingconditionsmustbeinplace:
To run a recovery plan
1 Ontherecoverysite,IntheInventory,selecttheplantorun.
2 OntheSummarytab,clickRunRecoveryPlan.
3 ConfirmandclickRunRecoveryPlan.
Astheplanruns,thestatusofeachstepupdatesontheRecoveryStepstab.
Remove a Recovery Plan

RemovingarecoveryplanpermanentlydeletestheplanfromSRM.Youcannotretrieve
arecoveryplanafteritisdeleted.
Toremovearecoveryplan,thefollowingconditionsmustbeinplace:
64 VMware, Inc.
To remove a recovery plan
1 Inthenavigationbar,selecttheplantodelete.
2 OntheSummarytab,clickRemoveRecoveryPlan.
3 ClickYestoconfirmanddeletetheplan.
Configure Virtual Machines in a Recovery Plan

TheVirtualMachinestaballowsyoutoviewandconfigurethevirtualmachinesthat
thisrecoveryplanincludes.
Toconfigurevirtualmachinesinarecoveryplan,thefollowingconditionsmustbein
place:
VIClientmustbeconnectedtotherecoverysite.
To edit virtual machine properties in a plan
1 OntheVirtualMachinestab,clickEdit.
2 ClickBrowsetoviewtheavailablecustomizationspecifications.
3 Clickthearrowandselectthecustomizationpropertytoapplytothevirtual
machine.
Toconfigurethisoption,acustomizationspecificationmustbecreatedusingthe
VIClientontherecoverysite.Ifnospecificationsareconfigured,themessageNo
availableCustomizationSpecificationfoundappears.
4 ClickOK.
5 SpecifythedefaultrecoverypriorityandclickNext.
Recoverypriorityisapropertyofavirtualmachine,notarecoveryplan.The
recoverypriorityofavirtualmachinecannotbechangedafterithasbeenmade
partofarecoveryplan.
6 Addmessagesandcommands,removeorreorderstepstobeperformedbefore
poweron.
SeeAddMessageandCommandStepsonpage 52.
7 ClickNext.
8 Addmessagesandcommands,removeorreorderstepstobeperformedafter
poweron.
9 ClickFinish.
VMware, Inc. 65
View a Recovery Plan

Toviewarecoveryplan,clicktheRecoveryStepstab,whichliststherecommended
stepsfordisasterrecovery.Somestepsmightincludesubstepsinatreeformation.
Clicktheplussign(+)toexpandtheviewtoincludesubsteps.Clicktheminussign()
toviewonlyhighlevelsteps.
Inadditiontorecoverystepsandsubsteps,othercolumnsofinformationappear.
The followinginformationappearsintherecoveryplan.Somefieldsareemptyuntila
recoveryplanistestedorrun.
RecoveryStepThestepsandsubstepstobeperformedduringtherecovery.
StatusBlankuntilarecoveryplanisrunortested.Whenastepissuccessfully
completed,thewordSuccessappearsintheStatuscolumn.
TaskStartedWhenaplanisrunortested,thestartdateandtimeforthisstep
appear.
TaskCompletedWhenaplanistestedorrun,thecompleteddateandtimefor
thisstepappear.
ModeDescribeswhetherthestepisrunningduringatestoranactualrecovery.
Recoverydescribesstepsthatarerunningonlyduringarecovery.Ifatestis
running,thewordTestappearsandappliestotestsonly.
To select which information columns appear on a recovery plan
1 Rightclickthetextbar.
2 Deselectthenameofacolumntoturnoffviewingforthatcolumn.
OntheRecoverytab,atoolbaroficonsappears.Rollthecursorovereachicontoseea
briefdescriptionoftheicons,whichenableactionssuchaseditingorexportingyour
recoveryplan.
To export the steps of a recovery plan
1 ClicktheExporticonontheRecoveryStepstab.
2 Savethefileinadirectoryusingafilenameofyourchoice.
ThereportexportsinXML, .doc,XLW,HTML,andCSVformats.
66 VMware, Inc.
View Recovery Plan History

Afteryoutestorrunarecoveryplan,informationappearsontheHistorytab.
To view a recovery plan
1 OntheHistorytab,selectarecoveryplanandclickView.
2 ClicktheWindowsClosebuttonwhenyouarefinishedviewingtheplan.
Export Recovery History Results

UsetheHistorytabtoexportatherecoveryplanresults.
To export a recovery plan
1 OntheHistorytab,selecttherecoveryplantoexportandclicktheExporticon.
2 EnteranamefortherecoveryplanintheFileNamefieldandclickSave.
3 ClosetheSaveAsdialogbox.
Work with Customization Specifications

SRMusesdefaultsettingsinheritedfromVirtualCentersuchasregistration
information,timezone,administratorpassword,andIPadapterpropertiesofthe
virtualmachinesinarecoveryplan.YoucanupdatetheIPadapterproperties,butno
otherproperties,ofvirtualmachinesintheplanbyeditingthecustomization
specification.
Toapplycustomizationspecificationstovirtualmachines,seeConfiguringVirtual
MachinePropertiesonpage 49.
To create a customization specification

1 FromtheVIClient,selectEdit>CustomizationSpecifications.
2 SelectNew.
3 ClickNextuntiltheNetworkpageappears.
4 Tochangenetworksettings,selectCustomsettingsandclickNext.
5 SelectthenameofthenetworktocustomizeandclickCustomize.
VMware, Inc. 67
6 MakechangestothenetworksettingsandclickOK.
7 ClickNextandclickFinish.
ThescriptnowappearsontheCustomizationSpecificationManagerpageandis
availableforuseontheprotectedsite.
8 ClicktheClosebox.
To import a customization specification
1 SelectEdit>CustomizationSpecifications.
2 SelectImport.
3 BrowseforthescripttoimportandclickOpen.
68 VMware, Inc.
7
Failback 7
ManagingfailbackusingVMwareSiteRecoveryManager(SRM)isamanualprocess
thatyoucanmanagelikeanyplannedservermigration.WithSRMyoucanfailback
servicesfromarecoverysitetotheprotectedsiteaftertheprotectssiteisreadyto
resumeoperation.
NOTEConsultyourarrayvendorsdocumentationbeforeattemptingafailback.
Not allarrayssupportthenecessaryoperations.Formoreinformation,seetheVMware
Website.
FailbackScenarioonpage 69
OtherFailbackConsiderationsonpage 74
Failback Scenario
ThefollowingstepsdescribeascenariousingSRMasafailbacktooltoSiteAafterthese
virtualmachinesarerecoveredatSiteB.Sixmachinescalledapp_vm7through
app_vm12(hostedbyadatastoregroupcalledsharedsan2)arefailedbacktoSiteA
fromSiteB.
Figure 71illustratesthestorageconfigurationafterrunningafailoverfromSiteAto
SiteB.
VMware, Inc. 69
Figure 7-1. Storage Configuration after Running an Actual Failover from Site A to
Site B for the shared-san-2 Datastore
protected protected
virtual machines Write Disabled Read Write virtual machines
(app_vm7 to app_vm12) (read only) enabled (app_vm7 to app_vm12)
apps apps
apps apps
apps apps
apps apps
all apps apps all
powered apps apps powered
off by SRM on by SRM
at start of OS OS during the
source LUN target LUN
SRM Recovery (shared-san-2) (shared-san-2) SRM Recovery
Site A protected site Site B recovery site
ThisfailbackscenariodescribesthestepsforasuccessfulfailbackfromSiteBtoSiteA.
ItincludesthestepstocompletethereprotectionofSiteAafterthefailbackfromSiteB.
NOTEIfyouhavenotpurchasedaprotectionenablementlicensekey
(SRM_PROTECTED_HOST)fortheprotectedsite,youmusttransferthatkeyfromthe
recoverysitetotheprotectedsitebeforeyoucanrunafailback.Formoreinformation,
seeSRMLicensingonpage 24
Thefollowingtermsandabbreviationsareused.
SiteATheoriginalprotectedsite.
SiteBTheoriginalrecoverysite.
PG1TheoriginalprotectiongroupdefinedatSiteA.
PG2AnewprotectiongroupdefinedatSiteBtofacilitatethefailbackfrom
Site BbacktoSiteA.
PG3AnewprotectiongroupdefinedatSiteAtofacilitatethefailovertoSiteB.
PG3isbasicallythesameprotectiongroupasPG1.
RP1TheoriginalrecoveryplandefinedatSiteB.
RP2AnewrecoveryplandefinedatSiteAtofacilitatethefailbackfromSiteB
backtoSiteA.
SourceLUNAVMFSdatastorethatisbeingreplicatedtoanalternativedatacenter.
TargetLUNTheresultingdatastoreatthealternatedatacenter.
CloneLUNAcloneofthetargetLUNusedonlyduringatestoffailover.
70 VMware, Inc.
Chapter 7 Failback
Thisscenariodescribesgeneralproceduresforperformingfailbackfromarecoverysite
backtotheoriginalprotectedsite.
Tohelpyoutrackthesestepsasyoucompletethem,seeAppendix B,Failback
Checklist,onpage 83.
To prepare for failback
1 ShutdownallSiteBvirtualmachinesthatwererecoveredtoSiteBforthefailover.
2 CreatealistofalltheprotectedvirtualmachinesthatwererecoveredtoSiteB.You
willneedthisinformationforalaterstep.
3 IntheVirtualCenterdatastorebrowser,cleanupthedirectoryatSiteBthat
containedthevirtualmachineconfigurationfilescreatedduringprotectiongroup
creationatSiteA.
CAUTIONThedatastoreholdingthesevirtualmachinesistheoneusedfor
placeholdermachines.Donotremovethesefilesfortheactualvirtualmachines.
Thisisthelocationselectedduringthecreationoftheoriginalprotectiongroupat
SiteAPG1.Specifically,deletethe.vmsd,.vmx,and.vmxffiles.Usethelistyou
createdinStep 2aboveasareferenceduringthiscleanupstep.
To complete a storage configuration change so that the source LUN is now Site B
Workwithyourstorageteamtocompleteastorageconfigurationchangesothatthe
sourceLUNisnowassociatedwithSiteBandthetargetLUNisassociatedwithSiteA.
protected protected
virtual machines Write Disabled Read Write virtual machines
(app_vm7 to app_vm12) (read only) enabled (app_vm7 to app_vm12)
apps apps
apps apps
apps apps
apps apps
apps apps
protected apps apps protected
vms offline vms that will
in Site A OS OS be recovered
target LUN source LUN
(shared-san-2) (shared-san-2) to Site A
Site A recovery site Site B protected site
VMware, Inc. 71
To remove the out-of-date protected virtual machines from inventory on Site A
1 AtSiteA,rescanthehostbusadapters(HBAs)onallthehosts.Thismakesiteasier
toidentifytheprotectedvirtualmachines,becausetheynowappearinvalidinthe
inventory,asdoestheprotectiongrouptowhichtheyareassigned.
2 AtSiteA,removePG2fromtherecoveryplan,thendeletePG2.
3 SelectalltheprotectedvirtualmachinesatSiteAthatwererecoveredtoSite B.
RightclicktheselectedvirtualmachinesandselectRemove from Inventoryto
removethehighlightedprotectedvirtualmachinesfromtheinventoryatSite A.
To failback from Site B to Site A
1 CompletetheArrayManagerconfigurationwizardatSiteB,whichnowhasthe
sourceLUNconfiguredatSiteBandthetargetLUNconfiguredatSiteA.The
recoverysitearraymanagernowbecomestheprotectedsitearraymanager,and
theprotectedsitearraymanagernowbecomestherecoverysitearraymanager.
2 ConfigureinventorymappingsatSiteB.
Theseinventorypreferencesareassignedtotheprotectedvirtualmachineswhen
theyarerestartedatSiteAafterthefailback.
3 AtSiteB,configurePG2tofailbacktoSiteA.
4 AtSiteA,configureRP2.
DonotdeleteRP1,whichyoucreatedatSiteBtoprotectthedesignatedvirtual
machinesatSiteA.
5 ClickTesttotesttherecoveryplanwithclonesorsnapshotsofthetargetLUNson
theprotectedsite.Ifthetestissuccessful,clickRuntorunanactualrecoveryofRP 2.
Thefollowingfigureillustratesthestorageconfigurationaftertherecoveryagainst
RP2completes.
protected protected
virtual machines Read Write Write Disabled virtual machines
(app_vm7 to app_vm12) enabled (read only) (app_vm7 to app_vm12)
apps apps
apps apps
apps apps
apps apps
all apps apps all
powered apps apps powered
on by SRM off by SRM
during the OS OS at start of
target LUN source LUN
SRM Recovery (shared-san-2) (shared-san-2) SRM Recovery
Site A recovery site Site B protected site
72 VMware, Inc.
Chapter 7 Failback
To prepare Site A for failover in case of a second disaster
1 ShutdownalloftheprotectedvirtualmachinesatSiteAthatwerefailedbackfrom
SiteBduringtheSRMrecoveryoperationperformedinTofailbackfromSiteBto
SiteA.
TheshutdownensuredthatallI/OontheLUNshasstoppedbeforeswappingthe
replicationdirectiononthearrays.
2 PerformacleanupofthedirectoryatSiteAthatcontainedthevirtualmachine
configurationfilescreatedduringprotectiongroupcreationatSiteB.(SeeStep 3of
theproceduretitledToprepareforfailback.)
3 IntheVirtualCenterdatastorebrowser,cleanupthedirectoryatSiteAthat
containedthevirtualmachineconfigurationfilescreatedduringprotectiongroup
creationatSiteB.
To complete a storage configuration change so the source LUN is now Site A
Workwithyourstorageteamtocompleteasecondstorageconfigurationchange.
ReassociatethesourceLUNwithSiteA,andreassociatethetargetLUNwithSiteBand
thecloneLUN,asshowninthefollowingfigure.
protected protected
virtual machines Read Write Write Disabled Write Disabled virtual machines
(app_vm7 to app_vm12) enabled (read only) (read only) (app_vm7 to app_vm12)
apps apps
apps apps
apps apps
apps apps
protected apps apps protected
vms that will apps apps vms offline
be recovered in Site B
to Site A OS OS
source LUN target LUN clone LUN
(shared-san-2) (shared-san-2) (shared-san-2)
Site A protected site Site B recovery site
Thestorageconfigurationisnowrevertedtotheoriginalconfigurationbeforethesetup
ofSRM.Thestoragearrayvendordeterminesthedatasynchronizationmethod
(snapshotatintervalsorcontinuoussynchronization)ofthetargetLUNtotheclone
LUN.WhenasimulatedfailoverisinitiatedwiththetestoptioninSRM,finaldata
synchronizationisperformedfromthetargetLUNtothecloneLUN.
VMware, Inc. 73
To prepare Site B for failover in case of a second disaster
1 AtSiteB,rescanthehostbusadapters(HBAs)onallthehosts.Thismakesiteasier
toidentifytheprotectedvirtualmachines,becausetheynowappearinvalidinthe
inventory,asdoestheprotectiongrouptowhichtheyareassigned.
2 AtSiteB,removePG2fromtherecoveryplan,thendeletePG2.
3 AtSiteB,removealltheprotectedvirtualmachinesthatwererecoveredtoSite A
frominventoryatSiteB.Inthisscenario,thisisapp_vm7 to app_vm12.(SeeTo
removetheoutofdateprotectedvirtualmachinesfrominventoryonSiteA.)
4 CreatePG3atSiteAfortheprotectedvirtualmachines.
PG3shouldbeidenticaltoPG 1,theprotectiongroupthatwasoriginally
associatedwithRP1,therecoveryplanthatwasruninRecoverymodeand
resultedinthestartupoftheprotectedvirtualmachinesatSite B.
5 ReassociatetheprotectiongroupsatSiteAwithRP1atSiteB.
YoudonotneedtodeleteRP2(therecoveryplanthatwascreatedatSiteAto
facilitatetherecoverybacktoSiteAfromSiteB).
YouhavecompletedthereprotectionoftheprotectedvirtualmachinesatSiteA.
VMwarerecommendsthatyounowconductafailovertestagainstRP1toensurethat
SiteAisprotectedandreadyforanyeventthatmaynecessitatearecoverytoSiteBif
anotherdisasteroccurs.
Other Failback Considerations

Thereareseveralmoreissuestoconsiderduringafailback.
SitePairingSitesAandBneedtobepairedonlyonce.SRMmaintainsa
bidirectionalrelationshipbetweenpairedsites.
DNSUpdatesIfSiteAandSiteBarenotjoinedbyastretchedVLAN,manually
provideDNSupdatesasthevirtualmachinesaremovedbetweenSite AandSite B
andtheirIPaddresseschangetoaccommodatetheirnewnetwork.
74 VMware, Inc.
8
Alerting and Monitoring 8

ThischapterdescribesSiteRecoveryManager(SRM)eventsandalarmnotification
configurationoptions.Thischapterincludesthefollowingtopics:
SRMAlarmsonpage 75
AboutSRMAlarmTriggersonpage 76
EditSRMAlarmSettingsonpage 76
PrepareforAlarmNotificationbyEmailonpage 78
SRM Alarms
SRMalarmsarenotificationsthatoccurinresponsetoselectedeventsthatSRMraises.
TheseeventtriggeredalarmsareavailableandconfiguredwhenSiteRecoveryis
selectedintheVIClient.ThealarmsspecifictoSRMeventsaredefinedwhenSRMis
installed.
SRMalarmsuseemailmessagenotification.Forinformationabouthowtoconfigurea
VirtualCenterServertosupportemailmessagealarmnotificationbeforeyoueditSRM
alarms,seePrepareforAlarmNotificationbyEmailonpage 78.
TheAlarmstabintheSiteRecoveryviewdisplaysthelistofalarmsforSRMthatare
activatedwhendesignatedeventsoccur.ThesealarmsareSRMspecificandarenot
availablefromtheVirtualCenterServer.(SRMalarmsdonotappearintheVIClients
TriggeredAlarmspane,thoughtheyareshownintheVirtualCenterEventLog.)
NOTESRMalarmsforanyeventdonottriggermorethanonceeveryfiveminutes.
Multipleinstancesofthesameeventduringafiveminuteperiodtriggeronlyasingle
alarm.
VMware, Inc. 75
About SRM Alarm Triggers

Alarmtriggerstakeseveralforms:
SRMgenerateseventsthatcanbeassociatedwithalarmsontheVirtualCenter
Server,suchas:
ProblemsontheSRMservergenerateSNMPtraps,emails,andsoon.
AlarmsareassociatedwithSRMeventsfromtheSRMplugin.
FailureoftheSRMserverorVirtualCenterserverattheprotectedorrecoverysite
generateseventsthatcanbeassociatedwithVirtualCenteralarms,suchas:
Problemswiththelocalsite(forexample,resourceconstraints).
Problemswiththeremotesite(forexample,beingunabletopingtheSRMor
VirtualCenterhostataremotesite).RemotesitefailureisreflectedintheSRM
eventsanddoesnottriggerarecovery.Recoverymustbeinitiatedmanually.
Diskspaceislow.
CPUuseexceededthelimit.
Memoryislow.
Theremotesitefailstorespond.
TheVirtualCenterServerorSRMserverattheremotesitefails.
Therecoveryteststarted,endedsuccessfully,failed,oriscancelled.
Virtualmachinerecoverystarted,ended,succeeded,failed,orreportsawarning.
Thefollowingarethealarmnotificationmethods:
Sendanotificationemailmessage
Sendanotificationtrap
Runascript
Edit SRM Alarm Settings

YoucanmodifySRMalarms.Asimplechangeistoenableordisablethealarm.Ifan
alarmisdisabled,anXappearsonthealarmlistingicon.
ToeditanSRMalarm,thefollowingconditionsmustbeinplace:
VIClientmustbeconnectedtotheprotectionorrecoverysite.
TheminimumrequiredprivilegesareModifyAlarm(Alarmsprivileges).
76 VMware, Inc.
Chapter 8 Alerting and Monitoring
To edit an alarm
1 UsingaVIClient,logintotheprotectedsiteVirtualCenterServer.
3 ClicktheAlarmstab.
4 RightclicktheeventandselectEditSettings.
5 ClickActiontochoosetheactiontotakewhentheeventistriggeredandspecify
theassociatedinformation.
Option Description
Sendanotification ProvidetheemailaddressofthenotificationrecipientintheValuefield.
email SMTPsendsanotificationemail.SMTPmustbereadywhentheemailis
sent.
TheVirtualCenterServergeneratestheemailmessagesubjectandbody
text.Onlythetolist(Value)isrequiredfromuserinput.Specifythe
emailaddresstowhichthemessageshouldbesent.
ForinformationaboutpreparingforemailmessageSMTPalarm
notificationforVirtualCenterServer,seetheVMwareInfrastructureBasic
SystemAdministration.
Sendanotification TheVirtualCenterServerisadefaultSNMPnotificationreceiver.An
trap SNMPtrapviewerisrequiredtoviewasenttrap.TheVirtualCenter
ServerhostmustbeconfiguredtoreceiveSNMPtraps.
ForinformationaboutpreparingforemailmessageSNMPalarmSMTP
alarmnotificationforVirtualCenterServer,seeVMwareInfrastructure
BasicSystemAdministration.
Runascript Ifthescriptisan.exefile,providethepathtothescript.Ifthescriptis
a.batfile,providethescriptpathasanargumenttothe
c:\windows\system32\cmd.execommand.Forexample,toruna
scriptlocatedinc:\alarmscript.bat,providethescriptpathas
c:\windows\system32\cmd.exe /c c:\alarmscript.cmd.
6 Tocompletethealarm,clickOK.
7 VirtualCenterverifiestheconfigurationofthealarmandaddsthealarmtothelist
ofalarmsforSRM.
VMware, Inc. 77
Prepare for Alarm Notification by Email

Touseemailmessagestosendalarmnotifications,youmust:
DefinetheSMTPserverandemailmessageaddressinginformation.
Specifytheemailaddressesfortheuserswhoyouwanttoreceivetheemail
notifications.
Toprepareforemailmessagealarmnotification,thefollowingconditionsmustbein
place:
TheVIClientmustbeconnectedtotheVirtualCenterServer.
MinimumrequiredprivilegeisSettings(Globalprivileges).
To define the SMTP server and email message addressing information
1 FromtheVIClient,chooseAdministration>VirtualCenterManagementServer
Configuration.
2 ClickMailinthenavigationlist.
3 Foremailmessagenotification,settheSMTPserverandSMTPportasfollows:
SMTPServerThehostnameorIPaddressoftheSMTPgatewaytousefor
sendingemailmessages.
SenderAccountTheemailaddressofthesender,forexample,
srm_alarms@example.com.
4 ClickOK.
5 IntheSRMview,clicktheAlarmstab.
6 Selectanalarmtoaddamailnotificationevent.
7 RightclickthealarmandselectEditSettings.
8 SelecttheActionstab.
9 ClickAdd.
10 ChangethetypeoftheactiontoSendanotificationemail.
11 Setthevalueoftheactiontotheemailaddresstosendthenotificationto.
78 VMware, Inc.
9
Protected and Recovery

Site Changes 9
SRMmonitorsandhandleschangestotheVirtualCenterServerattheprotectedand
recoverysites.
ChangestoVirtualCenterServeronpage 79
ChangestoProtectedSitesonpage 79
ChangestoRecoverySitesonpage 80
Changes to VirtualCenter Server

TheSRMserversdependontheavailabilityofcertaininventoryobjects,suchasvirtual
machinesandnetworks.ChangestotheVirtualCenterServerstatecanaffectSRM.
RenamingandrelocatingobjectsintheVirtualCenterServerinventorydoesnotaffect
SRMunlessitcausesresourcestobecomeinaccessibleduringtestorrecovery.
Changes to Protected Sites

SRMsupportsthefollowingchangesattheprotectedsitewithoutdisruption:
Modifyingprotectedvirtualmachineconfiguration,suchasadding,modifying,
removingdevices,orrelocatingvirtualmachines.
Changingavirtualmachinesmemorysizeontheprotectedsiteisnotreflectedon
therecoverysiteifthevirtualmachineisalreadyinaprotectiongroup.
Deletingprotectedvirtualmachines.
Deletinganobjectforwhichaninventorymappingexists.
VMware, Inc. 79
SRMrequiresreinstallationofSRMattheprotectedandrecoverysites:
TheVirtualCenterServerisreinstalledattheprotectedsite,reinitializingthe
VirtualCenterdatabase.
SRMisreinstalledattheprotectedsite,reinitializingtheSRMdatabase.
Changes to Recovery Sites

SRMsupportsthefollowingchangesattherecoverysitewithoutdisruption:
Deletingrecoveryvirtualmachines.
Movingrecoveryvirtualmachinestoadifferentfolder,resourcepool,ornetwork.
Deletinganobjectforwhichaninventorymappingexists.
TheVirtualCenterServerisreinstalledattherecoverysite(reinitializingthe
VirtualCenterdatabase).
SRMrequiresreinstallationofSRMattheprotectedandrecoverysitesifSRMis
reinstalledattherecoverysite(reinitializingtheSRMdatabase).
80 VMware, Inc.
Preinstallation Checklist A
Thefollowingisachecklisttohelpensurethatyourstorageplatformsarereadyfor
integrationwithSRM.
Description Protected Recovery

DownloadtheSRMsoftware,StorageReplicationAdapter(SRA),
andproductinformationfromtheVMwareWebsite.
EnsurethatasupportedreleaseofMicrosoftSQLServerorOracle
Databaseserverisconfiguredandreadyforuse.
CreateadatabaseinstanceforVirtualCenterServer.
CreateadatabaseuserfortheVirtualCenterinstancewith
db ownerandcreatetableprivileges.
CreateaDSNfortheVirtualCenterdatabase.
EnsurethatacompatibleversionofVirtualCenterServeris
installedandreadyforuse.
UsetheVIClienttosetupaccesstotheVirtualCenterServer.
EnsurethatasupportedversionofESXisinstalledandintegrated
intoVirtualCenter.TheESXmusthaveaccesstoaLUNonaSAN
thatisconfiguredasaVMFSdatastoreandissetupfordata
replicationtoacorrespondingSANintherecoverysite.
VMware, Inc. 81
Description Protected Recovery
CreateadatabaseinstanceforSRM.
Createadatabaseuser,withappropriateprivileges,fortheSRM
databaseinstance.
CreateaDSNfortheSRMdatabase.
IdentifyaphysicalorvirtualsystemonwhichtoinstallSRM.
InstalltheSRAfromyourarrayproviderontheSRMhost.
82 VMware, Inc.
Failback Checklist B
Usethefollowingchecklisttotrackthefailbackstepsasyoucompletethem.
Prepare for failback

_____ SiteB Powerdowntheprotectedvirtualmachines.
_____ SiteB Createalistoftheprotectedvirtualmachinesthatwererecoveredto
SiteB.
_____ SiteB CleanupthedirectoryatSiteBthatcontainedthevirtualmachine
configurationfilescreatedwhenyouassignedtheprotectedmachines
toaprotectiongrouponSiteA.
Complete a storage configuration change so that the source LUN is now Site B
_____ Storage Workwithyourstorageteamtocompleteastorageconfiguration
changesothatthesourceLUNisnowassociatedwithSiteBandthe
targetLUNisassociatedwithSiteA.
Remove out-of-date protected virtual machines from inventory on Site A
_____ SiteA Rescanthehostbusadapters(HBAs)onallthehosts.
_____ SiteA ConnecttotheVirtualCenterinstanceatSiteAanddeletetheoriginal
protectiongroup(PG2).
_____ SiteA RemovealltheprotectedvirtualmachinesthatwererecoveredtoSite
BfromtheinventoryatSiteA.
Failback from Site B to Site A
_____ SiteB CompletetheArrayManagerconfigurationwizardatSiteB,which
nowhasthesourceLUNconfiguredatSiteBandthetargetLUN
configuredatSiteA.
_____ SiteB ConfiguretheinventorypreferencesatSiteB.Thesearetheinventory
preferencesthatareassignedtotheprotectedvirtualmachineswhen
theyarerestartedatSiteAafterthefailback.
VMware, Inc. 83
_____ SiteB ConnecttotheVirtualCenterinstanceatSiteBandconfigurePG2.

_____ SiteA ConnecttotheVirtualCenterinstanceatSiteAandconfigureRP2.
_____ SiteA PerformarecoveryagainstRP2.
Prepare Site A for failover in case of a second disaster
_____ SiteA ShutdowntheprotectedvirtualmachinesatSiteAthatwerefailed
backfromSiteBinthepreviousstep.
_____ SiteA CleanupthedirectoryatSiteAthatcontainedthevirtualmachine
configurationfilescreatedduringprotectiongroupcreationatSiteB.
Complete a storage configuration change so the source LUN is now Site A
_____ Storage Workwithyourstorageteamtocompleteasecondstorage
configurationchangesothatthesourceLUNisassociatedwithSiteA
again,andthetargetLUNandcloneLUNareassociatedwithSiteB.
Prepare Site B for failover in case of a second disaster
_____ SiteB Rescanthehostbusadapters(HBAs)onallthehosts.
_____ SiteB ConnecttotheVirtualCenterinstanceatSiteBanddeletePG2.
_____ SiteB ConnecttotheVirtualCenterinstanceatSiteBandremoveallthe
protectedvirtualmachinesatSiteB.Thesevirtualmachineswere
recoveredtoSiteA.
_____ SiteA CreatePG3atSiteAfortheprotectedvirtualmachines.
_____ SiteB ReassociatePG3(fromstep18atSiteA)withRP1atSiteB.
_____ SiteB PerformatestfailoveragainstRP1tomakesurethatSiteAis
protectedagain.
84 VMware, Inc.
Use the srm-config
command to repair an SRM
server connection C
Thesrm-configcommandconfiguresthenetworkconnectionbetweenanSRMserver
andtheVirtualCenterServerthatsupportsit.Anadministratorcanusethiscommand
torepairanSRMserverconnectionwheneithertheVirtualCenterServerortheSRM
serverIPaddresshaschanged,orwhentheuserIDorpasswordusedfor
credentialbasedauthenticationchanges.
NOTEAfteryouhavecompletedanyoftheproceduresdescribedhere,youmust
reconfiguresitepairingasdescribedinConnectingtheProtectedandRecoverySites
onpage 34.
Repair a connection after an SRM server IP address change
1 LogintotheSRMserverhostandstartaWindowscommandshell.
2 OpenC:\Program Files\VMware\VMware Site Recovery

Manager\config\extension.xmlfileinatexteditor.
3 Intheopenfile,locatethe<url>tagandchangeitscontentstothenewIPaddress
andportoftheSRMserver:
<config>
<extension>
<key></key>
<version></version>
<description></description>
<servers>
<server>
<url>http://10.17.186.120:8095</url>
VMware, Inc. 85

Manager\bin.
5 Runthefollowingcommandtoupdatetheextensionregistration:
C:\Program Files\VMware\VMware Site Recovery Manager\bin>srm-config.exe
-cmd updateext -cfg ..\config\vmware-dr.xml -extcfg
..\config\extension.xml
Repair a connection after a Virtual Center server IP address change

Manager\bin.
3 Runthefollowingcommand,where<vcipaddr>istheIPaddressoftheVirtual
Centerhost:
-cmd updatevc -cfg ..\config\vmware-dr.xml -vc <vc-ip-addr>
Ifthatcommandreturnsanerrorindicatingthatthecertificateisnottrusted,run
thefollowingcommand,where<vcipaddr>istheIPaddressoftheVirtualCenter
hostand<thumbprintstring>isthethumbprintstringreturnedintheerror
message:
-cmd updatevc -cfg ..\config\vmware-dr.xml -vc <vc-ip-addr> -thumbprint
<thumbprint-string>
Reinitializing credential-based authentication after a user ID or password change
2 ChangedirectorytoC:\ProgramFiles\VMware\VMwareSiteRecovery
Manager\bin
3 RunthefollowingcommandtoupdatetheuserIDandpassword,supplyingthe
new<userID>onthecommandlineandthepasswordwhenprompted:
-cmd updateuser -cfg ..\config\vmware-dr.xml -u <userID>
86 VMware, Inc.
Avoiding Replication of
Paging Files and Other
Transient Data D
WhileSRMallowsyoutoreplicatetransientdatasuchasWindowspagingfilesor
virtualmachineswapfiles,suchdataneednotbereplicated.Preventingreplicationof
suchdataavoidsunnecessaryconsumptionofnetworkbandwidth.
Specify a Nonreplicated Datastore for Swapfiles

Everyvirtualmachinerequiresaswapfile,whichisnormallycreatedinthesame
datastoreastheothervirtualmachinefiles.WhenyouuseSRM,thisdatastoreis
replicated.Topreventswapfilesfrombeingreplicated,createthemonanonreplicated
datastore.Thisproceduremustbecarriedoutforallprotectedclusters,atboththe
protectedandrecoverysites.Formoreinformation,seetheVMwareInfrastructure
documentation.
To create swapfiles on a nonreplicated datastore (ESX 3.5)
1 IntheVIClient,rightclickanESXclusterandclickEditSettings.
2 IntheSettingswindowforthecluster,clickSwapfileLocationandselectStorethe
swapfileinthedatastorespecifiedbythehost,thenclickOK.
3 Foreachvirtualmachineinthecluster:
a ClicktheConfigurationtab.
b ClickEditontheSwapfilelocationline.
c IntheVirtualMachineSwapfileLocationwindow,selectanonreplicated
datastoreandclickOK.
VMware, Inc. 87
To create swapfiles on a nonreplicated datastore (ESX 3.0.2)
1 Intheselectedcluster,pickavirtualmachineandshutitdown.
2 Makeabackupcopyofthevirtualmachines.vmxfile.
3 Editthe.vmxfiletochangethevalueofthesched.swap.dirparametertospecify
thepathnameofanonreplicateddatastoreattheprotectedsite.
Adatastorewiththispathnamemustalsoexistattherecoverysite.Ifitdoesnot,
thevirtualmachinecannotpoweronattherecoverysite.
4 Editthevmxfiletoremovethesched.swap.derivedNameline.
5 Savethemodified.vmxfile.
6 Poweronthevirtualmachine.
7 Repeattheprocedureforeachvirtualmachineinthecluster.
Creating a Nonreplicated Virtual Disk for Paging File

Storage
Inthedefaultconfiguration,Windowscreatesitspagingfileonthesystemdisk
(typicallyC:).Pagingfilescreatedinthislocationarealwaysreplicatedwhenyouuse
areplicateddatastore.Youcanavoidreplicationofpagingfilesbycreatingavirtual
disk(.vmdkfile)onanonreplicateddatastoreand,oneachvirtualmachineina
protectiongroup,configuringWindowstocreateitspagingfileonthatdisk.SRM
detectsthatanyvirtualmachineconfiguredthiswaydependsonatleastone
nonreplicatedvirtualdisk(thepagingfiledisk)andremovesthatvirtualmachinefrom
itsprotectiongroup.Youmustexplicitlydesignateacopyofthatvirtualdiskfileatthe
recoverysitefortherecoveredvirtualmachinetouse.
Tosimplifytherepetitionofthisprocedureforeveryvirtualmachineinaprotection
group,youcancreateavirtualdiskfiletemplateandthencloneittoprovide
nonreplicatedpagingfiledisksforvirtualmachinesatbothsites.
To force virtual machines to use nonreplicated paging file storage
1 Attheprotectedsite,createatemporaryvirtualmachine.
2 Onthetemporaryvirtualmachine,createanewdisk.
Storethediskfileinalocationwhereyoutypicallystorevirtualmachinetemplates.
3 Poweronthetemporaryvirtualmachine,thencreateandformatapartitiononthe
newdisk.
4 Disconnectthenewdiskfromthetemporaryvirtualmachine.
88 VMware, Inc.
Appendix D Avoiding Replication of Paging Files and Other Transient Data
5 Copythetemplatedisktoatemplatefolderattherecoverysite.
Youmustcopythe .vmdkfileanditsflatcounterpart(forexample,pagedisk.vmdk
andpagedisk-flat.vmdk).
6 Attheprotectedsite,foreachvirtualmachineinaprotectiongroup:
a Usethevmkfstoolscommandtocreateacloneofthetemplatediskina
nonreplicateddatastore.
b UsetheVIClienttoconnectthecloneddisktothevirtualmachine.
c Poweronthevirtualmachineandassignadrivelettertothecloneddisk.
d Configurethevirtualmachinetocreateitspagingfileontheclonedvirtual
disk.
e Shutdownandrestartthevirtualmachinesothatitwritesitspagingfileto
thenewlocation(ontheclonedvirtualdisk).
Youcandeletetheold,unusedpagingfilefromthesystemdisk.
f UsethevmkfstoolscommandtoclonethetemplateyoucopiedinStep 5toa
.vmdkfileonanonreplicateddatastoreattherecoverysite.
g UsetheVIClienttoviewtheprotectiongroupthatcontainsthevirtual
machine.
Becausethevirtualmachineusesanonreplicateddiskforitspagingfile,SRM
notifiesyouthatthevirtualmachineusesoneormoredevicesthatdonothave
filebackingsonareplicatedLUN.Itthenremovesthevirtualmachinefrom
theprotectiongroupuntilyouresolvethisconfigurationproblem.
h IntheVIClient,usetheConfigureStorageforthisVMpagetoassignstorage
forthepagingfiledisktothe.vmdkfileyouclonedinStep f.
Afteryouconfigurethevirtualmachinetousethenonreplicateddiskatthe
protectedsite,SRMconsidersthevirtualmachinesstoragetobeconfigured
andreturnsittotheprotectiongroup.
Afterthechangesyoumadeattheprotectedsitearereplicatedtotherecoverysite,you
canrunatestoftherecoveryplantoverifythattherecoveredvirtualmachinesare
usingthenonreplicatedpagingfile.
VMware, Inc. 89
90 VMware, Inc.
Glossary
arraybasedreplication
Replicationofvirtualmachinesthatismanagedandrunbythestoragesubsystem
itselfratherthanfrominsidethevirtualmachines,thevmkernel,ortheservice
console.
failback
Theprocessofrestoringasystemtoitsoriginalstate,followingasystemfailure
thatautomaticallyswitchedthecomputerserver,system,ornetworktoastandby
server,systemornetwork.
failover
Eventthatoccurswhentherecoverysitetakesoveroperationinplaceofthe
protectedsiteafterthedeclarationofadisaster.
inventorymapping
Mappingbetweenresourcepools,networks,andvirtualmachinefoldersonthe
protectedsiteandtheirdestinationcounterpartsontherecoverysite.
LUN(logicalunitnumber)
Anidentifierforadiskvolumeinastoragearray.
protectedsite
Thedatacenterthatcontainsthevirtualmachinesforwhichdataisbeing
replicatedtotherecoverysite.
protectiongroup
Agroupofvirtualmachinesthatarefailedovertogetherduringtestandrecovery.
VMware, Inc. 91
recoveryplan
Thenecessarystepstorecoverprotectedvirtualmachinesintheirassigned
protectiongroupsaccordingtoanorderofprioritydefinedintheplan.
recoverysite
Thedatacenterthatcontainstherecoveryvirtualmachinesperformingworkwhile
theprotectedsiteisunavailable.
recoveryvirtualmachine
Aplaceholderthatrepresentsaprotectedvirtualmachinerepresentingthevirtual
machinesreplicatedfromtheprotectedsite.
storagereplicationadapter(SRA)
Softwarethatstoragevendorsprovidethatensuresintegrationofstoragedevices
withSiteRecoveryManager.Thesevendorspecificscriptssupportarray
discovery,replicatedLUNdiscovery,testfailover,andactualfailover.
storagearray
Astoragesystemthatcontainsmultiplediskdrives.
92 VMware, Inc.
Index
A configuration
alarms inventory preferences 47
defined 75 prerequisites for virtual machine pro-
defining message addressing tection properties 50
information 78 protected site 43
editing 77 recovery site 59
events that trigger 76 requirements for VMware
notification 75 Infrastructure 44
prerequisites for editing 76 connecting protected and recovery sites
prerequisites for email message see pairing 34
SMTP notification 78 customization specifications 67
API listener ports creating 67
HTTP 30 importing 68
SOAP 30
array managers
D
repairing 47 database requirements
array scripts 43 Oracle Server 23
authentication databases
see secure connection 34 Oracle 11
SQL 11
B DataSourceName (DSN) 30
batch file 52 datastore
meta data 49
C datastore groups
checklists and protection groups 13
failback 83 directory cleanup during failback 71, 73
pre-installation 81 disaster
clones 20 definition of 9
masking of 20 DNS updates 74
command steps
prerequisites for adding 52 E
purpose of 52 export formats (for recovery plans) 61
VMware, Inc. 93
F procedure for SRM plug-in 32

failback VMware Infrastructure requirements
change source LUN to site A 73 for 19
change source LUN to site B 71 inventory mapping
checklist 83 how used 17
directory cleanup 71, 73 inventory preferences
failing back from recovery to protect- configuring 47
ed site 72 prerequisites for configuring 47
managing 69 purpose of 47
prepare Site A for another
failover 73 L
prepare Site B for another licensing
failover 74 finding more information 24
preparing for 71 license server 24
scenario 69 SiteRecoveryManager.lic file 24
features of SRM 10 VMware License Server Tools 25
CPU and memory quality 11 listener ports
instant updates 11 HTTP 30
leveraged storage 10 SOAP 30
monitoring and alerts 11 LUN
network reconfiguration 10 clone 73
non-disruptive tests 10 masking and zoning 20
predictable management 11 replication verification 13
prepared response 10 source LUN 71
target LUN 71
H
host bus adapters (HBAs) 72, 74 M
host system requirements 20 maximums
HTTP port 30 number of connections 30
response time for virtual
I machines 61
installation message steps
array requirements for 20 prerequisites for adding 52
operating systems required for purpose of 52
SRM 20 meta data 49
operating systems required for SRM Microsoft .NET 2.0 Framework 21
plug-in 21
prerequisites 28 N
procedure 28, 31 notification 75
94 VMware, Inc.
Index
O testing 63, 72
operating system viewing 66
20 viewing details 61
viewing history 67
P recovery site
pairing 74 disruptive modifications 80
prerequisites for 34 non-disruptive modifications 80
protected and recovery sites 34
PKCS#12 certificate file 29 S
placeholder virtual machine scripts
purpose of 49 alarm notification 77
poweron categorization running batch file 53
High, Normal, Low, or No 60 running DOS command 53
pre-installation checklist 81 secure connection
protected and recovery sites certificate based 34
setting up 15, 16 credential based 34
protected site SMTP port 78
disruptive modifications 80 SMTP server 78
non-disruptive modifications 79 snapshots 20
protection groups 13 masking of 20
and datastore groups 13 SNMP trap 77
creating 48 SOAP
defined 16, 48 port 30
on protected sites 16 SRM
prerequisites for creating 48 environment 12
installation process 15
R requirements for using 11
recovery plan SRM architecture components
creating 60 ESX server 12
defined 16, 59 license server 12
editing 62 Oracle or SQL database 12
export formats 61, 66 SAN 13
exporting 66, 67 SRM Server 12
prerequisites for creating 60 VirtualCenter Server 12
prerequisites for removing 64 VMware File System (VMFS) 13
prerequisites for running actual 64 SRM Bulk Insert feature 23
prerequisites for testing 63 default file location 23
removing 65
running actual 64, 72
VMware, Inc. 95
storage replication adapters 20, 43

suspending virtual machines 60
system requirements 20
T
trigger events for alarms 76
trusted certificate 34
V
VI Client
logging into SRM from 33
using to manage SRM 33
Virtual Machine File System (VMFS) 13
virtual machines 16
configuring 17, 65
customization settings 67
mapping preferences 16
poweron categorization 60
prerequisites for configuring 65
prioritizing for restart after
recovery 16
removing from protected site
inventory 72
suspending non-critical 60
VMware Infrastructure
auditability 10
change control 10
Distributed Resource Scheduler 10
encapsulation 9
hardware independence 10
hardware re-purposing 10
how it supports SRM 9
resource pools 10
shared storage 9
VLANs and SRM testing 10
96 VMware, Inc.

SRM 10 Admin

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SRM 10 Admin

Uploaded by

Copyright:

Available Formats

Administration Guide

Site Recovery Manager 1.0 Update 1

Site Recovery Manager Administration Guide

VMware Infrastructure Documentation

Technical Support and Education Resources

Online and Telephone Support

VMware Professional Services

Overview of Site Recovery

VMware Infrastructure Supports Site Recovery Manager

Site Recovery Manager Features

Site Recovery Manager Requirements

Site Recovery Manager Environment

Figure 1-1. Prerequisite Environment for SRM

VCMS VirtualCenter VirtualCenter VCMS

ESX ESX ESX ESX ESX

VMFS VMFS VMFS VMFS VMFS

primary site secondary site

ESXServersA virtualization layer run on physical servers that abstracts processor,

LUN Replication and Datastores

Site Recovery Manager Process Overview

Figure 1-2. SRM Installation Architecture

SRM server 1 SRM server 2

protected site recovery site

Set Up the Protected and Recovery Sites

Figure 1-3. Relationship of Computing Resources in the Protected Site to the

apps (whole site)

apps apps apps apps

Configure Virtual Machines

Folder 3 Folder 4 Inherited Inventory Mappings

Prerequisites for SRM Installation

SRM Hardware and Software Requirements

SRM Database Requirements

Microsoft SQL Server Configuration

Oracle Server Configuration

Table 2-2. SRM Configuration Maximums

Import License Files

To enable an SRM license

Installing or Updating Site

Install Site Recovery Manager

Update Site Recovery Manager

Install the Site Recovery Manager Plug-In

To download and install the SRM plug-in

Updating Database Credentials

Reverting to a Previous Release

To revert to a previous release

Use the VI Client to Manage SRM

To log in to SRM from a VI Client session

Connecting the Protected and Recovery Sites

Pairing Sites with Credential-Based Authentication

To connect to protected and recovery sites

Pairing Sites Using Certificate-Based Authentication

To connect to protected and recovery sites

SRM Users, Groups, Permissions, and Roles

SRM Default Roles

Assign VirtualCenter Access Permissions

To assign a permission to a user or group

d RepeatStep athroughStep ctoaddadditionalusersorgroupsandclickOK

Add a New User Group and Role to SRM

To assign a user or group permission

d RepeatStep athroughStep ctoaddmoreusersorgroups.

Change Access Permissions

To change the permissions for a user or group

Remove Access Permissions