After a successful takeover operation, the secondary cluster becomes the primary for the protection group and the services are online on the secondary cluster. After the recovery of the original primary cluster, the services can be brought online again on the original primary by using a process called failback. The protection group on the original primary cluster has either the primary role or secondary role depending on whether the original primary cluster can be reached during the takeover from the current primary cluster.
The disaster recovery framework software supports the following kinds of failback:
Failback-switchover - During a failback-switchover, applications are brought online again on the original primary cluster after the data of the original primary cluster is resynchronized with the data on the secondary cluster.
Failback-takeover - During a failback-takeover, applications are brought online again on the original primary cluster and the current data is used on the original primary cluster. Any updates that occurred on the secondary cluster while it was acting as primary are discarded.
You can check for the status with the following command:
# geoadm status
The recovery after a takeover involves the following actions:
Configuring the original primary cluster to run as a secondary cluster.
Manually starting the extracts and replicats on the original primary cluster.
Resynchronizing the protection group to switch the role.