1.0

Site Recovery Manager Administration Guide
70 VMware, Inc.
Figure 7-1. Storage Configuration after Running an Actual Failover from Site A to
Site B for the shared-san-2 Datastore
ThisfailbackscenariodescribesthestepsforasuccessfulfailbackfromSiteBtoSiteA.
ItincludesthestepstocompletethereprotectionofSiteAafterthefailbackfromSiteB.
Thefollowingtermsandabbreviationsareused.
 SiteA—Theoriginalprotectedsite.
 SiteB—Theoriginalrecoverysite.
 PG1—TheoriginalprotectiongroupdefinedatSiteA.
 PG2—AnewprotectiongroupdefinedatSiteBtofacilitatethefailbackfrom
Site BbacktoSiteA.
 PG3—AnewprotectiongroupdefinedatSiteAtofacilitatethefailovertoSiteB.
PG3isbasicallythesameprotectiongroupasPG1.
 RP1—TheoriginalrecoveryplandefinedatSiteB.
 RP2—AnewrecoveryplandefinedatSiteAtofacilitatethefailbackfromSiteB
backtoSiteA.
 SourceLUN—AVMFSdatastorethatisbeingreplicatedtoanalternativedatacenter .
 TargetLUN—Theresultingdatastoreatthealternatedatacenter.
 CloneLUN—AcloneofthetargetLUNusedonlyduringatestoffailover.
NOTEIfyouhavenotpurchasedaprotection‐enablementlicensekey
(SRM_PROTECTED_HOST)fortheprotectedsite,youmusttransferthatkeyfromthe
recoverysitetotheprotectedsitebeforeyoucanrunafailback.Formoreinformation,
see“SRMLicensing”onpage 24
Site A — protected site Site B — recovery site
source LUN
(shared-san-2)
Write Disabled
(read only)
target LUN
(shared-san-2)
Read Write
enabled
protected
virtual machines
(app_vm7 to app_vm12)
apps
apps
apps
apps
apps
apps
OS
apps
apps
apps
apps
apps
apps
OS
all
powered
off by SRM
at start of
SRM Recovery
protected
virtual machines
(app_vm7 to app_vm12)
all
powered
on by SRM
during the
SRM Recovery