Open topic with navigation
Source server requirements
This is the server that contains the data you will be migrating.
- Operating system—The source server can be a physical or virtual server running any of the following operating system editions.
- Windows Server 2008 or 2008 R2 Datacenter, Enterprise (x86, x64), Standard (x86, x64), Essential Business Server, Web Server, Foundation Server, Small Business Server, or Storage Server Edition
- Windows Server 2003 or 2003 R2 Datacenter, Enterprise (x86, x64), Standard (x86, x64), Web Server, Small Business Server, or Storage Server Edition. Each of the Windows 2003 operating systems require Service Pack 1 or later.
- File system—Double-Take Move supports the same file system formats that Microsoft supports: FAT, FAT32, and NTFS.
- System memory—There are different memory requirements depending on the system architecture you are using. Be sure you have at least the minimum amount of memory for your environment. You should consider having at least the recommended amount of system memory.
- i386 operating systems—The minimum system memory is 1 GB.
- x64 operating systems—The minimum system memory is 1 GB. The recommended system memory is at least 2 GB.
- Disk space for program files—This is the amount of disk space, approximately 130 MB, needed on the source to hold the Double-Take Move program files.
- Server name—Double-Take Move includes Unicode file system support, but your server name must be in ASCII format.
- Network protocols—Your servers must use TCP/IP with static IP addressing.
- Microsoft .NET Framework—Microsoft .NET Framework version 3.5 Service Pack 1 is required on the source. 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 Move CD, via a web connection during the Double-Take Move installation, or from a copy you have obtained manually from the Microsoft web site.
- Junction points—Only domain controller junction points will be replicated. Any user-created junction points will be replicated as two unlinked copies of the data.
Related Topics