Open topic with navigation

Data migration requirements

After you have verified your source server meets the Requirements, verify that your target server meets the requirements below for data migration.

• Operating system—Your existing physical or virtual target server can have any of the following Windows operating system editions.

• Windows Server 2003 or 2003 R2 Datacenter, Enterprise (i386, x64), Standard (i386, x64), Web Server, Small Business Server, or Storage Server Edition. Each of the Windows 2003 operating systems require Service Pack 1 or later.

• Windows Server 2008 or 2008 R2 Datacenter, Enterprise (i386, x64), Standard (i386, x64), Essential Business Server, Web Server, Foundation Server, Small Business Server (including SBS 2011), or Storage Server Edition

• Windows 2012 Datacenter, Standard, Essentials, or Foundation Edition

• Microsoft Server Core 2008 R2 and 2012 are supported for mirroring, replication, and cutover.

• 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. The amount depends on your operating system version and your architecture (32-bit or 64-bit) and ranges from 350-500 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.

• 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. Additionally, all Double-Take servers and appliances must have a unique server name.

• 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.

  • IPv4 and IPv6 are both supported.

  • IPv6 is only supported for Windows 2008 and 2012 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.

• NAT support—Data migration jobs can support NAT environments in an IP-forwarding configuration with one to one port mappings. Port-forwarding is not supported. Additionally, only IPv4 is supported for NAT environments. Make sure you have added your servers to the Double-Take Console using the correct IP address. Review the NAT configuration table in the Adding servers section before you start the job creation process.

• 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. For Windows 2008 and earlier, you can install this version from the Double-Take DVD, via a web connection during the Double-Take installation, or from a copy you have obtained manually from the Microsoft web site. For Windows 2008 R2 and later, you need to enable it through Windows features.

• Cloud—Double-Take can be used to migrate data to an existing server in the cloud. Keep in mind that you should enable appropriate security measures, like VPN, to protect your data as it migrates to the cloud.

• Supported configurations—The following table identifies the supported configurations for a data 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.3 Double-Take Move Console data migration job to 7.0 Double-Take Console data migration job		X
  	Upgrade 6.0 data migration job to 7.0 data migration job	X

Related Topics