Bringing up the application on the secondary host

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

  1. From the left-pane in the VEA GUI console on the Secondary host, right-click on the desired secondary RVG node inside the replication network.
  2. Select Takeover and follow the instructions in the wizard to perform the takeover operation.

    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.

  3. Assign drive letters to the volumes on the new Primary. Ensure that these drive letters are the same as that of the original Primary.
  4. Bring the SQL group online.
  5. Attach the databases. See the Microsoft documentation for instructions.

    Now you can start using the application on the new Primary.