Hyper-V Host Level Protection using Double-Take Availability

Hyper-V Host Level Protection using Double-Take Availability


The following video demonstrates how to protect Virtual Guest machines running on a Hyper-V virtual host, to another Hyper-V virtual host.
Replication is performed real-time, asynchronous and at byte-level.

Features:

* Manage the entire protection workflow (configuration, monitoring, failover, reverse protection) all from one console.

* Configuration performed from the Hyper-V host (hypervisor) level.

Benefits:

* Host Level Protection: Single instance of Double-Take Availability (Virtual Host Edition) installed at the hypervisor level, on source and target Hyper-V hosts, but provides the ability to protect multiple virtual guest machines on the virtual hosts.

* Flexible Topology: Protect a virtual guest machine from one Hyper-V host, to one or multiple Hyper-V hosts (one-to-one, or one-to-many). Or protect Hyper-V guest machines from multiple Hyper-V hosts to one Hyper-V host (many-to-one).


YouTube Video : Hyper-V Host Level Protection using Double-Take Availability

Hyper-V Hos
Figure 1: Hyper-V Protection and Failure

Hyper-V to Hyper-V Host Level Protection Requirements:

In addition to the core Double-Take Availability requirements, use these requirements for Hyper-V to Hyper-V protection.
  • Source and target host operating system—Your source and target host servers can be any Windows 2008 or 2008 R2 operating system from the core Double-Take Availability requirements that has the Hyper-V role enabled. In addition, you can use Hyper-V Server 2008 R2 or Server Core 2008 R2 with the Hyper-V role enabled. (Hyper-V Server 2008 and Server Core 2008 are not supported.) In each case, the source and target must be running identical operating system versions. For example, your source cannot be Windows 2008 and your target Windows 2008 R2.
  • Source and target host configurations—You can use one-to-one, many-to-one, or one-to-many configurations, however, you cannot use a chained configuration in a Hyper-V to Hyper-V to Hyper-V scenario.
  • Clusters-Clustered Hyper-V servers running Windows 2008 R2 are supported on the source and target.
  • Guest operating systems—The guest operating system can be any operating system. However, if you want Double-Take Availability to monitor the virtual machine for failover, then you must have Integration Components installed on the guest operating system and the virtual machine must be powered on.
  • Virtual machine configurations—The following limitations apply to the virtual machines on the source and target Hyper-V servers.
  • The virtual machines must be in their own home folder that is not shared by any other virtual machines.
  • The virtual machines cannot be created in or replicated to the Hyper-V system default folder.
  • The virtual machines' snapshot folder must be unique to each virtual machine, they cannot be in the Hyper-V system default folder, and they cannot be changed once protection has been established.
  • The virtual machines cannot use raw, pass-through, or differencing disks.
  • WAN support—If your source and target are across a WAN and you want Double-Take Availability to automatically update networking on the guest operating system during failover, the following limitations apply. If you choose not to have Double-Take Availability automatically update networking on the guest operating system during failover, you will have to update the network manually, but the following limitations will not apply.
  • Guest operating system—The guest operating system must be Windows 2003 or Windows 2008.
  • Windows Management Instrumentation (WMI)—The host and guest operating systems must have the WMI service enabled.
  • User Access Control (UAC)—UAC must be disabled on the guest operating system.
  • Name resolution—You must establish name resolution for the guest operating system.
  • Ports—In addition to the standard Double-Take Availability ports that must be opened, you must also open port 135 for communication between the client and the servers.
  • Microsoft .NETFramework—The source and target servers require the Microsoft .NET Framework version 3.5 Service Pack 1. 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 Availability CD, via a web connection during the Double-Take Availability installation, or from a copy you have obtained manually from the Microsoft web site.
  • Server Core—If you are installing on Server Core 2008 R2, .NET3.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 Availability. See your Server Core documentation for the specific commands to enable the .NETfunctionality.



Article ID: SLN310454

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


Rate this article

Accurate
Useful
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.