Issues with migrating a Virtual Machine from one cluster to another
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
Remove the source cluster from management. Here i assume that the Migration Failed VM is part of this source cluster (i.e. the cluster that contains the host that had the VM in the first place before the migration was initiated)
Re-add the source cluster into VMM management. The VM in question should now be in a healthy state and running. Verify your VM is working properly in the source cluster. This is a very important step.
Go to the destination cluster (the cluster that contains the host you want to move the VM to) and cleanup the service that maps to this VM. You might also have to go to the destination hyper-v host and delete that VM that was created as a placeholder. This is a very important step. You need to ensure you are deleting the VM from the destination cluster [the VM should be working properly in the source cluster and DO NOT touch that]
Re-apply any metadata to the VMs of your source cluster after it was re-added into management by VMM. the blog post referenced above explains how to do that
Apply one or both of the workaround steps from this blog post for this issue
Refresh the source and destination clusters
Refresh the Virtual Machine that is going to be migrated
Start the migration of the VM from the source cluster to the destination cluster