This is provided as supplemental material to the User Guide until the Fail Over / Fail Back process is updated.
Fail Over refers to switching to a redundant system in case of system failure. Fail Back is the process of returning the workload to the original or replacement system once the system failure is resolved. Rapid Recovery supports Fail Over and Fail Back in replicated environments. Fail Over and Fail Back is performed on a machine by machine basis.
To summarize, Fail Over consists of failing over a replicated machine on a Target Core. During Fail over, protection of the machine is resumed by the Target Core. Fail Back consists of stopping the agent, archiving the protected data from the Fail Over period, importing the archive to the new or repaired Source Core, and restoring the changed data to new or repaired machines as needed.
It is recognized the Fail Back process may present gaps in production server up time / protection time. We have provided an alternate Fail Back method that will reduce downtime to almost zero for virtual environments and greatly reduce down time for physical machines by forgoing the archive process.
Alternate Fail Back Method:
This method allows continued up-time of production servers. It basically reverses the Failover method back to a new or repaired Source Core.