Skip to main content
Hyper-V errors
Updated today

HYPERV1

Error message:Failed to connect to HyperV Virtual Machine Management service.

Description:Hybrid Workloads agent failed to connect to Hyper-V Virtual Machine Management service (HyperV VMMS).

Resolution: Ensure that the Hyper-V Virtual Machine Management Service(VMMS), and its dependencies (RPC, WMI) are running. If they fail to start, check the Windows event logs for further details.

HYPERV2

Error message:Failed to connect to SCVMM.

Description:Hybrid Workloads agent failed to connect to SCVMM.

Resolution:Ensure that:

  • SCVMM is running and reachable from Hyper-V Host

  • Provided SCVMM credentials are correct. Hybrid Workloads agent requires correct credentials so that it can connect to SCVMM. For more information, see Install the agent and register the Hyper-V host.

HYPERV3

Error message:Failed to connect to cluster with given credentials.

Description:Hybrid Workloads agent failed to connect to Cluster.

Resolution:Ensure that provided domain credentials are correct. For more information, see Install the agent and register the Hyper-V host.

HYPERV4

Error message:Failed to get host info from SCVMM.

Error Description: This error occurs when:

  • The Hybrid Workloads agent fails to list virtual machines if the SCVMM host is down or it is in an inconsistent state.

  • Remote command execution is not allowed.

Resolution: Verify if the SCVMM is up and running.

HYPERV6

Error message:Host is not part of given SCVMM.

Description:Hyper-V virtual machine host registered as a part of the SCVMM is actually not a part of the given SCVMM.

Resolution: Verify if the host is registered as a part of the SCVMM.

HYPERV7

Error message: Missing credentials for SCVMM/Cluster.

Description:Hybrid Workloads agent needs SCVMM/cluster credentials to backup and restore virtual machines hosted on the virtual machine host.

Resolution:Provide SCVMM/cluster credentials so that Hybrid Workloads agent can backup and restore virtual machines. For more information, see Install the agent and register the Hyper-V host.

HYPERV8

Error message: Virtual disk not found.

Description: Hybrid Workloads agent could not find the virtual disk on the host.

Resolution: Check if the VHD is present and accessible on the host.

HYPERV9

Error message:Failed to get disk info.

Description: Hybrid Workloads agent failed to fetch virtual disk information.

HYPERV10

Error message:Virtual machine not found.

Error description:A backup job fails with this error:

  • If the agent cannot find the virtual machines configured for backup, or

  • During restore, if you opt to restore to the original server and the virtual machine no longer exists, or

  • "VM not found for UUID (FXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX0)"

Resolution:

  • To find the UUID of the Hyper-V virtual machine from the host, perform the following steps:

    1. Open PowerShell in the admin mode.

    2. Run the command:
      ​Get-VM | ft Name, VMID

    3. You can verify from the job logs if the virtual machine is available on the specific hosts.

    4. In the case of the Clustered Hyper-V host, run this command separately on each host to get the list of hosted virtual machines on the host.

  • If you encounter this error after re-registering a host, see Troubleshooting.

HYPERV11

Error message:Virtual machine creation failed.

Error Description: Hybrid Workloads agent failed to create a virtual machine on the Hyper-V host at the time of full virtual machine restore.

Resolution: If you are restoring a virtual machine from Windows Server 2008 standard host to Windows 2012 R2 host, you can restore the virtual disk and create a virtual machine using the disk. For other issues, see

HYPERV12

Error message: Invalid virtual machine disk path.

Description:Hybrid Workloads agent is unable to find the location provided to restore the VHD/VHDX files.

Resolution: Ensure that you provide the correct path to restore the VHD/VHDX files.

HYPERV13

Error message:Invalid virtual machine config path.

Description:Hybrid Workloads agent is unable to find the location provided to restore the XML file.

Resolution: Ensure that you provide correct path to restore the XML file.

HYPERV14

Error message:Not enough space available for restore.

Error Description: Enough free space is not available on the location selected to restore virtual machines files (VHD/VHDX and XML).

Resolution: Select an alternate location with enough free space to restore the virtual machine files.

HYPERV15

Error message:Failed to move existing file.

Description: Hybrid Workloads agent cannot restore a virtual machine because it failed to move the (disk/config) file of the existing virtual machine.

HYPERV16

Error message:HyperV host with same name already exists.

