I have an issue which I haven't been able to find anyone else post anywhere about.
We have a Windows 2008 R2 cluster using Hyper-V.
Every now and again, virtual machines cannot be migrated manually between the hosts and it automatically fails if it needs to move them for whatever reason (such as a host going down).
Overview of our setup (same as everyone elses basically)
All virtual machines are stored in C:\ClusterStorage\Volume1(
al Machines on each host we have shortcuts for their XML configuration files (SYMLINK) and this corresponds correctly to what virtual machines are on that host - and the shortcuts point to C:\ClusterStorage\Volume1(
\ (they are correct).
The issue is, when we encounter the error and we cannot migrate a certain virtual machine, one of the HOST machines in our cluster actually has a duplicate XML file and folder which correspond to the virtual machine we cannot migrate.
As soon as I delete the actual XML file and folder from there, it migrates without an issue.
I don't know why it is every now and again placing that file in C:\ProgramData\Microsoft\W
al Machines instead of the correct location of C:\ClusterStorage\Volume1(
\ with a shortcut to the XML file in C:\ProgramData\Microsoft\W
As you can see in my attached screenshot - I just moved the offending XML files and folders into a folder called newfolder.
I am not sure if this issue is due to our hyper V manager having it's default locations for config files and virtual machine files still the default eg:
Virtual Hard Disks: C:\Users\Public\Documents\
rtual Hard Disks (this is empty anyway)
Virtual Machine Configuration Files: C:\ProgramData\Microsoft\W
er-V (this is where all our configuration file shortcuts are going and the offending XML file duplicates and folders).
Should I be changing these default locations? We have several clients setup the same and none present the current issue.
We backup with VEEAM and I don't know if this may be linked.
In the event logs we receive errors 4096
The Virtual Machines configuration F7DB08A6-DD45-4C87-853D-76
\virtual machines\intranet' is no longer accessible: The file cannot be accessed by the system. (0x80070780)
Cannot load a virtual machine configuration: Cannot create a file when that file already exists. (0x800700B7) (Virtual machine ID 8413B873-FC21-4DAB-8DBD-9A
Cannot load a virtual machine configuration: The data is invalid. (0x8007000D) (Virtual machine ID 8413B873-FC21-4DAB-8DBD-9A
Cannot load a virtual machine configuration: General access denied error (0x80070005) (Virtual machine ID F7DB08A6-DD45-4C87-853D-76