This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
public:module:vmware:run_direct [2019/09/17 12:16] ronnie.chan created |
public:module:vmware:run_direct [2019/09/19 15:59] (current) ronnie.chan |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Run Direct Instant VM Restore ====== | + | ====== About Run Direct ====== |
---- | ---- | ||
- | |||
- | ===== What is Run Direct? ===== | ||
Run Direct is a feature that helps reduce disruption and downtime of your production VMs. | Run Direct is a feature that helps reduce disruption and downtime of your production VMs. | ||
Unlike normal VM restore procedure where a VM is extracted from backup files and copied to the production storage, which can take hours to complete. Restore with Run Direct can instantly power up a VM by running it directly from the backup files in the backup destination and the VM can be put into production. | Unlike normal VM restore procedure where a VM is extracted from backup files and copied to the production storage, which can take hours to complete. Restore with Run Direct can instantly power up a VM by running it directly from the backup files in the backup destination and the VM can be put into production. | ||
+ | |||
+ | {{INLINETOC}} \\ | ||
===== How does Run Direct work? ===== | ===== How does Run Direct work? ===== | ||
+ | ---- | ||
+ | |||
When a Run Direct restore is performed, the backup destination is mounted as an NFS datastore from the VMware host, where the VM is run directly from the backup files. | When a Run Direct restore is performed, the backup destination is mounted as an NFS datastore from the VMware host, where the VM is run directly from the backup files. | ||
The backup destination should be a local drive that can connect with CloudBacko Pro. \\ {{public:module:vmware:cloudbacko_module_vmware_002.png}} | The backup destination should be a local drive that can connect with CloudBacko Pro. \\ {{public:module:vmware:cloudbacko_module_vmware_002.png}} | ||
Line 14: | Line 15: | ||
===== Settings Differences between Run Direct and Non-Run Direct Backup Set on VMware ===== | ===== Settings Differences between Run Direct and Non-Run Direct Backup Set on VMware ===== | ||
+ | ---- | ||
+ | |||
^ ^ Run Direct Backup Set ^ Non-Run Direct Backup Set ^ | ^ ^ Run Direct Backup Set ^ Non-Run Direct Backup Set ^ | ||
^ Encryption | NO | YES | | ^ Encryption | NO | YES | | ||
Line 22: | Line 25: | ||
===== Finalizing a VM Recovery (Migrating VM to permanent location) ===== | ===== Finalizing a VM Recovery (Migrating VM to permanent location) ===== | ||
+ | ---- | ||
+ | |||
To finalize recovery of a VM, you will still need to migrate it to a permanent location on the VMware host. The following steps are taken when you finalize a Run Direct restore: | To finalize recovery of a VM, you will still need to migrate it to a permanent location on the VMware host. The following steps are taken when you finalize a Run Direct restore: | ||
<WRAP indent> | <WRAP indent> | ||
Line 32: | Line 37: | ||
</WRAP> | </WRAP> | ||
<WRAP info>For vCenter VM backup set, provided that the vMotion feature of the vCenter set is working properly, the VM will not be suspended during the data consolidation.</WRAP> | <WRAP info>For vCenter VM backup set, provided that the vMotion feature of the vCenter set is working properly, the VM will not be suspended during the data consolidation.</WRAP> | ||
- | </WRAP> | + |