After a real failover, the DR site becomes the new production site. When the original PROD site returns to service, the administrators may decide to continue to run the production applications on the DR site, designating it as the new PROD site. The roles will be reversed and the original PROD site will now become the DR site. What remains to be done is to reverse the replication direction and re-protect the new PROD site.
-
Stop the applications and databases on the original PROD, if not done already
-
Demote the original PROD pod using the skip quiesce option, if not done already
Whenever we demote a pod that is the source of a replica link, if the other pod is promoted, ActiveDR will automatically reverse replication, ensuring that the new application data at the other site is protected as quickly as possible. This eliminates risks associated with manual processes and automates the reversal of replication relationships. Automatic replication reversal does not happen during DR tests because the DR test pod is the target, not the source, of the replica link.
Demoting the original source pod will also save a temporary copy of the source pod content (prior to replication reversal) in the recycle bin for 24 hours. If needed, you can clone the .undo pod so that you can recover any data written but not replicated before the outage.