CenturyLink Cloud Guide to Double-Take DR

Updated by Gavin Lai on Nov 16, 2015

Table of contents


Double-Take DR allows customer to have a DR environment setup with a few easy steps. By utilizing the Vision Solutions created Blueprint in CenturyLink Cloud, this further simplifies the deployment process.

Before deploying any software, a DR plan needs to be in place. Depending on the business requirement, the server can be mirrored and replicated from on premise infrastructure to CenturyLink Cloud, CenturyLink Cloud to CenturyLink Cloud or CenturyLink Cloud to another location. In this walk through, a one to one scenario is used for the Double-Take DR for Windows, which can be expanded to many to many. For detail of the products, please see Vision Solutions website.


Use Case

For ease of management, a Double-Take Management Console software is the user management interface for all Double-Take products. Double-Take DR can mirror and replicate any server to any server, using it to create an easy to deploy DR environment either a one to one or many to many environment without costly infrastructure.
In Double-Take DR product, there are minimum three servers, the source server, the repository server and the target server

  • The Source Server is the server requires DR
  • The Repository Server is used to store the data server images
  • The Target Servers are the servers built for disaster recovery (see below) DT DR blockdiagram

Starting with the Blueprint, apply the appropriate license to the server during the Blueprint setup. Please see the Getting Started with Double-Take Blueprint for details of licensing request.


In preparation, there are several factors need to be considered:

  • Verify the Windows version on the source server is supported by Double-Take
  • Currently Double-Take Blueprints are available on CentOS 5/6, RHEL 5/6 and Microsoft Windows 2008 R2 and 2012 R2
  • Bandwidth and connectivity between Source Servers and Repository Server
  • Double-Take Console (for management) is part of the Windows Blueprint installation


For this example, the source server is running Windows 2012 R2.

Multiple Windows servers require a central offsite disaster recovery to meet the business requirement. By using Double-Take Disaster Recovery product and CenturyLink Cloud Blueprints, this can be done in a few steps with an easy to understand costing model.


If there an existing Double-Take Console installed and have network access to all Source, Repository and Target servers, then it can be used instead of creating new one. For a new installation of Double-Take Management Console, please use the following steps:

  1. Deploy Double-Take Console on a VM in CenturyLink Cloud by running the Double-Take Windows Blueprint from the blueprint library, for this scenario, it could reside on the same sever as the Repository server

  2. Once installed, start the Console from the “Start’ Menu

    DT console icon

  3. This will be the management interface to set up the DR environment

    DTconsole UI

    Once in the Management Console, go to ‘Help’ and ‘Check for Updates’ and install any updates available

    DT console update

Repository Server

Using the steps below to create the Repository Server in CenturyLink Cloud:

  1. Create the Repository server by running the Double-Take Blueprint on Windows 2012 R2 from the Blueprint library, enter the Double-Take DR for Windows Repository license in the Blueprint configuration screen

    DT blueprint Windows2k12

    DT blueprint license Windows2k12

  2. Once Blueprint is completed, the new server can be managed from the Double-Take Console by clicking on ‘Get Started’ and ‘Add Servers’ DT console add servers

  3. Enter the IP address or hostname, user name and password in the prompt: DT console add servers 2

  4. The ‘Manage Servers’ screen will show the status of the management connectivity

    DT console DR manage repository server

  5. The server details can be seen by double clicking the server DT console DR Repository server details

  6. The Double-Take Repository server has been created successfully, it will be use as the central storage for many Source Servers as DR target. The detail user guide for Double-Take DR is located here

Source Server

Important Note: make sure Remote Desktop Services and ping is enabled on the Source Server as this is part of the requirement to Import server to CenturyLink Cloud (please see Self Service VM import OVF requirement knowledge article). There are two way of installing Double-Take software on the source server, either by downloading from Vision Solutions website or from the Double-Take Management Console.

Install Double-Take DR on the Source Server using the Double-Take Management Console

  1. To manage the new server from the Double-Take Console by clicking on ‘Get Started’ and ‘Add Servers’

    DT console add servers

  2. Enter the IP address or hostname, user name and password in the prompt

    DT console add servers 2

  3. The source server will appear on the managed server list with ‘Cannot Connect to Double-Take’ activity

    DT console manage servers

  4. Right click on the source server and click on ‘Install’

    DT console install Double-Take

    The ‘Install’ screen will give the installation option, like temporary directory, installation path as well as schedule of the installation

    DT console install Double-Take 2

    DT console install Double-Take 3

  5. The ‘Manage Server’ screen will display the status of the installation, once completed, the source server will have ‘idle’ status and license status displayed DT console DR manage servers idle

  6. The server details can be seen by double clicking the server

    DT console DR source server details

    Under ‘Edit Server Properties’, the network traffic can be encrypted for all Double-Take activities

    DT console DR source server properties

