1.0

VMware, Inc. 73
Chapter 7 Failback
To prepare Site A for failover in case of a second disaster
1ShutdownalloftheprotectedvirtualmachinesatSiteAthatwerefailedbackfrom
SiteBduringtheSRMrecoveryoperationperformedin“TofailbackfromSiteBto
SiteA.”
TheshutdownensuredthatallI/OontheLUNshasstoppedbeforeswappingthe
replicationdirectionon
thearrays.
2PerformacleanupofthedirectoryatSiteAthatcontainedthevirtualmachine
configurationfilescreatedduringprotectiongroupcreationatSiteB.(SeeStep 3of
theproceduretitled“Toprepareforfailback.”)
3IntheVirtualCenterdatastorebrowser,cleanupthedirectoryatSiteAthat
containedthe
virtualmachineconfigurationfilescreatedduringprotectiongroup
creationatSiteB.
To complete a storage configuration change so the source LUN is now Site A
Workwithyourstorageteamtocompleteasecondstorageconfigurationchange.
ReassociatethesourceLUNwithSiteA,andreassociatethetargetLUNwithSiteBand
thecloneLUN,asshowninthefollowingfigure.
The
storageconfigurationisnowrevertedtotheoriginalconfigurationbeforethesetup
ofSRM.Thestoragearrayvendordeterminesthedatasynchronizationmethod
(snapshotatintervalsorcontinuoussynchronization)ofthetargetLUNtotheclone
LUN.WhenasimulatedfailoverisinitiatedwiththetestoptioninSRM,finaldata

synchronizationisperformedfromthetargetLUNtothecloneLUN.
Site A — protected site Site B — recovery site
source LUN
(shared-san-2)
clone LUN
(shared-san-2)
Write Disabled
(read only)
target LUN
(shared-san-2)
Write Disabled
(read only)
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 that will
be recovered
to Site A
protected
virtual machines
(app_vm7 to app_vm12)
protected
vms offline
in Site B