1.0

VMware, Inc. 71
Chapter 7 Failback
Thisscenariodescribesgeneralproceduresforperformingfailbackfromarecoverysite
backtotheoriginalprotectedsite.
Tohelpyoutrackthesestepsasyoucompletethem,seeAppendix B,“Failback
Checklist,”onpage 83.
To prepare for failback
1ShutdownallSiteBvirtualmachinesthatwererecoveredtoSiteBforthefailover.
2 Create
alistofalltheprotectedvirtualmachinesthatwererecoveredtoSiteB.You
willneedthisinformationforalaterstep.
3IntheVirtualCenterdatastorebrowser,cleanupthedirectoryatSiteBthat
containedthevirtualmachineconfigurationfilescreatedduringprotectiongroup
creationatSiteA.
This
isthelocationselectedduringthecreationoftheoriginalprotectiongroupat
SiteA‐PG1.Specifically,deletethe.vmsd,.vmx,and.vmxffiles.Usethelistyou
createdinStep 2aboveasareferenceduringthisclean‐upstep.
To complete a storage configuration change so that the source LUN is now Site B
Workwithyourstorageteamtocompleteastorage
configurationchangesothatthe
sourceLUNisnowassociatedwithSiteBandthetargetLUNisassociatedwithSiteA.
CAUTIONThedatastoreholdingthesevirtualmachinesistheoneusedfor
placeholdermachines.Donotremovethesefilesfortheactualvirtualmachines.
Site A — recovery site Site B — protected site
target LUN
(shared-san-2)
Write Disabled
(read only)
source 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
protected
vms offline
in Site A
protected
virtual machines
(app_vm7 to app_vm12)
protected
vms that will
be recovered
to Site A