if you have two Hyper-V failover clusters managed by VMM 2008 R2, it is possible that you can't migrate over the network (LAN migration) a VM from one of the clusters to the other cluster. This issue will only appear if ALL of the following conditions are met.
· VM is created using Hyper-V (i.e. the VM was not created through the VMM Administrator Console)
· VM is made into an HA VM using the FOC GUI (resource name will be called something like “Virtual Machine <vmname>”)
· VM is in a running state
· VM is migrated to a different cluster. VMM will chose QSM (Quick Storage Migration) network migration (LAN migration) in this case
· The migration job will always fail with the error below.
VMM cannot complete the WMI operation on server blre3r02-24a.DOM202594.LOCAL because of error: [MSCluster_ResourceGroup.Name="2068e895-4930-42be-a4c8-152ab15a28b8"] The cluster group could not be found.
(The cluster group could not be found (0x1395))
Resolve the issue and then try the operation again.
Currently there are two possible workarounds for this issue.
· If the VM is in a saved state, and not in a running state, at the beginning of the migration across the two clusters then this issue will not appear. Everything completes successfully in that case. So put the VM in a saved state and then initiate the migration.
· Use the Failover Cluster Manager User Interface to locate the Virtual Machine in "Services and Applications". Right click on the top resource group for this VM and change the Resource Name from "Virtual Machine <vmname>" to "SCVMM <vmname>". Now refresh this VM from VMM using the "refresh-vm -force '<vmname>'" cmdlet. Migrating the VM from one cluster to another should now complete successfully.
If you are already in a situation where your VM migration failed (the virtual machine should be in a migration failed state) because of the issue described in this blog post, there is only one way to get your VM in a healthy state. Follow these steps:
Now, take a full database backup of the DB used by VMM [Just in case; this is a safety net in case something goes wrong]
Use this blog post to save any metadata applied to the VMs in your cluster. http://blogs.technet.com/b/m2/archive/2010/04/16/saving-and-re-applying-the-virtual-machine-metadata-in-vmm.aspx