Virtual disaster recovery to VMware ESXi
The virtual disaster recovery feature lets you create a virtual machine on a remote vSphere/ESXi server and recover your system there. You can launch the virtual machine using vSphere Client or vSphere Web Client.
Before you initiate virtual disaster recovery to VMware ESXi, make sure both of the systems involved are supported and properly configured.
- Source system – the system that has been backed up with the Backup Manager and is now going to be recovered.
- Host system – the system that the recovery software is installed on. It can coincide with the source system.
All the supported Windows versions are suitable for virtual disaster recovery to VMware ESXi targets.
- Windows 7, 8, 8.1 and 10
- Windows Server 2008, 2008 R2, 2012, 2012 R2 and 2016
Backup selection requirements
To start using the Virtual Disaster Recovery feature, you need to back up the following:
- The system state of your computer (the System State data source).
- The whole system disk –
C:\or another disk that has your operating system and that the operating system boots from (the Files and Folders data source).
- Any other data that is important to you. Supported data sources: Files and Folders, MS Exchange, and MS SQL.
It is possible to back up a system containing dynamic disks (they are converted to basic disks during virtual disaster recovery). If a dynamic disk uses the MBR partition table, the total size of its dynamic volumes must not exceed 2TB.
Optional settings (for better restore speed)
If the data transfer speed through the Internet is not high enough, you can benefit from enabling the LocalSpeedVault in the source system.
Planning to perform recovery from another machine? Then consider placing the LocalSpeedVault folder on any of the following:
- A removable storage drive that you will be able to attach to the host machine
- The host machine (if it is located on the local network)
- Another machine on the local network that is accessible from the host machine.
The host system that virtual disaster recovery is performed from must meet some requirements. It can be the same system that is being recovered or a different one.
You can initiate data recovery from the following versions of Windows (64-bit only):
- Windows 7, 8, 8.1 and 10
- Windows Server 2008 R2, 2012, 2012 R2 and 2016
The host system must not be older than the source system. For example, if you want to restore Windows 8, you must install your recovery software on Windows 8 or a newer version.
If you want to enable continuous recovery for multiple devices, consider using the target vSphere/ESXi server as your virtual disaster recovery host. Make sure you use the same datacenter and storage for the host machine and the target machine. This will give you twofold or threefold speed increase (confirmed by in-house tests).
- VMware vSphere/VMware. All paid 64-bit versions are supported: 5.1, 5.5, 6.0 and 6.5.
- 64-bit virtual disaster recovery software (the Backup Manager or the Recovery Console)
Free versions of VMware ESXi hosts are not supported. Two workaround options are available:
- Create a new virtual machine with required characteristics and perform bare metal recovery there (recommended as a faster option).
- Perform virtual disaster recovery to a VMDK file. Use VMware vCenter Converter to convert the local VMDK file from the workstation format to the appropriate format and to attach it to the ESXi server.
- Access to remote ESXi server – Enter your vSphere/ESXi server access credentials to let the recovery software access the server and create a virtual machine there. The server address, username and password is required.
- Access to virtual machine – You must assign a name to the new virtual machine. The rest of the settings are retrieved automatically after a connection to the server is established. Whenever options are available, you will be able to choose a suitable one from a dropdown list: a data center, host, storage and resource pool.
Virtual machine properties
You can assign custom properties to the new virtual machine: an IP address, subnet mask, gateway and DNS servers.
Set boot disk size to ...
Use this setting to customize the size to the system disk created on the virtual machine (by default, the new disk is the same size as the original).
If the disk contains several partitions, you cannot reduce the original size by more than the amount of free space on the last partition. For example, if the total size of the disk is 100 GB and the last partition has 10 GB of free space, you can set the value to 90 or more.
Use restore-only mode on target machine
Helps prevent unwanted backups from running on the recovered virtual machine.
Skip files that have not changed
Helps optimize data recovery operations and increases recovery speed. It applies to subsequent restore sessions (not the initial restore session in which the whole amount of data is transferred).
Create only volumes that are selected for restore
- If the setting is on, the target virtual machine will contain only those disks that have data selected for recovery.
- If the setting is off and no data from a disk is selected for recovery, the virtual disk is created without any data.
The setting is ignored if the disk you have excluded from recovery contains critical data. Such a thing can happen if your recovery selection includes MS Exchange or MS SQL and some files belonging to these data sources are located on the excluded disk. In this case the disk is created and populated with the files required by MS Exchange and MS SQL.
Repair files replication service
If you are restoring Active Directory with multiple domain controllers, you should change the FRS and DFSR services to authoritative in the domain controller that will be started in the first place. Avoid marking several FRS/DFSR services as authoritative in the production environment as it can result in data loss. When the feature is on, the FRS and DFSR services are started on the target VM in the authoritative mode. The NETLOGON and SYSVOL shares become available, so the Active Directory and DNS services become functional again.
More information about FRS/DFSR is available in the Microsoft Knowledge Base. Article IDs: KB2218556, kbinfo KB290762.
Start the virtual machine after restore and take screenshot
If the option is enabled, the new virtual machine is booted up after recovery and a confirmation screenshot is created. The results of virtual disaster recovery sessions together with screenshots of the booted systems come in email notifications (a special notification rule has to be activated by the service provider or system administrator).
The screenshots are also available in the Backup & Recovery Console (see the "Virtual Disaster Recovery data session verification details (restore)" column in the Device Management module).
Use the feature carefully if there is another virtual machine in the local network offering the same services (for example, the Active Directory) as it can result in a conflict with subsequent data loss.