Home > Storage > PowerMax and VMAX > Storage Admin > Implementing Dell SRDF SRA with VMware SRM > Failback
An automated failback workflow can be run to return the entire environment to the primary site from the secondary site. This will happen after reprotection has ensured that data replication and synchronization have been established to the original site.
Failback runs through the same workflow that was originally used to migrate the environment to the recovery site - planned migration. It guarantees that the critical virtual machines encapsulated by the failed-over recovery plan are returned to their original environment. The workflow will execute only if reprotection has successfully completed.
Failback ensures the following:
Failback is no different in its execution or behavior than the original failover operation as seen in Figure 179. Before failback can occur, valid protection groups and recovery plans must be created or re-configured through a reprotect operation or manual creation by the user.
Once failback is complete, it is still necessary to run a reprotect on the primary site.
Since failback is in practice no different than failover, the process will not be discussed any further in this chapter.
For Cascaded RDF configurations that have been recovered to the tertiary site, reprotect and consequently also failback is not supported from with SRM. For instructions on manual failback procedures of this configurations, refer to section Manual Reprotection/Failback of Cascaded SRDF after recovery to tertiary site.