vCenter Service crash during Vmotion

[jbsengineer]

During a maintenance mode enter operation and the VM's were being shuffled off ESX1 to other hosts we lost vCenter. The service stopped. I'm currently digging into why. However in the meantime I have a little issue. There is atleast 1 VM that vCenter believes is running ESX2 when if fact its actually running on ESX1. It looks as thought the vmotion completed successfully as the VM is running happily. I can VC client right to the ESX1 host to verify this. So to remedy this I plan on disconnecting both ESX1 and ESX2 from vCenter and do a reconnect. Which I hope should re-register the VM location correctly in VC.

So let me ask this. Once the vmotion is activated and running can ESX hosts complete the operation without VC? Obviously this leaves me in the situation I am in now (bad DB info). But I always wondered what would happen to the VM if this were to occur (vCenter crashing).

Thanks.

[jbsengineer]

Ok. So I disconnect/reconnected ESX1/ESX2. This orphaned the VM's on ESX2. My next plan of action was to offload the "good" VM's off of ESX1/ESX2 except for the 2 orphans and disconnect/remove from VC/and do an "Add Host..." which theoectically would re-register the running orphaned VM's into the VC DB. Am I correct with that assumption? Anyway while I was offloading the "good" VM's vCenter suddenly got smart and unorphaned the VM's and properly showed then on ESX1.

Anyone know what process in VC picked up on the fact the orphaned VM's were running on another host? This seemed to take almost an hour. Also would this have happened without me doing the initial disconnect/reconnect?

Thanks for any info