Quantcast
Channel: Hyper-V forum
Viewing all articles
Browse latest Browse all 8743

HyperV and Failover Cluster Disjoined

$
0
0

Windows 2008 R2:

I've got an odd one where I can't seem to make heads or tails of. In my environment I have 3 servers acting in a Hyper V failover cluster. We've been having issues where when we attempt to Live Migrate a VM from one host to another, move or do storage migration the Hyper V Console reports a correct configuration but the Failover Cluster does not.

Example:  I did an export of a VM and an Import of the VM.  Hyper V Manager and SCVMM reports that the VM's storage is in the new location.  The VM is online and running.  I can remote desktop into the VM, I can ping the VM and the VM is working as expected.  However, I'm getting errors in the Event Log every hour and in the Failover Cluster Manager the VM is offline with an error.  The event log errors in the System log are as follows:

EventID:  1205 Source:  FailoverClustering

The Cluster service failed to bring clustered service or application 'VMName' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

EventID:  21502 Source:  Hyper-V-High-Availability

'SCVMM VMName Configuration' failed to unregister the virtual machine with the virtual machine management service.

EventID: 

EventID:  21502  Source:  Hyper V-High-Availability

'SCVMM VMName Configuration' failed to register the virtual machine with the virtual machine management service.

The Virtual Machine Management Service failed to register the configuration for the virtual machine 'EEDD18D9-83C7-4D2B-B7A2-E8D88869987C' at 'C:\ClusterStorage\Volume4\Virtual Machines\VMName': Cannot create a file when that file already exists. (0x800700B7)

Note:  The C:\ path above is the OLD path where the VM was located, not the new one.

Doing a quick Google I found that we should be restarting the Cluster Service to resolve this on one of the hosts.  However, this happens every time we do anything with the VM"s.  Live Migrate, Move Storage, etc.  Restarting the Cluster Service kind of defeats the purpose of being able to Live Migrate a VM.  Is there a better solution?


Dmox


Viewing all articles
Browse latest Browse all 8743

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>