Open topic with navigation

Full server to Hyper-V migration requirements

After you have verified your source server meets the Requirements, verify that your target server meets the requirements below for full server to Hyper-V migration.

• Operating system—You must have a physical Hyper-V host machine, where Double-Take can create the new virtual server, that meets the following requirements.
• Your physical Hyper-V host machine can be any Windows 2008 or 2008 R2 operating system from the 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.)
• If you are using Hyper-V Integration Services and your source is running Windows 2003, the source must have Service Pack 2 or later.
• The virtual machines cannot use raw, pass-through, or differencing disks.

• System memory—The minimum system memory on each server should be 1 GB. The recommended amount for each server is 2 GB.

• Disk space for program files—This is the amount of disk space needed for the Double-Take program files. For Windows 2003, this is approximately 300 MB. For Windows 2008, this is approximately 375 MB.

  The program files can be installed to any volume while the Microsoft Windows Installer files are automatically installed to the operating system boot volume.

  Make sure you have additional disk space for Double-Take queuing, logging, and so on.

   

• Disk space for data files—This is the amount of disk space needed for the source data files. This will be dependent on the applications you are running and the amount of data files you have.

• Disk space for system state image—This is the amount of disk space for the image of the source system state. The size of the system state will depend on the operating system and architecture. Windows 2003 operating systems need at a minimum 2-3 GB of free space for the system state. Windows 2008 operating systems need at a minimum 7-9 GB of free space for the system state. Windows 2008 R2 operating systems need 10 GB of free space for the system state. These minimums are for a clean operating system installation. Operating system customizations will increase the disk space requirement.

• Server name—Double-Take includes Unicode file system support, but your server name must still be in ASCII format. If you have the need to use a server's fully-qualified domain name, your server cannot start with a numeric character because that will be interpreted as an IP address.

• Protocols and networking—Your servers must meet the following protocol and networking requirements.

  • Your servers must have TCP/IP with static IP addressing. (Some job types allow you to add DHCP addresses for failover monitoring, although only after a job has already been created. Keep in mind that depending on your failover configuration, a source reboot may or may not cause a failover but having a new address assigned by DHCP may also cause a failover.)
  • By default, Double-Take is configured for IPv6 and IPv4 environments, but the Double-Take service will automatically check the server at service startup and modify the appropriate setting if the server is only configured for IPv4. If you later add IPv6, you will need to manually modify the DefaultProtocol server setting. See Server and job settings for details.
  • IPv6 is only supported for Windows 2008 servers.
  • If you are using IPv6 on your servers, your clients must be run from an IPv6 capable machine.
  • In order to properly resolve IPv6 addresses to a hostname, a reverse lookup entry should be made in DNS.

• Microsoft .NET Framework—Microsoft .NET Framework version 3.5 Service Pack 1 is required. 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.

• Supported configurations—The following table identifies the supported configurations for a full server to Hyper-V migration job.

  Configuration		Supported	Not Supported
  Source to target configuration	One-to-one, active/standby	X
  	One-to-one, active/active		X
  	Many-to-one		X
  	One-to-many		X
  	Chained		X
  	Single server		X
  Server configuration	Standalone-to-standalone	X
  	Standalone-to-cluster		X
  	Cluster-to-standalone		X
  	Cluster-to-cluster		X
  	Cluster Shared Volumes (CSV) guest level	X
  	Cluster Shared Volumes (CSV) host level		X
  Upgrade configuration	Upgrade 5.2 Double-Take Move Console server migration job to 6.0 Double-Take Console full server to Hyper-V migration job		X
  	Upgrade 5.3 Double-Take Move Console provisioned migration job to 6.0 Double-Take Console full server to Hyper-V migration job		X

Related Topics