Here's a great post our very own Michael Michael posted today that talks about an issue you may run into when using System Center Virtual Machine Manager 2008 trying to migrate 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.
For all the details including his suggested workaround see the following link:
J.C. Hornbeck | System Center Knowledge Engineer
The App-V Team blog: http://blogs.technet.com/appv/ The WSUS Support Team blog: http://blogs.technet.com/sus/ The SCMDM Support Team blog: http://blogs.technet.com/mdm/ The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ The OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/ The SCVMM Team blog: http://blogs.technet.com/scvmm/ The MED-V Team blog: http://blogs.technet.com/medv/ The DPM Team blog: http://blogs.technet.com/dpm/ The OOB Support Team blog: http://blogs.technet.com/oob/ The Opalis Team blog: http://blogs.technet.com/opalis
the steps in the link do work. our problem was that the migration job from one cluster to another originally failed because the VM was attached to the host server's physical DVD drive. after running through the "fix" steps in the link, we restarted the migration with the VM in a saved state (just to be safe) and the migration was successful.