4. Select the virtual machine that you would like to restore.
When performing a Run Direct restore to Alternate Location, only one VM can be selected per restore session.
If you wish to restore the VM to another VMware host (ESXi server), you can restore the VM in raw file format, where the .vmdk disk format file will be included, by clicking the Restore raw file button at the bottom left corner.
5. Select to restore the VM to its Original location (to the original VMware host and datastore), or to an Alternate location (to another datastore of the original VMware host or another VMware host).
6. Enable the Run Direct option to run the VM directly from the backup files in the backup destination. Configure the following options according to your restore requirement:
This will finalize the recovery of the VM; The migration will be performed after the VM is powered on.
7. Click Show advanced option if you want to enable Verify checksum of in-file delta files during restore.
8. This step applies only for restoring to Alternate location. For restoring to Original location, skip to step 9.
Enter the VMware host and access information of where you would like the VM to be restored to.
Press Next to proceed when you are done with the settings.
Click Next to proceed when you are done with the settings.
10. When restoring your guest VM, different messages will be prompted depending on the selected location.
When a run direct restore is initiated, the following steps are taken at the backend.
i. Create NAS datastore - The backup destination is turned into a NFS (also known as NAS) datastore
ii. Mount VM on VMware Host - The NFS datastore is mounted on the VMware Host
iii. Create Virtual Machine Snapshot - A snapshot of the virtual machine is created. All changes made while Run Direct is taking place will be stored temporarily in this snapshot, and the changes will not be committed to the virtual machine until a migration is done.
iv. Power on Virtual Machine - The virtual machine is being powered on so it can be run directly from the backup files.
Check the following items to verify if the run direct restore connection has been established between the backup destination and the VMware host.
Do not exit from the AhsayOBM application when a Run Direct restored VM is still running. Run Direct must be stopped (e.g. by finalizing recovery of the VM or stopping the VM) before exiting CloudBacko Pro.
When the restored VM is starting up, there may be an error screen prompted to alert you that Windows was not shut down properly. This message shows as a result of the VM’s runtime status not being backed up. You may simply select to start up Windows as normal to proceed with the startup.
Manage a Run Direct restored virtual machine, by finalizing the VM recovery (e.g. migrating it to a permanent location on the VMware host), or stop the virtual machine when it is no longer needed.
To finalize recovery of a VM, migrate it to a permanent location on the VMware host:
3. Click Migrate Virtual Machine to start the migration process.
For VM on ESXi host, the VM may be suspended temporarily during the migration process. The downtime of the VM should be minimal.
To stop all virtual machines, or individual virtual machine that is running with the Run Direct feature:
1. Click Stop all Run Direct virtual machines to stop all VMs that are currently running with the Run Direct option.