HP MSA 2040 SAN Storage - Manual (Page 15)

: Failover and failback 15
Reprotection
After a recovery plan or planned migration is executed, there are often cases where the environment must
continue to be protected against failure in order to ensure its resilience or to meet all disaster recovery
objectives.
With SRM 5.0 or greater, reprotection is a new extension to recovery plans for use only with array-based
replication. It enables the environment at the recovery site to establish synchronized replication and
protection of the original environment.
After failover of the recovery site, choosing to reprotect the environment will establish synchronization and
attempt to replicate the data between the protection groups running at the recovery site and at the
previously protected primary site.
This capability to reprotect an environment ensures that environments are protected against failure even
after a site recovery scenario. It also enables automated failback to a primary site following a migration
or failover.
Automated failback
An automated failback workflow can be run to return the entire environment to the primary site from the
recovery site.
This will happen after the reprotection has ensured that data replication and synchronization are
established to the original primary site.
Failback will run the same workflow that was used to migrate the environment to the protected site. It will
ensure that the critical systems encapsulated by the recovery plan are returned to their original
environment. The workflow will execute only if reprotection is successfully completed. Failback is only
available with array-based replication.
Failback ensures the following:
• All virtual machines that were initially migrated to the recovery site will be moved back to the primary
site.
• Environments that require that disaster recovery testing be done with live environments with genuine
migrations can be returned to their initial site.
• Simplified recovery processes will enable a return to standard operations after a failure.
• Failover can be done in case of disaster or in case of planned migration.