Operation Manual

managed by Acronis vmProtect 7 Agent. If the ESX(i) host you need is not in this list, then make sure

it is added in the Configure->ESX(i) hosts view.

Note that when restoring to “Original Location” the restored VM may not appear in the same

location (automatically overwriting the existing VM) as it was at the moment of creating the recovery

point. This will be the case if the selected VM (defined by the recovery point) has been migrated to a

host and/or datastore, ESX(i) host, resource pool or vApp. Since VMs are preserving their UUIDs

during migration, the recovery will go to the current location of the virtual machine. For example, at

the moment of creating the recovery point the VM was in vApp1, but later it has migrated to vApp2.

Then this VM will be restored to vApp2 overwriting the existing VM.

Once the ESX(i) host is defined, the list of available resource pools and datastores is build up

automatically where you can define the exact location for the restored virtual machine(s).

You should also define the format of the restored virtual drives, “As in original VM (recommended)”,

“Thin provisioning” or “Thick provisioning” with the respective drop-down list. Thin provisioning

increases the VM storage utilization by enabling dynamic allocation and intelligent provisioning of

the physical storage capacity.

Based on this selection, a hint will appear indicating how much space is required on the datastore for

the successful recovery operation. You cannot proceed to the next step of the restore backup task

wizard until the valid datastore with enough free space is selected.

Note that when restoring multiple virtual machines all of them will be placed to the destination

defined at this step of the restore wizard, each to unique new VM on the selected datastore.

New Restore Task wizard, Step 2 “Where to restore”, overwrite the existing VM confirmation dialog

If there are virtual machines on the selected ESX(i) host or datastore with the same names, you will

be asked to confirm overwriting the existing VMs. This choice defines the restored virtual machines

naming. If you choose to “Overwrite VMs”, then the existing virtual machines will be replaced with

the restored ones.

Note that in this case the datastore selection will be unavailable (since it is already defined by the

target VM being overwritten), however, you can change the resource pool location for this VM by

choosing corresponding item in the Resource Pool selection.