Setting up the DR mirroring and replication

  1. Click on ‘Get Started’ from the Double-Take Management Console and pick ‘Double-Take DR’

    DT console DR get started

  2. Choose the ‘Protect files and folders or an entire Windows server’ from the next screen

    DT console DR protect

  3. Pick the server that need to be protected

    DT console DR source server

  4. Choose the data on this server that needed protection, this could be a data directory or a whole server

    DT console DR choose data

    DT console DR choose data 2

  5. Next is choose the target Repository server

    DT console DR repositoryserver

  6. Set options for this replication

    • Location of the Virtual Disk Path (ensure enough disk space for the images)

      DT console DR options disk

    • Mirror Verify and file management options

      DT console DR options mirror

    • Snapshot schedules, Compression, Bandwidth (depends on the connectivity between Source and Repository) options and any customized scripts can be configured here

      DT console DR options network

    • Summary will report any issue with the checklist

      DT console DR source summary

  7. Jobs can be managed and monitored from the ‘Managed Jobs’ screen

    DT console DR manage jobs source

  8. Double Click on the job to see the ‘Job Detail’

    DT console DR job details source

  9. The synchronization will continue until is completed

    DT console DR job highlights source

    DT console DR manage servers source

Creating a Target Server

Similar to building the Repository server in the previous step, utilizing CenturyLink Cloud Blueprint to create the target server in the desired datacenter using Getting Started with Double-Take Blueprint

DT blueprint license Windows2k12

The Double-Take license required for this node is ‘Double-Take DR For Windows Recovery Target’

  • Once completed, the server can be managed from the Double-Take Management Console by ‘Add Servers’

    DT console add servers

    DT console add servers 2

Creating the Recovery Job

  1. Click on ‘Manage Jobs’ and select ‘Create a New Job’ or ‘Get Started’

    DT console DR manage jobs new job

  2. Choose Double-Take DR

    DT console DR get started

  3. In order to recover data or entire server, select ‘Recover files and folders or an entire Windows server’

    DT console DR recover

  4. Pick the Source Repository Server and the Image to Recover

    DT console DR choose source

  5. Choose Source Image to Recover, it can be done from a live image or a previously captured snapshot

    DT console DR choose image

  6. Choose to recover data or entire server

    DT console DR choose data recover

  7. Choose the newly created server as the target server

    DT console DR choose target

  8. Next is to customize the options for the recovery job, please do NOT change the network information in ‘Recovery Identity’ section on the target server as this will lead to lose access to the server in CenturyLink Cloud

    DT console DR options recover

    DT console DR options recovery ID

    DT console DR options recover network

  9. Make sure the job meets all the requirement from the checklist

    DT console DR options recover summary

  10. Click on ‘Finish’, the ‘Manage Jobs’ screen will show the job has been submitted

    DT console DR managejobs recovery

  11. Once completed, the status on the job will turn green and it can be used as a recovery server DT console DR manage jobs recovery completed

Perform a Test fail over

  • Create a snapshot of the target server from the Control Portal (Creating and Managing Server Snapshots knowledge article), API or CLI for recovery or rebuild the test node with the procedure Creating a Target Server

    DT-CenturyLink Cloud-snapshot

  • From ‘Manage Jobs’ screen, right click on the replication job from the Repository Server to the Target Server and choose ‘Failover, Cutover or Recover’

    DT console DR fail over

  • Choose how to apply the target data

    DT console DR fail over options

  • The Failover has started

    DT console DR fail over started

  • Depending on size and bandwidth, the time required for this process can be varied. Once completed, the Target Server is rebooted and becomes a copy of the Source Server

Health Check

  • Once the server is running, please ensure the password is identical to the one defined in the Control Portal to ensure the server operates correctly.
  • Please review the following list to complete the installation:

    1. Check if VMware tool is installed
    2. Windows can be activiated via a support ticket or the following commands

       slmgr /skms
       slmgr /ato
    3. Make sure the password on the server matches the one in the Control Portal

    This process can be used to create DR for multiple servers using the existing Repository Server. The target server can be created at the time of disaster, this means there is not ongoing cost to maintain the running Target Servers as they can be created on demand for both testing and disaster recovery purposes.
    This procedure can be repeated to set up multiple servers in a complex environment and managed from the Double-Take Management Console. For multi-tiers application environment, either using built-in script function or a manual failover can control the start up sequence of the new environment.