
TECHNICAL WHITE PAPER / 117
VMware vCenter Site Recovery Manager 5.0
Evaluation Guide
When executing the failback of the recovery plan, it will only have the virtual machines and other information
that were in the recovery plan for initial failover. If VMs have been added to the recovery site after failover, but
before failback, they will not be automatically represented in the failback. If the environment has changed
dramatically during the failed-over state, ensure that recovery plans are updated to reflect the new environment.
Figure 123. Failback Will Not Automatically Update Recovery Plans with VMs That Are Added to the Failover Site
being protected to which site. This becomes especially important with regards to the process of reprotects and
failbacks to ensure that data is being synchronized correctly. To ensure that the reprotect has successfully
reversed the direction of replication and that a failback is going to be successful, you might choose to return to
the Array Managers section of SRM and examine the direction of replication for each relevant device by clicking
the appropriate Array Manager and selecting the Devices tab. Here, you can see in graphic detail the direction
in which devices are replicating, and can ensure that the failover will be directed appropriately.
Kommentare zu diesen Handbüchern