Disaster recovery procedures

This section provides information on bringing up an application server on the secondary host, in the event of a disaster. It also explains how to migrate the primary role back to the original primary host once it is returned to normal functioning after a disaster.

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 the desired secondary RVG node inside the replication network.
  2. Select Takeover and follow the instructions to perform the takeover operation. You can choose to perform takeover with the following options:
    • Perform Takeover with the 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 Takeover without the fast-failback option. In this case, you will 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 the takeover, the existing secondary becomes the new primary.

  3. Assign drive letters to the volumes on the new primary. Make sure that these drive letters are the same as those of the original primary.
  4. Bring the application group online.

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