Use the following procedure to bring up SQL Server on the secondary host if a disaster recovery scenario occurs on the primary host.
To bring up the application on the secondary host
You can choose to perform takeover with the following options:
Perform the Takeover with fast-failback option to restore the original Primary easily once it becomes available again. When performing Takeover with fast-failback, make sure that you do not select the Synchronize Automatically option.
Perform the Takeover without fast-failback option. In this case, you need to perform a complete synchronization of the original Primary with the new Primary. This may take quite a while depending on the size of the data volume. Only after the synchronization is complete can you migrate the Primary role back to the original Primary.
After takeover, the existing Secondary becomes the new Primary.
Now you can start using the application on the new Primary.