Description: Hyper-V host with the same name is already registered with Druva.

Resolution: Read through the activation section of the registration article to learn more about the activation command, and how you can register a host with a different name.

HYPERV18

Error message: Failed to get cluster info.

HYPERV19

Error message: Multiple VMs with same UUID exists in cluster/scvmm.

Description: Druva does not support a setup that hosts multiple virtual machines that use the same universally unique identifier. Druva cannot back up virtual machines hosted on such a setup.

HYPERV23

Error message:VM API error

Description:This error occurs when a virtual machine is modified at the time of restore. For example, a virtual machine is modified for resource addition or modification or disk addition or modification at the time of restore.

Resolution: Check detailed WMI error message in the Druva logs or contact Support.

HYPERV25

Error message: Host OS check failed.

Description: This error can occur if you are trying to restore a virtual machine from a newer Windows host to an older Windows host. For example, you back up a virtual machine created on a Windows Server 2016 host and try to restore it on a Windows Server 2012 host. At the time of restoring the virtual machine, the Hybrid Workloads agent checks for the host OS. If the virtual machine is not compatible with the host OS, the host OS check fails with this error.

The following table lists supported restore scenarios:

Virtual machine backed up from

Virtual machine intended to be restored on

Restore supported?

Microsoft Windows Server 2008

Microsoft Windows Server 2008

Yes

Microsoft Windows Server 2008

Microsoft Windows Server 2008 R2

Yes

Microsoft Windows Server 2008 R2

Microsoft Windows Server 2008 R2

Yes

Microsoft Windows Server 2008 R2

Microsoft Windows Server 2012

Yes

Microsoft Windows Server 2008 R2

Microsoft Windows Server 2012 R2

Yes

Microsoft Windows Server 2008 R2

Microsoft Windows Server 2016

Yes

Microsoft Windows Server 2012

Microsoft Windows Server 2012

Yes

Microsoft Windows Server 2012

Microsoft Windows Server 2012 R2

Yes

Microsoft Windows Server 2012

Microsoft Windows Server 2016

Yes

Microsoft Windows Server 2012 R2

Microsoft Windows Server 2012 R2

Yes

Microsoft Windows Server 2012 R2

Microsoft Windows Server 2016

Yes

Microsoft Windows Server 2016

Microsoft Windows Server 2012 R2

Depends on the virtual machine configuration version.
​
If you created a virtual machine with configuration version 5 on Windows Server 2016, and then it was backed up using Druva, you can restore it to Window Server 2012 R2.

Microsoft Windows Server 2016

Microsoft Windows Server 2016

Yes

Microsoft Windows Server 2016

Microsoft Windows Server 2019

Yes

Microsoft Windows Server 2016

Microsoft Windows Server 2022

Yes

Microsoft Windows Server 2019

Microsoft Windows Server 2019

Yes

Microsoft Windows Server 2019

Microsoft Windows Server 2022

Yes

Microsoft Windows Server 2022

Microsoft Windows Server 2022

Yes


πŸ“ Note


​A restore job fails if its scenario is not listed above.


HYPERV26

Error message: Failed to create file/directory.

Error Description: This error occurs if the Hybrid Workloads agent failed to create a folder at the time of restore.

Resolution: Check if the provided path is read-only or the Hybrid Workloads agent cannot write to the provided location. Druva fails to create a file/directory at a location that is read-only or the write permissions are not available to the Hybrid Workloads agent. The Hybrid Workloads agent uses local system account credentials. Check for rights and permissions available to the local system account.

HYPERV27

Error message: Failed to delete VM.

Description:Hybrid Workloads agent failed to restore a virtual machine because it could not delete the existing virtual machine.

Resolution: Check if the existing virtual machine is powered off or restore the virtual machine to an alternate location.

HYPERV28

Error message:Failed to backup because both Cluster Shared Volume (CSV) and non-CSV volume are included in the backup.

Description: Microsoft does not support CSV and non-CSV volumes in one backup set. Druva will not be able to back up a virtual machine with such configuration.

HYPERV29

Error message:VM contains user recovery point. File Level Restore will not be supported for this recovery point.

Description:Virtual machine had a user recovery point(s) at the time of backup. File Level Restore is not supported for such recovery point. You can restore the virtual machine or the virtual disk.

Resolution: See Troubleshooting.

HYPERV30

Error message:This virtual machine recovery point contains user recovery point. File Level Restore is not supported for this recovery point.

