Due to an unexpected power outage, Site A is completely down. The disaster recovery strategy was implemented (see diagram). What is the correct way to start replicated VMs on Site B, while ensuring you can failback after Site A comes back online?
Due to an unexpected power outage, Site A is completely down. The disaster recovery strategy was implemented (see diagram). What is the correct way to start replicated VMs on Site B, while ensuring you can failback after Site A comes back online?
In the event of an unexpected power outage at Site A, resulting in the site being completely down, executing a planned failover is not feasible as it requires communication with the source VM to initiate a seamless transition to the replica. The correct procedure in this scenario is to perform an immediate Failover because it allows the replica VMs at Site B to take over instantly. This ensures continued availability of services without needing Site A to be online. This step is crucial for ensuring that operations can resume quickly despite the outage at Site A.
D is correct
Planned failover like the word says it's for planned situation. Perform Failover it's the right answer.
"Failover Now: Failover now refers to an immediate response to an unexpected system or service failure. In this case, the primary system or service experiences an unplanned outage or becomes unavailable, and the failover process is triggered immediately to shift the workload to a secondary system or service."
With Site A offline there is no way of "planned failover" so no incremental pass and a final with the VMs shut down. Failover with the latest state already replicated to Site B is the only option.
There is a similar Question where BUR and vC are in Site A. in this case the correct answer is to start the replicas manually since there is no management available
- Failover Now = Turns on the latest replica. workload from source VM is not migrated so we actually have some data loss depends on when the last replication was done. - Planned Failover = Moves all workload in from source vm to replica. Powers off source vm and the replica is now acting same as the source VM. Answer is B
You can not run Planned Failover, because Site A is down.
The correct way to start replicated VMs on Site B while ensuring you can failback after Site A comes back online is to perform a "Planned failover". This option ensures that the replication process is stopped and all changes made to the VM on Site B are not replicated back to Site A. This will prevent any data loss or conflicts when Site A comes back online. After the failover is completed, the administrator can work on restoring Site A to its normal state. Once Site A is back online, a "Planned failback" can be performed to move the VMs back to Site A.
D is correct