Full Server Protection of W2008 R2 Server Core using Double-Take Availability 6.0

Full Server Protection of W2008 R2 Server Core using Double-Take Availability 6.0

The following video demonstrates how to protect a Windows Server 2008 R2 (Server Core) to a standby Server, using the "Full Server Failover" protection option of Double-Take Availability 6.0.

Though this demo is conducted on a Server Core OS, the same Double-Take workflow applies for protecting servers running non-core versions of Windows Server (2008, 2008-R2 or 2003, 2003-R2). Applications running on protected servers (such as SQL Server, MS-Exchange, Oracle) are replicated and protected as part of the full server protection job and are fully available for use on the target server following fail-over... just as they were on the source server prior to fail-over.

The demonstration specifically details:

1) Configuring Double-Take Availability with a Full Server Protection job
2) Synchronize data from source server to target server
3) Monitor the Double-Take job
4) Fail-over from source server to target server
5) Invoke Reverse Protection while failed over
6) Fail-over to original source server


YouTube Video : Double-Take Availability 6.0
Double-Take Full Server Protection Requirements

In addition to the Core Double-Take requirements (see User Guide), use these requirements for full server protection.
  • Operating system—The source and target servers can be any operating system listed in the Core Double-Take requirements section of the User Guide. However, keep in mind that a target server may meet these requirements but may not be suitable to stand-in for a source in the event of a source failure. See Target compatibility for additional information regarding an appropriate target server for your particular source.
  • Operating system language—Your servers must be running the same Windows localized version. For example, if your source is running an English language version of Windows, your target must also be running an English language version of Windows. If your source is running a Japanese language version of Windows, your target must also be running a Japanese language version of Windows. This applies to all localized languages.
  • Source and target preparation—Uninstall any applications or operating system features that are not needed from both your source and target. For example, unused language packs will slow down failover since there are thousands of extra files that need to be examined.
  • Storage Server Edition—If you are using Windows Storage Server Edition, you will need to check with your NAS vendor to verify if there are technical or license restrictions on failing over an image of a server to different hardware.
  • Microsoft Server Core 2008 R2—This operating system is only supported in a Server Core to Server Core configuration.
  • Hyper-V servers—Full server protection of a Hyper-V server is not supported.
  • Network adapters—NIC teaming is not supported for full server protection.
  • Double-Take licensing—If you are protecting a full server in a physical source to virtual target configuration, you will be unable to reverse if your virtual target has a Double-Take Availability Virtual Guest Edition license. If you want to reverse, you will need to have one of the other (non-virtual) Double-Take Availability licenses.
  • Microsoft .NET Framework—Microsoft .NET Framework version 3.5 Service Pack 1 is required on the source and target. This version is not included in the .NET version 4.0 release. Therefore, even if you have .NET version 4.0 installed, you will also need version 3.5.1. You can install this version from the Double-Take CD, via a web connection during the Double-Take installation, or from a copy you have obtained manually from the Microsoft web site.
If you are installing on Server Core 2008 R2, .NET 3.5.1 functionality is included with the operating system but is disabled by default. You will need to enable it prior to installing Double-Take. See your Server Core documentation for the specific commands to enable the .NET functionality.

Article ID: SLN310458

Last Date Modified: 08/14/2018 03:49 AM

Rate this article

Easy to understand
Was this article helpful?
Yes No
Send us feedback
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.

Thank you for your feedback.