====== Run Direct VM Restore ======
----
{{INLINETOC}} \\

===== Running Direct Restore via CloudBacko Pro =====
----

1. Click the Restore icon on the main interface of CloudBacko Pro.   \\ {{public:module:vmware:cloudbacko_module_vmware_042.png}}
 
2. Select the backup set that you would like to restore the VM from.   \\ {{public:module:vmware:cloudbacko_module_vmware_043.png?640}}
 
3. Select the backup destination that contains the VM that you would like to restore. \\ {{public:module:vmware:cloudbacko_module_vmware_044.png?640}}
 
4. Select the virtual machine that you would like to restore.
<WRAP important>
When performing a Run Direct restore to Alternate Location, only one VM can be selected per restore session.
</WRAP>

{{public:module:vmware:cloudbacko_module_vmware_045.png?640}}

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).

{{public:module:vmware:cloudbacko_module_vmware_046.png?640}}
 
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:  

{{public:module:vmware:cloudbacko_module_vmware_047.png?640}}

  * **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.

<WRAP info>
This will finalize the recovery of the VM; The migration will be performed after the VM is powered on.
</WRAP>

  * **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. 

7. Click Show advanced option if you want to enable Verify checksum of in-file delta files during restore. 

{{public:module:vmware:cloudbacko_module_vmware_048.png?640}}
              
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.

  * For restoration to another VMware host (ESXi server), select Version VMware ESXi 5 / 5.5 / 6 / 6.5 / 6.7, then enter the Password of the root account, Host, Port and SSH Port of the new / original host. \\ 
{{public:module:vmware:cloudbacko_module_vmware_049.png?640}}     

  * For restoration to another VMware host (vCenter server), enter the Username  and Password of the administrator account, Host, and Port information of the new / original vCenter server. \\ {{public:module:vmware:cloudbacko_module_vmware_050.png?640}}        

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.   \\ {{public:module:vmware:cloudbacko_module_vmware_051.png?640}}  \\ {{public:module:vmware:cloudbacko_module_vmware_052.png?640}} 
 
Click Next to proceed when you are done with the settings. 

9. Select the temporary directory for storing temporary files, then click Restore to start the restoration.  \\ {{public:module:vmware:cloudbacko_module_vmware_053.png?640}} 
 
10. When restoring your guest VM, different messages will be prompted depending on the selected location.   

  * Restoring guest VM to original location, click Yes to proceed.  \\ {{public:module:vmware:cloudbacko_module_vmware_054.png?640}} 

  * Restoring guest VM to another VMware host, 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.  It is not possible to have two identical UUID running at the same time, so make sure to click Yes when you see the prompt below.  \\ {{public:module:vmware:cloudbacko_module_vmware_055.png?640}} 

11. The following screen shows when the VM has been restored successfully.  \\ {{public:module:vmware:cloudbacko_module_vmware_056.png?640}} 
\\

===== Verifying Run Direct Restore Connection =====
----
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.

  * The following screen with the text Restore Completed Successfully displayed in your CloudBacko Pro.  \\ {{public:module:vmware:cloudbacko_module_vmware_057.png?640}} 
 
  * You should also be able to see the restored VM being run directly from the backup files in the backup destination. \\ {{public:module:vmware:cloudbacko_module_vmware_058.png?640}} 
 
<WRAP info>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.</WRAP>
\\

===== Manage Run Direct VM =====
----
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.

1. Click the Restore icon on the main interface of CloudBacko Pro. \\ {{public:module:vmware:cloudbacko_module_vmware_059.png}} 
 
2. Click Manage Run Direct virtual machines to manage all Run Direct virtual machines. \\ {{public:module:vmware:cloudbacko_module_vmware_060.png}} 

<WRAP indent>
==== Finalize VM Restore ====
To finalize recovery of a VM, migrate it to a permanent location on the VMware host:

1. Select the backup set which contains the Run Direct VM that you would like to finalize. \\ {{public:module:vmware:cloudbacko_module_vmware_061.png}} 
 
2. Click Browse to select the datastore where you would like to migrate the VM to. \\ {{public:module:vmware:cloudbacko_module_vmware_062.png}} 
 
3. Click Migrate Virtual Machine to start the migration process.
<WRAP info>For VM on ESXi host, the VM may be suspended temporarily during the migration process.  The downtime of the VM should be minimal.</WRAP>
 
==== Stop Run Direct VM ====
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.

Alternatively, select the backup set which contains the VM that you would like to stop. \\ {{public:module:vmware:cloudbacko_module_vmware_063.png}} 
 
2. Click Stop Run Direct to stop the VM. \\ {{public:module:vmware:cloudbacko_module_vmware_064.png}} 
 
3. Click Yes to proceed.  \\ {{public:module:vmware:cloudbacko_module_vmware_065.png}}