Skip to main content


Druva Documentation


Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

This topic describes common workarounds of issues that you might encounter while backing up or restoring Hyper-V virtual machines. 

Linux virtual machine boots into maintenance mode after restore

If the disk sequence changes after restore, the boot order changes for the Linux virtual machine and the virtual machine boots into maintenance mode or some virtual disks are not visible. 


For the Linux virtual machine, change the disk sequence in /etc/fstab.  The virtual machine boots without any problem after you enter the correct disk sequence. For more information, see RedHat documentation. [External link]

Virtual machine restored to an alternate host fails to start

When VM is restored on another host, sometimes it fails to start with an error: 'Unnamed VM' could not initialize. (Virtual machine ID).
The event log shows the error: The security ID structure is invalid (0x80070539).


On the Hyper-V host:

  1. Open an administrative PowerShell command window.
  2. Run:
    Grant-VMConnectAccess -VMName "Name of VM that is not starting" -UserName "Domain and username of the current user"

For more information, see Virtual machine cannot start - The security ID structure is invalid (0x80070539) [External link to a Microsoft support article.]

Cannot perform a file-level restore from a virtual machine backup

One of the reasons why a virtual machine FLR fails is presence of user snapshots. If user snapshots are present, Phoenix backs up a virtual machine however FLR from such virtual machine backups is currently not supported. The backup job for such a virtual machine is marked as successful with errors. 


Delete the user snapshots and backup the virtual machine to use file-level restore. 

The following error messages are encountered at the time of virtual machine restore:

  • Failed to add VHDs to VM dev03 (#10009000b)
  • General access denied

This error can occur if you are restoring a virtual machine or a virtual disk to a Windows Server 2008 or Windows Server 2008 R2 host with SMB share target, and appropriate write issues on the share are not available. 


To resolve this issue:

  • Flush and purge the existing authentication tickets between the host and the share, and
  • Re-apply write permissions to the target folder

For example:

  • Hyper-V host is Domain\hypervhost1
  • SMB Share system is Domain\smbsharesystem

To flush and purge the existing authentication tickets:

Run the following commands as administrator on the Hyper-V host

klist tickets
klist purge

Create a new folder apply write permissions to the target folder

Run the following commands as administrator on the Hyper-V host

MD C:\SomeFolder
ICACLS C:\SomeFolder /GRANT Domain\Administrator:(OI)(CI)F /GRANT Domain\hypervhost1$:(OI)(CI)F Domain\smbsharesystem$:(OI)(CI)F
NET SHARE SomeFolder=C:\SomeFolder /GRANT:Domain\Administrator,FULL /GRANT:Domain\hypervhost1$,FULL /GRANT:Domain\smbsharesystem$,FULL
Use the above example as a guide. Replace the inputs  SomeFolder, hypervhost1, and  smbsharesystem  based on your setup. 
  • Was this article helpful?