Today on the community forums someone mentioned an issue where his VMs were not protected by vSphere HA after they had been migrated between clusters. After reading it I vague recalled this being a known issue. I dug up the KB and the work around is fairly simple:
- Disable HA on the cluster where the unprotected VM resides
- Enable HA on the cluster again
If you need to do a lot of migrations to a different cluster you can also temporarily disable HA, migrate all VMs and then enable it again. This leads to the same result as above, all VMs will be protected again. This is on the radar of our developers and they are working on fixing this in a future release.
Scary… with this issue, would right clicking the host, and choosing disconnect, then reconnect, or Configure HA, fix unprotected on the VMs living on that host?
It seems like disabling+re-enabling HA entirely would leave the entire cluster unprotected from a failure in between the time it is disabled, and the time you turn it back on…
It took me longer to read your response that it did to disable and re-enable HA in my cluster. Seems like the benefits WAAAAY outweigh the negatives.
Just my 2¢
Then don’t do it, it is your environment not mine 🙂
This is the recommend work around. Indeed it would leave your VMs temp unprotected.
only applies to vMotion? If you cold migrate a guest this is still applicable?
Doesn’t apply to cold migration.
I have been holding back on upgrading to v5 because of wanting for such things to be discovered and fixed. Hopefully it will be fixed with update 1 as I really want to upgrade soon
Thanks for the article and pointing the KB
I had the same problems. disabled HV&DRS for the cluster and reenabled and now all VMs are HV protected
Thanks for sharing alway your discoveries. Your posts are always very useful – as this one in which i ran into today.
The workaround works perfect.