If the protected site is offline and Site Recovery Manager cannot perform its usual tasks in a timely manner which increases the RTO to an unacceptable level, you can run the recovery with the forced recovery option. Forced recovery starts the virtual machines on the recovery site without performing any operations on the protected site.
Only use forced recovery in cases where the recovery time objective (RTO) is severely affected by a lack of connectivity to the protection site.
Forced recovery is for use in cases where infrastructure fails at the protected site and, as a result, protected virtual machines are unmanageable and cannot be shut down, powered off, or unregistered. In such a case, the system state cannot be changed for extended periods. To resolve this situation, you can force recovery. Forcing recovery does not complete the process of shutting down the virtual machines at the protected site. As a result, a split-brain scenario occurs, but the recovery might complete more quickly.
When running disaster recovery using vSphere Replication, Site Recovery Manager prepares vSphere Replication storage for reprotect and you do not have to verify mirroring.
To select forced recovery when running disaster recovery, you must enable the option recovery.forceRecovery in Advanced Settings on the Site Recovery Manager Server on the recovery site. That enables the option in the Run Recovery Plan wizard. You can only select the forced recovery option in disaster recovery mode. It is not available for planned migration.
After the forced recovery completes, you can resolve the issue that necessitated the forced recovery. After you resolve the underlying issue, run planned migration on the recovery plan again, resolve any problems that occur, and rerun the plan until it finishes successfully. Running the recovery plan again does not affect the recovered virtual machines at the recovery site.
When you run planned migration after running a forced recovery, virtual machines on the protected site might fail to shut down if the underlying datastores are read only or unavailable. In this case, log into vCenter Server on the protected site and power off the virtual machines manually. After you have powered off the virtual machines, run planned migration again.