RunDirect Restore via ServosityPro
- Click the Restore icon on the main interface of Servosity.
- Select the backup set that you would like to restore the VM from.
- Select the backup destination that contains the VM that you would like to restore and choose "Restore Virtual Machines".
- Select Restore virtual machines as the restore mode.
- Select to restore VM from a specific backup job, or the latest job available from the Select what to restore drop down menu.
- Select the virtual machine that you would like to restore.
Important Note: When performing a Run Direct restore to Alternate Host, only one VM can be selected per restore session.
- 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).
- Enable the Run Direct option to run the VM directly from the backup files in the backup destination. Configure the following options according to the restore requirement:
Auto migrate after Run Direct is running - Enable this option to auto migrate the VM to a permanent location on the original VMware host \ another datastore of the original VMware host \ another VMware host, according to the Restore virtual machines to option.
Note: This will finalize the recovery of the VM; The migration will be performed after the VM is powered on.
Auto power on after Run Direct is running - Enable this option to power up the virtual machine automatically, after Run Direct is running for the VM.
Use existing storage as VM working directory to improve performance - Enable this option to enhance performance of the restored VM.
Click Next to proceed when you are done with the settings.
- This step applies only for restoring to Alternate location. For restoring to Original location, skip to the next step.
- Enter the VMware host and access information of where you would like the VM to be restored to.
- For restoration to another VMware host (ESXi server), select Version VMware ESXi 5 / 5.5 / 6 / 6.5, then enter the Password of the root account, Host, Port and SSH Port of the new / original host.
- For restoration to another VMware host (vCenter server), enter the Password of the administrator account, Host, and Port information of the new / original vCenter server.
- Press Next to proceed when you are done with the settings.
- Enter a new Name for the VM, then Browse to modify the Inventory Location, Host/Cluster, Resource Pool and Storage settings, according to where you would like the VM to be restored to.
- Click Next to proceed when you are done with the settings.
- Select the temporary directory for storing temporary files, then click Restore to start the restoration.
- When restoring your guest VM to another VMware host, the following message will be prompted. Since each virtual machine is automatically assigned a universally unique identifier (UUID), a new UUID must be created when you restore the guest VM to another host because it is not possible to have two identical UUID running at the same time.
Therefore, make sure you click Yes when you see the prompt below.
- The following screen shows when the VM has been restored successfully. You can then verifying the RunDirect Restored VM is running by logging into your ESXI / Vcenter and consoling into the VM.
When a RunDirect restore is initiated, the following steps are taken at the backend:
- Check the following items to verify if the RunDirect restore connection has been established between the backup destination and the VMware host.
- The following screen with the text Restore Completed Successfully displayed in your ServosityPro.
- A snapshot of the virtual machine is created. All changes made during Run Direct is taken place will be stored temporarily in this snapshot, and the changes will not be committed to the virtual machine until a migration is done.
- The virtual machine is powered on so it can be run directly from the backup files.
- The backup destination is turned into a NFS (also known as NAS) datastore
- Then the NFS datastore is mounted on the VMware Host so you are able to access the VM as you would be normally if it was created on your local datastore.