Learn how to restore whole virtual machines in Xopero ONE.
Open the Hyper-V tab (Virtual Machines > Hyper-V) in XMS, then click the Manage & Restore button next to the host whose backup you want to restore.
Select the VM you want to restore and click the restore button.
After choosing the backup plan and VM version, click Restore under the backup copy you wish to recover and select the Whole machine option from the drop-down list.
Specify whether to restore the VM to its original location or a new one. Provide key details, including the restored VM’s name and desired power state (on/off) after restoration.
Next, select a directory for the VM configuration files, choose a location to store the VM disks, and assign a Hyper-V switch or resource pool for the network adapters.
Once configured, click Start now to begin the restoration process.
In Restore settings you can also limit the internet bandwidth.




Learn more about Hyper-V recovery limitations in Xopero ONE.
Depending on the situation, Xopero ONE uses two restoration methods: one that provides higher accuracy and another that is less precise. The system automatically selects the appropriate method based on predefined criteria.
If the configuration version on the host where the restoration is taking place is lower than that of the VM being restored, a warning labeled DW9715 will appear. You can check the host’s configuration version using the following PowerShell command:
Get-VMHostSupportedVersion | Where-Object { $_.IsDefault -eq $true }It’s important to note that this limitation originates from Hyper-V itself.
If the VM you backed up had the TPM (Trusted Platform Module) enabled, a warning labeled DW9717 will appear during restoration.
Several important settings cannot be restored using the less accurate method. These include:
CD/DVD drive controller settings.
Connect access settings.
Console support settings.
Disk QoS (quality of service).
Display settings.
EFI boot order settings.
Floppy drive settings.
Machine group memberships.
Resource measurement settings.
Keep these limitations in mind when restoring Hyper-V machine settings. If you have any questions or encounter issues, contact Xopero ONE technical support for assistance.
Instant restore - disaster recovery feature.
Instant restore provides immediate virtual machine recovery— it restores VM’s configuration files to the Hyper-V host, prepares the VM, and mounts its disks directly from the backup. This allows the Xopero ONE administrator to start using the VM almost immediately, without waiting for the full restoration.
Instant restore is intended only for disaster recovery and is not suitable for production use — to restore production data, use the whole VM recovery option.
When a VM backup is stored in cloud storage, the instant restore feature may work slower due to the need for random-access read operations.
Instant restore can be performed for only one virtual machine per backup agent at a time.
Open the Hyper-V tab (Virtual Machines > Hyper-V) in XMS, then click the Manage & Restore button next to the host whose backup you want to restore.
Select the VM you want to restore and click the restore button.
After choosing the backup plan and VM version, click Restore under the backup copy you wish to recover and select the Instant restore option from the drop-down list.
Specify whether to restore the VM to its original location or a new one. Provide key details, including the restored VM name, desired power state (on/off) after restoration, and the iSCSI port to use.
Next, select a directory for the VM configuration files, choose a location to store the VM disks, and assign a Hyper-V switch or resource pool for the network adapters.
Once configured, click Start now to begin the restoration process.
You can monitor active instant restore tasks in the Tasks tab in XMS. When you're finished working with the VM, you can shut it down by canceling the instant restore job — click the X button and confirm the cancellation.
In Restore settings you can also limit the internet bandwidth.





Hyper-V virtual machines restoration process overview.
When working with backup software, it’s important to know how to restore your data efficiently. Xopero ONE offers multiple methods to restore virtual machines directly to Hyper-V hosts — select one that best fits your requirements.
Note that these restore options also allow you to transfer VMs between different Hyper-V hosts, as long as they are connected to the Xopero ONE Management Service.
The instant restore feature quickly restores a VM’s configuration files to the Hyper-V host and prepares the virtual machine by mounting its disks directly from storage using the iSCSI protocol. This enables the VM to start within minutes. Because the data remains in the backup storage, no actual data is copied or restored elsewhere, allowing fast access without duplicating the backup.
This method is intended for disaster recovery scenarios and should not be used as a standard production restoration process.
To restore a virtual machine to Hyper-V after an incident, run both the instant restore and whole VM recovery tasks at the same time. This allows you to access and use the VM almost immediately via instant restore. Once the whole VM recovery is finished, you can stop the instant restore process and switch to using the fully recovered VM in production.
Note that this is a non-production restore; any changes or modifications made during the instant restore session are temporary and will not be saved. When you perform another restore, these changes will no longer be visible.
Whole VM recovery allows you to restore a virtual machine to its original location or to a new one. This is the standard method for VM restoration — Xopero ONE retrieves the VM data directly from storage and restores it to the Hyper-V host.
Instant restore is perfect for immediate disaster recovery, giving rapid access to your virtual machines within minutes.
Whole VM recovery ensures that your VM is fully restored and ready for production use.
Using both methods together allows you to quickly recover Hyper-V virtual machines while minimizing downtime.



