Show Hide

 

Feedback

  • Contents
 

Third Server Disaster Recovery Site Scenario

Scenarios where a Switchover pair exists at a primary site, with a third backup server at a Disaster Recovery (DR) site are becoming more common. You can use Interaction Migrator in a third server disaster recovery site scenario in an automated fashion to back up the configuration of one of the servers in the Switchover pair to the remote DR site.

Note: If the DR server has a different server name than either of the CIC servers in the Switchover pair, use Interaction Migrator’s Migration mode instead of Recovery mode.

Following are the steps for this scenario.

Implementation/Testing Phase

  1. Set up server completely, short of importing configuration.

  2. Image Server. Call this Image1.

  3. Import newest Migrator Data and test.

If anything does not test correctly and requires a configuration change that should have been in Image1, do the following:

  1. Restore CoreImage.

  2. Change configuration.

  3. Make new CoreImage.

  4. Import Migrator Data again and retest.

  5. Complete cycle until CoreImage works fine.

    Note: CoreImage contains no configuration. It is ready for you to apply configuration.

Maintenance Phase

  1. Record all changes to production servers that need changed on the DR server.

  2. On a scheduled interval:

    1. Take list of items proven in production not to cause issues as a task list.

    2. Back up CoreImage to CoreImage_<date>.

      If something goes wrong, you have a great audit trail of past task lists that you applied (keep those lists for long-term tracking) and you can go back to an older CoreImage:

    3. Restore CoreImage.

    4. Apply task list.

    5. Make new image to replace CoreImage (remember, you backed it up before this step).

    6. Import newest Migrator Data.

If something does not test correctly and requires a configuration change that should have been in Image1, do the following:

  1. Restore new CoreImage made in step (e).

  2. Change the configuration.

  3. Make a new CoreImage to replace the one made in step (e).

  4. Import Migrator Data again and retest.

  5. Complete cycle until CoreImage works fine.

Disaster recovery plan

  1. Examine the list of production changes since updating the last image to create a task list. You can implement all or any of these changes. Examine each as a potential issues list.

  2. Restore CoreImage.

  3. Apply anything from the task list that you need.

  4. Import newest Migrator Data and test.