You are here: Double-Take Backup requirements > Recovery server requirements

Recovery server requirements

This is the server that will become your new source when you are recovering an entire server. This server can be an existing physical or virtual machine or Double-Take Backup can provision (automatically create) a virtual machine for you during the recovery process.

Operating system—You have several options for your recovery server operating system.
Physical or existing virtual—If your recovery server is a physical server or an existing virtual server, it can have any of the following Windows operating system editions. A physical or existing virtual recovery server must have the same operating system as the original source.
Windows Server 2008 Enterprise, Standard, Web, Small Business Server, Enterprise x64, or Standard x64
Windows Server 2003 or 2003 R2 Enterprise, Standard, Web, Small Business Server, Enterprise x64, or Standard x64. Each of the Windows 2003 operating systems require Service Pack 1 or later.
Provisioned virtual—If your recovery server will be provisioned (automatically created during the recovery process) you must have a physical host machine where Double-Take Backup can create the new virtual server. Your physical host machine can be either of the following operating systems.
Windows 2008 Hyper-V
The Enterprise Edition of VMware ESX version 3.0.x, 3.5, or 4.0. If you are using version 3.0.1, you must have HotRemove patch #6921838. VMware ESXi versions 3 or 4 are also supported as long as ESXi is managed by VCenter or VSphere.
You must have an existing virtual machine, known as a virtual recovery appliance, running Windows Server 2008, 2003, or 2003 R2. The virtual recovery appliance must have a same or newer operating system than the original source (not including service pack level).
The existing virtual must have Double-Take Backup installed and licensed on it before you can start the recovery process.

When you are ready for recovery the existing virtual will create the new virtual server, mount disks, format disks, and so on. Once the new virtual machine is online, it will have the identity, data, and system state of the original source. Since the existing virtual machine maintains its own identity, it can be reused for additional recoveries.

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.

Architecture	Minimum System Memory	Recommended System Memory
32-bit	128 MB	At least 512 MB
64-bit	512 MB	At least 1024 MB

Disk space for program files—This is the amount of disk space, approximately 130 MB, needed on the recovery server to hold the Double-Take Backup program files.
Disk space for data files—This is the amount of disk space on the recovery server to hold all of 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 on the recovery server to hold the image of the source system state. You should have at least 5 GB of space on the recovery server for the system state. The more applications you are running on the source, the larger the system state image will be. Therefore, you may need additional space if you source has many applications.
Disk types—Thin-provisioned virtual disks on VMware ESX are not supported because they cannot be shared by two virtual machines simultaneously.
Server name—Double-Take Backup 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—Version 3.5 Service Pack 1 is required on the recovery server.