Limitations on restoration hyper-V VMs settings

Depending on specific conditions, Xopero ONE employs two restoration methods: a more accurate one and a less accurate one. These methods are chosen automatically based on certain criteria.

Conditions for Using the Less Accurate Restoration Method

1) Lower Configuration Version on the Host

If the configuration version on the host machine where the restoration is happening is lower than the configuration version of the restored machine, you'll see a warning labeled DW9715. To check the configuration version on the host, you can use a PowerShell command:

Get-VMHostSupportedVersion | Where-Object { $_.IsDefault -eq $true }

It's important to note that this limitation is inherent to Hyper-V itself.

2) TPM (Trusted Platform Module) Module Enabled on the Backed-Up Machine

If the machine you backed up had the TPM module enabled, you'll see a warning labeled DW9717.

TPM is a hardware-based security feature that helps ensure the integrity of the system and data by providing cryptographic keys and protecting sensitive information. The restrictions linked to the restoration of machine configurations involving TPM arise from the inherent constraints within Hyper-V.

What Cannot Be Restored Using the Less Accurate Method

Several important settings cannot be restored using the less accurate method. These include:

  • Disk QoS (Quality of Service)

  • CD/DVD Drive Controller settings

  • Machine group memberships

  • Connect Access settings

  • Console Support settings

  • Resource measurement settings

  • Floppy drive settings

  • Efi Boot Order settings

  • Display settings

Remembering the limitations

Please keep these limitations in mind during the Hyper-V machine settings restoration process. If you have any questions or encounter any issues, don't hesitate to reach out to Xopero ONE technical support for assistance

Last updated