Skip to main content
Hyper-V virtual machine restore
Updated over 7 months ago

Enterprise Workloads Editions: βœ… Business | βœ… Enterprise | βœ… Elite

Phoenix lets you restore your virtual machines to a Hyper-V host that is registered with Phoenix. You can choose to restore your virtual machine to the original location or the alternate location.

Restore virtual machine to the original location

  1. On the Management Console, select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then select the workload.

  2. In the left navigation, click Configured VMs.

  3. In the right pane, select the virtual machine you want to restore.



    β€‹πŸ“ Note
    ​You can apply filters based on VM, Host, or Admin Group.



    configured VMs.png

  4. Click Restore. The Restore VM wizard appears.

  5. The Data Restore option is selected by default. Select Full VM Restore.

  6. Select a recovery point from the drop-down and click Proceed to Restore.

  7. On the Full VM Restore dialog box, the restore target is selected by default to Restore to original location. This restores the entire VMs to the original hypervisor with original settings.
    ​

    original location.png

  8. Click Finish.


πŸ“ Note

  • To avoid accidental overwrites, ensure you have enough space available on the destination location, as original VHDs are not cleaned up after the restore is completed. The VHDs can be manually removed to recover space only after successful restores.

  • For a virtual machine backed up using Enterprise Workloads agent version 4.7.4 or earlier, if you change the virtual machine configuration such as name, memory, and vCPUs after backing up the virtual machine:

    • Phoenix overwrites the updated configuration at the time of restore

    • Phoenix restores the virtual machine with original configuration such as name, memory, and vCPUs of the virtual machine at the time of backup


After the agent fetches the virtual machine from the cloud, it performs the following tasks on the host:

  1. The agent deletes the virtual machine. Deleting the virtual machine does not delete the virtual machine's files and disks (if the virtual machine was backed up using the Enterprise Workloads agent version 4.7.4 or earlier).

  2. The agent downloads the disks and configuration files and restores them to the original location that Phoenix records at the time of backup.

  3. The agent renames the files and disks in that location. The agent adds the suffix β€˜.Phoenix.${restore_job_id} to the existing files and virtual disks.

  4. The agent creates a virtual machine using the disks and configuration files it restores (if the virtual machine was backed up using the Enterprise Workloads agent version 4.7.4 or earlier).

  5. If a virtual disk was excluded in the backup policy, then the disk is not attached to the restored virtual machine.

  6. A physical disk (Passthrough disk) or a shared disk attached to the original virtual machine is not attached at the time of restore. Druva does not backup physical disks (Passthrough disks) or shared disks attached to a virtual machine.

  7. Virtual machine ID is preserved to let a user perform a guest repair.

Restore virtual machine to an alternate location

  1. Log in to Management Console.

  2. select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then select the workload.

  3. In the left navigation, click Configured VMs.

  4. In the right pane, select the virtual machine you want to restore.

  5. Click Restore. The Restore VM wizard appears.

  6. The Data Restore option is selected by default. Select Full VM Restore.

  7. Select a recovery point from the drop-down and click Proceed to Restore.

  8. On the Full VM Restore dialog box, the restore target is selected by default to Restore to alternate location. This creates a new VM on any selected hypervisor with the customized settings.

    alternate location.png

    • Virtual Machine:

      Name of the virtual machine after restore. If you choose an alternate location for restore, a new virtual machine is created on the destination host.

    • Destination Hyper-V Host: Host on which the virtual machine will be restored.

    • Cluster: Cluster on which the selected host is present.

    • SCVMM: SCVMM on which the selected host is present.

    • Configuration File Location: Specify the location on the host where the configuration files are downloaded. You can choose:

      • A local folder: You can browse and select the destination folder

      • SMB share: Type the shared folder path

    • Disk(s) Location: Specify the location where the virtual disks are downloaded. You can choose:

      • A local folder: You can browse and select the destination folder

      • SMB share: Type the shared folder path

    • Network: Select a network available on the destination Hyper-V host.

  9. Click Finish.

After the agent fetches the virtual machine from the cloud, it performs the following tasks on the host:

  1. Agent downloads the disks at the entered disk location and configuration files at the entered configuration file location.

  2. If disks or files are present in the entered location, the agent renames the files with suffix β€˜.Phoenix.${restore_job_id}.
    If multiple disks use the same name, the agent renames the disks by adding a suffix such as _1, _2,and _3.

  3. The agent creates the virtual machine using the restored disks and configuration files and a new virtual machine ID.

  4. If a virtual disk was excluded in the backup policy, then the disk is not attached to the restored virtual machine.

  5. A physical disk or shared disk attached to the original virtual machine is not attached at the time of restore. Phoenix does not backup physical disks or shared disks attached to a virtual machine.

  6. All checkpoints at the time of backup are preserved if the backup method is VSS.


πŸ“ Note
​The virtual machine is in powered-off state after it is restored.


Did this answer your question?