Description:This recovery point contains user recovery point(s). File Level Restore is not supported for this recovery point. You can restore the virtual machine or the virtual disk and get the required files.

Resolution: See Troubleshooting.

HYPERV31

Error message:HyperV FLRProxy with same name already exists.

Description: You get this error when you try to activate aHyper-V FLRProxy which is already activated.

Resolution: You can use the existing proxy or delete the existing proxy and deploy and register a new proxy.

HYPERV32

Error message:Failed to read disk/configfile forHyperVVM

Description:Hybrid Workloads agent failed to read the virtual disk/configuration file of the virtual machine at the time of backup.

Resolution: Druva requires read permissions for the VHD/VHDX file.

HYPERV33

Error message:Failed to add Network Adapter to Virtual Machine

Description:Hybrid Workloads agent failed to add a network adapter to the restored virtual machine.

Resolution: Check the event logs and see Hyper-V host issues.

HYPERV34

Error message:Failed to prepare cluster shared volume for backup

Description:Failed to prepare cluster shared volume for backup. This can occur if cluster APIs are not available on the host or the cluster APIs on the host are not working properly.

Resolution: Check the event logs and see Hyper-V host issues.

HYPERV36

Error message:Failed to get cluster shared volume details

Description:This can occur at the time of backup or restore job if the Hybrid Workloads agent is unable to fetch the cluster shared volume details.

Resolution: Check if the cluster shared volume is accessible from the Hyper-V host.

HYPERV37

Error message:Invalid destination path given

Description: The path to the restore location that you provide should be empty.

Resolution: Druva requires that the path you provide should be an empty directory. If the directory does not exist, Druva will create the directory.

HYPERV38

Error message: Failed to create checkpoint for backup

Description:Druva could not create a checkpoint for backup. CheckWindowsevent log under Hyper-V-VMMS for more details.

Resolution: Check the event logs and see Hyper-V host issues.

HYPERV39

Error message:Failed to convert checkpoint to a reference point

Description:Druva could not convert a checkpoint to a reference point created for backup. CheckWindowsevent log underHyper-V-VMMSfor more details.

Resolution: Check the event logs and see Hyper-V host issues.

HYPERV42

Error message:Failed to openVHDfile

Description: The Hybrid Workloads agent failed to open the virtual disk to perform a read/write job.

Resolution: Ensure that the Hybrid Workloads agent has read-write access to the VHD/VHDX file.

HYPERV43

Error message:Failed to write toVHDfile

Description: Failed to write to virtual machine disk.

HYPERV44

Error message: Original VM restore failed

Description:Failed to restorethe virtualmachine to the original location.

HYPERV45

Error message: RCT backup not supported for this VM

Description: Virtual machine configuration does not support RCT based backup. For RCT based backup:

  • Virtual machine configuration level must be 6.2 or higher

  • If the host is a part of a cluster, cluster functional level must be 9 or higher

HYPERV47

Error message:No files available tobackup.

Description: No disk attached to the virtual machine configured or all virtual disks attached to the virtual machine are excluded from backup.

HYPERV48

Error message:No space left ondevicefor restore

Description: Disk ran out of space on which the data was getting restored.

HYPERV49

Error message: RCT backup not supported on this host

Description: Hyper-V RCT backup method is supported from agent version 4.7.5. Upgrade the agent to version 4.7.5 or later.

HYPERV50

Error Message: VM migrated to another host.

Description: This error occurs when VM is migrated to another host and the Hybrid Workloads agent attempts a backup job when a scheduled job kicks in or when you run it from the Management Console.

Resolution: The manual or scheduled backup fails after the VM is migrated. However, the backup job succeeds on a retry.

HYPERV51

Error Message: Failed to download from cold storage.

Description: This error occurs if the restoration of cold data failed.

Resolution: Contact Support.

HYPERV52

Error Message: VM contains passthrough/physical disks.

Description: Hyper-V does not allow takingrecovery pointsof physical/passthrough disks.

Resolution: VM contains a physical or passthrough disk whose backup is not supported. Ensure that you back up these disks using the File Server agent.

HYPERV53

Error message:VM contains shared disks

Description:This error occurs when an agent attempts to delete therecovery pointscreated during the backup for the VM containing shared disks.

Resolution:Detach or remove the shared disks from the VM.

Did this answer your question?