After a disaster, if the original Primary becomes available again you may want to revert the role of the Primary back to this host.
To restore the Primary role to the original Primary host
Note that the master, model, and tempdb, databases cannot be detached.
Depending on whether you performed Takeover with or without fast-failback option, do one of the following:
For Takeover with the Fast-failback option, the original Primary, after it has recovered, will be in the Acting as Secondary state. If the original Primary is not in the Acting as Secondary state, verify whether your network connection has been restored.
To synchronize this original Primary and the new Primary, use the Resynchronize Secondaries option from the right-click menu of the new Primary.
For Takeover without the Fast-failback option, after you have performed this operation, you must convert the original Primary to a Secondary using the Make Secondary option.
Before performing the Make Secondary operation, the original Primary's RVG and the new Primary's RVG will be shown in separate RDSs. However, after this operation they will be merged under a single RDS.
After the Make Secondary operation, the original Primary will be converted to a secondary. Right-click this secondary RVG and select Start Replication with Synchronize Automatically option.