Tutorials

Migrate a Windows Server using Double-Take

REQUIRED TO PROCEED:

  • Double-Take Move software and license. For the purposes of this demonstration, a Double-Take Availability trial license will be used as both products have the same underlying engine. The main difference is that Double-Take Move is meant for server migrations (only source server is licensed) versus Double-Take Availability which is meant for Disaster Recovery (source and target need to be licensed).
  • A Source machine running Windows Server 2003SP2 - 2012 R2.
    • Optional - A running application for verification purposes after the migration.
  • A Target machine running at ProfitBricks matching the base Operating System of the Source
    • Intel to AMD (or vice versa) is supported.
    • CPUs and RAM can be adjusted to meet your needs.
    • Identical number of drives with sufficient space.
  • A Third-Machine running Windows in order run the Double-Take Console (Command and Control).
  • Network connectivity among the three machines mentioned above.
  • Internet access for license activation.

Double-Take Move:

  • YouTube Video - Link here
  • Documentation (v7.1.0) - Link here

Double-Take Availability:

  • YouTube Video - Link here
  • Documentation (v7.1.0) - Link here

INSTRUCTIONS:

  1. Below is a snapshot of the ProfitBricks environment. In this scenario, a SOPHOS UTM is being used to provide site-to-site connectivity to a third-party site. There are also two freshly installed Windows Server 2012R2 machines (ProfitBricks image). One will be used for the console and the second machine as the target.

    DCD Setup

  2. Make a note of your ProfitBricks server IP addresses. My environment is configured as follows:

    • Source Server IP: 10.10.0.20
    • Target Server IP: 192.168.0.20
    • Management Server IP: 192.168.0.10
  3. Install the Double-Take Console on your Management Server. Launch the Double-Take installation wizard and perform the following steps:

    • Select Double-Take Availability (due to the trial license).
    • Click Yes, check for an updated version (Recommended).
    • Accept the License Agreement and click Next.
    • Read the License Activation information and click Next.
    • Select Client Components Only (aka Console) and click Next.
    • Leave the defaults for the Firewall configuration and click Next.
    • Click the Install button the begin the software installation.
  4. Copy the Double-Take installation package to both, source and target servers. Launch the Double-Take installation wizard and perform the following steps:

    • Select Double-Take Availability (due to the trial license).
    • Click Yes, check for an updated version (Recommended).
    • Accept the License Agreement and click Next.
    • Read the License Activation information and click Next.
    • Select Server Components Only and click Next.
    • Leave the defaults for the Firewall configuration and click Next.
    • Enter your license key and click Next.
    • Review the queue options. For this demonstration, defaults will work. Click Next.
    • Click Next on the Security Groups Information.
    • Click the Install button the begin the software installation.

    NOTE: It is possible to push-install the server components from the console instead of manually performing all of the steps described in #4 above. This requires WMI (which uses RPC) to be open as well as SMB (server message block) which uses 135-139 and port 445. See the User's guide for additional requirements.

  5. Once the Double-Take software has been installed, launch the Double-Take Console. From the Double-Take console, Click the Add Servers button as highlighted below.

    Double-Take Add Servers

  6. In the Add Servers wizard, enter the corresponding information for both, source and target servers and click OK. A sample screenshot is shown below:

    Double-Take Add Servers Wizard

  7. At this point, servers will be discovered and displayed on the Manage Servers screen with an "Idle" state as depicted below:

    Double-Take Servers Added

  8. The next step is to add the license(s). Click on the Manage License button located on the top menu bar followed by the "+" button to add a new license as shown below.

    Double-Take Add Licenses

  9. The Add Licenses window will pop-up. Enter your license(s) and hit the Add button.

  10. Click on the Manage Servers button located on the top navigation bar to go back to the list of servers that were previously added.

  11. Right-click the source server and select "View Server Details" from the pop-up menu as shown below.

    Double-Take View Server Details

  12. Click on the "Edit server properties" under the Tasks menu located on the right hand side.

    Double-Take Edit Server Properties

  13. Expand the Licensing drop-down. Click the "Choose..." button and select the appropriate license key. Click on the "Add" button to add it to the current license keys for this server. Click OK to close the Server Properties window.

    Double-Take Assign Licenses

  14. Repeat the previous step for the target server to license it. Both servers will display the license details as depicted below.

    REMEMBER: As mentioned at the beginning of this tutorial, a Double-Take Availability trial license is being used for this demonstration given that it utilizes the same underlying software engine as Double-Take Move. Double-Take Availability is mainly used for ongoing Disaster Recovery protection and hence both source and target need to be licensed. Double-Take Move only requires the source server to be licensed.

    Double-Take License Status

  15. It is now time to create a replication job. Click on the "Get Started" button located on the top navigation menu and select "Double-Take Availability". Click Next.

    Double-Take Get Started

  16. Select "Protect files and folders, an application, or an entire Windows or Linux Server". Click Next.

    Double-Take Get Started 02

  17. Select your source server. Click Next.

    Double-Take Get Started 03

  18. Select Full Server on the Workload type. Click Next.

    Double-Take Get Started 04

  19. Select your target server. Click Next.

    Double-Take Get Started 05

  20. The Next Screen will have several configuration options for the job. Review the options and configure according to your needs. In this scenario, the configuration will be as follows:

    • General - Job Name: DT-SRC-2012R2 to DT-Target-2012R2
    • Failover Identity: Retain target network configuration (Recommended for WAN configuration)
    • Reverse Protection: Disable reverse protection
    • Compression: Enable (Medium)
    • Bandwidth: Do not limit bandwidth - just for fun :-)

    Double-Take Get Started 06

  21. The next screen will run some verification checks and provide a summary.Review this checklist and ensure all items have passed the requirements check. Click Finish to create the job.

    Double-Take Get Started 07

  22. The Full Server Failover job will begin. The status may briefly show as error but should move to a warning state fairly quickly. This means that synchronization is in progress and the source server is not fully "protected". Review the progress and other details such as mirror remaining, bytes sent, etc.

    Double-Take Job Status

  23. Once the source and target servers are fully synchronized, the Activity state will show as "Protecting". At this point, right click the job and select "Failover, Cutover, or Recover..."

    Double-Take Failover 01

  24. Click on the "Failover to live data" and leave the default to "Apply data in the target queues before failover or cutover". Click on the Failover button to being the cutover process.

    Double-Take Failover 02

  25. During the actual test performed for this demonstration, the failover (after the initial synchronization) took approximately ~5 minutes for the target server to reboot with the identity of the source server. It is worth mentioning that the only application that was running on the source server was WAMP (Windows Apache MySQL PHP) so there were not a lot of applications installed on the source server.

  26. Once the job has completed. The Activity state will show as Failed over.

    Double-Take Job Failed over

  27. At this point, it is recommended to uninstall any legacy drivers (VMWare tools, etc.) and verify the integrity of the server.

NOTE: There may be a chance that the target server will require Windows activation. It depends on how the source server was licensed (KMS, MAK, etc.) as well as whether Windows will consider that there has been a significant change in the hardware. If you are prompted to activate windows and have a windows activation key, go ahead and license the server. If you prefer to use the ProfitBricks licensing model, please contact our support team for assistance.

 
  • Nice post thanks for the nice post you will play this game once time this game play the many user all session bloons towers defense 5 games you will play this game and create a high score forever.

Log In, Add a Comment