public:module:hyper-v:run_direct_restore
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
public:module:hyper-v:run_direct_restore [2019/09/11 16:49] ronnie.chan |
public:module:hyper-v:run_direct_restore [2019/09/20 15:20] (current) ronnie.chan |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Run Direct Restore ====== | ====== Run Direct Restore ====== | ||
| + | ---- | ||
| This type of restore will start up the guest VM directly from the backup file without restoring the guest virtual machine to the Hyper-V server. | This type of restore will start up the guest VM directly from the backup file without restoring the guest virtual machine to the Hyper-V server. | ||
| + | {{INLINETOC}} \\ | ||
| + | |||
| + | ===== Restore to Original Hyper-V Host ===== | ||
| ---- | ---- | ||
| - | |||
| - | ===== 1). Restore to Original Hyper-V Host ===== | ||
| **Start up a guest VM from Backup Destination without Auto Migration Enabled** -- The guest VM data will not migrate to the destination until you manually trigger this action. If manual migration is not performed, any changes made during the Run Direct instance will NOT be committed to backup files. | **Start up a guest VM from Backup Destination without Auto Migration Enabled** -- The guest VM data will not migrate to the destination until you manually trigger this action. If manual migration is not performed, any changes made during the Run Direct instance will NOT be committed to backup files. | ||
| Line 13: | Line 15: | ||
| ==== Requirements and Limitations ==== | ==== Requirements and Limitations ==== | ||
| + | ---- | ||
| 1. Run Direct restore can only be performed on one guest virtual machine at a time. | 1. Run Direct restore can only be performed on one guest virtual machine at a time. | ||
| Line 25: | Line 28: | ||
| ==== Procedures ==== | ==== Procedures ==== | ||
| + | ---- | ||
| <WRAP indent> | <WRAP indent> | ||
| === a). Start up a guest VM from Backup Destination without Auto Migration Enabled === | === a). Start up a guest VM from Backup Destination without Auto Migration Enabled === | ||
| + | ---- | ||
| Follow the steps below to start up the guest VM directly from the backup files. | Follow the steps below to start up the guest VM directly from the backup files. | ||
| Line 81: | Line 86: | ||
| === b). Migrate Virtual Machine (Permanently Restore) === | === b). Migrate Virtual Machine (Permanently Restore) === | ||
| + | ---- | ||
| To permanently restore the guest virtual machine after starting up using the Run Direct option, you will still need to migrate it from the backup destination to the designated permanent location on the Hyper-V server using the Migrate Virtual Machine option. This process can be performed even when the guest machine is already running. | To permanently restore the guest virtual machine after starting up using the Run Direct option, you will still need to migrate it from the backup destination to the designated permanent location on the Hyper-V server using the Migrate Virtual Machine option. This process can be performed even when the guest machine is already running. | ||
| Line 98: | Line 104: | ||
| === c). Stop Run Direct Virtual Machines === | === c). Stop Run Direct Virtual Machines === | ||
| + | ---- | ||
| To stop running guest virtual machines started up using Run Direct can be done by either: | To stop running guest virtual machines started up using Run Direct can be done by either: | ||
| Line 112: | Line 119: | ||
| === d). Start up a guest VM from Backup Destination with Auto Migration Enabled === | === d). Start up a guest VM from Backup Destination with Auto Migration Enabled === | ||
| + | ---- | ||
| Follow the steps below to start up the guest VM directly from the backup files. | Follow the steps below to start up the guest VM directly from the backup files. | ||
| Line 167: | Line 175: | ||
| </WRAP></WRAP> | </WRAP></WRAP> | ||
| - | ---- | + | \\ |
| - | ===== 2). Restore to Different (Standby) Hyper-V Host ===== | + | ===== Restore to Different (Standby) Hyper-V Host ===== |
| + | ---- | ||
| Run Direct restore guest VM to a standby Hyper-V host is supported by the latest CloudBacko Pro. This restore option allows you to restore your backed up guest VM to another Hyper-V host, for example: if your original Hyper-V host is down and you need to restore your production guest VM’s to a standby Hyper-V host. | Run Direct restore guest VM to a standby Hyper-V host is supported by the latest CloudBacko Pro. This restore option allows you to restore your backed up guest VM to another Hyper-V host, for example: if your original Hyper-V host is down and you need to restore your production guest VM’s to a standby Hyper-V host. | ||
| Line 178: | Line 187: | ||
| <WRAP indent> | <WRAP indent> | ||
| ==== Requirements and Limitations ==== | ==== Requirements and Limitations ==== | ||
| + | ---- | ||
| 1. CloudBacko Pro must be installed on the Hyper-V Host where you wish to restore the guest Virtual Machine. | 1. CloudBacko Pro must be installed on the Hyper-V Host where you wish to restore the guest Virtual Machine. | ||
| Line 283: | Line 293: | ||
| ==== Procedures ==== | ==== Procedures ==== | ||
| + | ---- | ||
| <WRAP indent> | <WRAP indent> | ||
| === a). Start up a guest VM from Backup Destination without Auto Migration Enabled === | === a). Start up a guest VM from Backup Destination without Auto Migration Enabled === | ||
| + | ---- | ||
| This restore option allows you to restore your backed up guest VM to another Hyper-V host, for example if your original Hyper-V host is down and you need to restore your production guest VM’s to a standby Hyper-V host. | This restore option allows you to restore your backed up guest VM to another Hyper-V host, for example if your original Hyper-V host is down and you need to restore your production guest VM’s to a standby Hyper-V host. | ||
| Please refer to the Requirements and Limitations for the details about requirements and limitations for restoring Hyper-V guest VM to another Hyper-V host. | Please refer to the Requirements and Limitations for the details about requirements and limitations for restoring Hyper-V guest VM to another Hyper-V host. | ||
| Line 342: | Line 354: | ||
| === b). Migrate Virtual Machine (Permanently Restore) === | === b). Migrate Virtual Machine (Permanently Restore) === | ||
| + | ---- | ||
| To permanently restore the guest virtual machine after starting up using the Run Direct option, you will still need to migrate it to from the backup destination to the designated permanent location on the Hyper-V server using the Migrate Virtual Machine option. This process can be performed even when the guest machine is already running. | To permanently restore the guest virtual machine after starting up using the Run Direct option, you will still need to migrate it to from the backup destination to the designated permanent location on the Hyper-V server using the Migrate Virtual Machine option. This process can be performed even when the guest machine is already running. | ||
| Line 360: | Line 373: | ||
| === c). Stop Run Direct Virtual Machines === | === c). Stop Run Direct Virtual Machines === | ||
| + | ---- | ||
| To stop running guest virtual machines started up using Run Direct can be done by either: | To stop running guest virtual machines started up using Run Direct can be done by either: | ||
| Line 374: | Line 388: | ||
| === d). Start up a guest VM from Backup Destination with Auto Migration Enabled === | === d). Start up a guest VM from Backup Destination with Auto Migration Enabled === | ||
| + | ---- | ||
| Follow the steps below to start up the guest VM directly from the backup files. | Follow the steps below to start up the guest VM directly from the backup files. | ||
| - | 1. On the machine you wish to restore Hyper-V guest VM, launch CloudBacko Pro and click the Restore icon in the main interface. | + | 1. On the machine you wish to restore Hyper-V guest VM, launch CloudBacko Pro and click the Restore icon in the main interface. \\ {{public:module:hyper-v:hyperv-155.png?200}} |
| - | Select the backup set that you would like to restore the guest virtual machine from. | + | |
| - | Select the local, mapped drive, or removable drive storage destination that contains Hyper-V guest virtual machine that you would like to restore. | + | |
| - | Select Restore virtual machines as the restore mode. | + | |
| - | Select to restore the Hyper-V guest from a specific backup job then select the files or folders that you would like to restore. Click Next to proceed. | + | |
| - | Select to restore the Hyper-V guest VM to the Original location, or to an Alternate location. Then select Run Direct and Auto migrate after Run Direct is running and click Next to proceed. | + | |
| - | Original location – The Hyper-V guest VM will be restored to the same directory path which stores the backup source on the original Hyper-V host. | + | 2. Select the backup set that you would like to restore the guest virtual machine from. \\ {{public:module:hyper-v:hyperv-156.png?640}} |
| - | Alternate location – The Hyper-V guest VM will be restored to the different directory path on the original Hyper-V host. | + | |
| - | Click Next to proceed and the following values are needed to be update: | + | |
| - | Virtual Machine Name | + | 3. Select the local, mapped drive, or removable drive storage destination that contains Hyper-V guest virtual machine that you would like to restore. \\ {{public:module:hyper-v:hyperv-157.png?640}} |
| - | Virtual Machines Directory Location (guest configuration files) | + | |
| - | Restore As (new location for the guest VHD files) | + | |
| - | Example: | + | |
| - | Rename the restored guest VM to “CentOS 6.4-1” | + | 4. Select Restore virtual machines as the restore mode. \\ {{public:module:hyper-v:hyperv-158.png?640}} |
| - | Store the configuration files in the new location “D:\Virtual Machines\CentOS6.4\CentOS 6.4\” | + | |
| - | Store the VHD files in the new location “D:\Virtual Machines\CentOS6.4\” | + | |
| - | When the values have been updated click on Next to proceed. | + | |
| - | Confirm the temporary directory path is correct and then click Restore to proceed. | + | |
| - | If the guest virtual machine selected to be restore already exists on the Hyper-V server CloudBacko Pro will prompt to confirm overwriting of the existing guest. | + | |
| - | Yes - the exiting guest virtual machine will be deleted from the Hyper-V server before the restore process starts. | + | 5. Select to restore the Hyper-V guest from a specific backup job then select the files or folders that you would like to restore. Click Next to proceed. \\ {{public:module:hyper-v:hyperv-159.png?640}} |
| - | No – the restore of the current guest virtual machine will be skipped. | + | |
| - | After the Hyper-V guest virtual machine has been restored, you will see the following screen. | + | |
| - | Go to the Hyper-V server and open the Hyper-V Manager to verify the guest has been restored and is powered on. | + | |
| - | Connect to the guest virtual machine to verify if is running correctly. | + | |
| - | Example: Linux guest | + | 6. Select to restore the Hyper-V guest VM to the Original location, or to an Alternate location. Then select Run Direct and Auto migrate after Run Direct is running and click Next to proceed. |
| + | * **Original location** – The Hyper-V guest VM will be restored to the same directory path which stores the backup source on the original Hyper-V host. | ||
| + | * **Alternate location** – The Hyper-V guest VM will be restored to the different directory path on the original Hyper-V host. | ||
| - | </WRAP> | + | Click Next to proceed and the following values are needed to be update: |
| - | </WRAP> | + | |
| - | ---- | + | * **Virtual Machine Name** |
| + | * **Virtual Machines Directory Location** (guest configuration files) | ||
| + | |||
| + | * **Restore As** (new location for the guest VHD files) | ||
| + | |||
| + | Example: | ||
| + | |||
| + | * Rename the restored guest VM to **CentOS 6.4-1** | ||
| + | |||
| + | * Store the configuration files in the new location **D:\Virtual Machines\CentOS6.4\CentOS 6.4\** | ||
| + | |||
| + | * Store the VHD files in the new location **D:\Virtual Machines\CentOS6.4\** \\ {{public:module:hyper-v:hyperv-162.png?640}} | ||
| + | |||
| + | When the values have been updated click on Next to proceed. | ||
| + | |||
| + | 7. Confirm the temporary directory path is correct and then click Restore to proceed. \\ {{public:module:hyper-v:hyperv-163.png?640}} | ||
| + | |||
| + | 8. If the guest virtual machine selected to be restore already exists on the Hyper-V server CloudBacko Pro will prompt to confirm overwriting of the existing guest. | ||
| + | |||
| + | * **Yes** - the exiting guest virtual machine will be deleted from the Hyper-V server before the restore process starts. | ||
| + | |||
| + | * **No** – the restore of the current guest virtual machine will be skipped. \\ {{public:module:hyper-v:hyperv-164.png?640}} | ||
| + | |||
| + | 9. After the Hyper-V guest virtual machine has been restored, you will see the following screen. \\ {{public:module:hyper-v:hyperv-165.png?640}} | ||
| + | |||
| + | 10. Go to the Hyper-V server and open the Hyper-V Manager to verify the guest has been restored and is powered on. \\ {{public:module:hyper-v:hyperv-166.png?640}} | ||
| + | |||
| + | 11. Connect to the guest virtual machine to verify if is running correctly. | ||
| + | |||
| + | Example: Linux guest \\ {{public:module:hyper-v:hyperv-167.png?640}} | ||
| + | |||
| + | </WRAP> | ||
| + | </WRAP> | ||
public/module/hyper-v/run_direct_restore.1568191772.txt.gz · Last modified: 2019/09/11 16:49 by ronnie.chan
Page Tools
