Skip to main content
Druva Documentation

Hyper-V error messages

This topic lists the Hyper-V specific errors that you may encounter during Hyper-V configuration. 

HYPERV1

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

Description: Phoenix Agent failed to connect to Hyper-V Virtual Machine Management service (HyperV VMMS). Ensure that VMMS service is running.

HYPERV2

Error message: Failed to connect to SCVMM.

Description: Phoenix agent failed to connect to SCVMM. 

Resolution: Ensure that:

  • SCVMM is running and reachable from Hyper-V Host
  • Provided SCVMM credentials are correct. Phoenix agent requires correct credentials so that it can connect to SCVMM.

HYPERV3

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

Description: Phoenix agent failed to connect to Cluster.

Resolution: Ensure that provided domain credentials are correct. 

HYPERV4

Error message: Failed to get host info from SCVMM.

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.

HYPERV7

Error message: Missing credentials for SCVMM/Cluster.

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

Resolution: Provide SCVMM/cluster credentials so that Phoenix agent can backup and restore virtual machines.  

HYPERV8

Error message: Virtual disk not found.

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

HYPERV9

Error message: Failed to get disk info.

Description: Phoenix agent failed to fetch virtual disk information. 

HYPERV10

Error message: Virtual machine not found.

HYPERV11

Error message: Virtual machine creation failed. 

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: Provided virtual disk path is incorrect. 

Resolution: Provide correct virtual disk path.

HYPERV13

Error message: Invalid virtual machine config path. 

Resolution: Provide correct virtual machine config path.

HYPERV14

Error message: Not enough space available for restore. 

HYPERV15

Error message: Failed to move existing file. 

Description: Phoenix agent cannot restore 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 Phoenix.

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: Phoenix does not support a setup that hosts multiple virtual machines that use the same universally unique identifier. Phoenix cannot backup virtual machines hosted on such a setup. 

HYPERV20

Error message: Failed to set SCVMM/cluster credentials. 

Resolution: Ensure that SCVMM/cluster credentials that provide are correct. 

HYPERV23

Error message: VM API error

Description: Phoenix agent failed to run WMI API. Please check detailed WMI error message.

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, Phoenix 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 Phoenix, you can restore it to Window Server 2012 R2.
Microsoft Windows Server 2016 Microsoft Windows Server 2016 Yes
Note: A restore job fails if its scenario is not listed above.

HYPERV26

Error message: Failed to create file/directory. 

Resolution: Check if the provided path is read-only. Phoenix fails to create a file/directory at a location that is read-only. 

HYPERV27

Error message: Failed to delete VM.

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

HYPERV28

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

Description: Microsoft does not support CSV and non-CSV volumes in one backup set. Phoenix will not be able to backup VM with such configuration.

See, A backup job may fail with a CSV and non-CSV volume in the same set on Windows Server 2012[External link to Microsoft Support article] 

HYPERV29

Error messageVM contains user snapshot. File Level Restore will not be supported for this restore point.

DescriptionVirtual machine had user snapshot(s) at the time of backup. File Level Restore is not supported for such restore point. You can restore the virtual machine or the virtual disk. 

Resolution: See, Troubleshooting

HYPERV30

Error messageThis virtual machine restore point contains user snapshot. File Level Restore is not supported for this restore point.

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

Resolution: See, Troubleshooting

HYPERV31

Error messageHyperV FLR Proxy with same name already exists

DescriptionHyperV FLR Proxy with same name already exists in Phoenix.

Resolution: You can delete the existing proxy to register a new proxy using the same name.

HYPERV32

Error messageFailed to read disk/config file for HyperV VM

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

HYPERV33

Error message: Failed to add Network Adapter to Virtual Machine

DescriptionPhoenix agent failed to add network adapter to the restored virtual machine.

Resolution: You can manually add a network adapter to the restored virtual machine.

HYPERV34

Error messageFailed to prepare cluster shared volume for backup

DescriptionFailed to prepare cluster shared volume for backup. See windows event logs for more details.

HYPERV35

Error messageFailed to clear backup state for shared volume

HYPERV36

Error messageFailed to get cluster shared volume details

HYPERV37

Error messageInvalid destination path given

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

  • Was this article helpful?