You are here: Recovering your source to the cloud > Recovering your source server

Recovering your source server

This process establishes the recovery of your source server from your backup repository server to your recovery server.

  1. Open the Double-Take Backup Console on the backup repository server by selecting Start, Programs, Double-Take, Backup, Double-Take Backup Console.
  1. Select Tools, Prepare Recovery Server.

  2. Specify the recovery server information, using the internal IP address of the server to prepare for recovery.

     

    Note:  The internal IP address is listed as the Private IP address on the server details page of the Double-Take Cloud console. To access the server details, click the recovery server name in the list of recovery servers on the Double-Take Cloud console Home page.

     

  3. Click Install.

  4. When the installation completes successfully, close the dialog box.

     

    Note:  If your recovery server is 64-bit architecture, you can disregard the installation error that instructs you to install Double-Take Backup again. This error is incorrect and Double-Take Backup has actually been installed.

     

  5. Click Recover in the left navigation pane.

     

    Note:  Do not select Recover from the toolbar. The toolbar option will not allow you to identify the correct backup repository server that contains the source server that you want to recover.

     

  6. Identify the backup repository server that you want to recover from by entering the internal IP address for the backup repository server. Do not use the 10.8.0.1 IP address.

     

    Note:  The internal IP address is listed as the Private IP address on the server details page of the Double-Take Cloud console. To access the server details, click the backup repository server name in the list of repository servers on the Double-Take Cloud console Home page.

     

  7. Click Next to continue.
  8. Select the image of the source that you want to recover. If you scheduled snapshots of the source, select the point-in-time strategy, if desired. Click Next to continue.
  9. Select the recovery server by entering the internal IP address of the recovery server. This is the same IP address from step 3 above.
  10. On the Choose image data to recover page, select Recover the entire server. This option recovers the entire source, including the system state, which is the server's operating system and configured applications. Click Next to continue.
  11. On the Set recovery type page, select WAN recovery, but do not select Update DNS Servers. Click Next to continue.
  12. Specify your recovery shutdown options. Ideally, you will want to disable Wait for user intervention before recovery so that the recovery process will not wait for a user response. If you are performing a test recovery, you should disable Shut down the source server. Click Next to continue.
  13. After Double-Take Backup validates the recovery server, click Next to continue.
  14. On the Recovery summary page, change the Route under Data transmission to the internal IP address of the recovery server. This is the same IP address from step 3 above.
  15. Click Finish to start your recovery. The Monitor jobs page will automatically appear with the recovery job. See the Double-Take Backup User's Guide for complete details on monitoring your job.

  16. When the recovery mirror has completed, the recovery server will automatically reboot to complete the recovery process. If you specified to pause the recovery, when the mirror is complete, the Activity will change to Recovery Paused. Use this time to complete any necessary tasks. When you are ready to complete the recovery, click Recover on the Monitor page toolbar to complete the recovery process. Once the recovery server has been rebooted, it will become the original source server.

     

    Note:  Because the Windows product activation is dependent on hardware, you may need to reactivate your Windows registration after recovery. Follow the on-screen prompts to complete the reactivation.

     

There are various tasks that can be run post-recovery in order to provide business continuity. For example, you may need to modify NIC properties on the new source (what was the recovery server), or you may need to update DNS. If you haven't already, be sure and modify any firewall settings on the new source (what was the recovery server) to allow connections to the server, such as SMTP: 25, HTTP: 80, HTTPS: 443, and so on.