• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Migrating VMs between clusters in vSphere 5.0 results in VMs being unprotected?

Duncan Epping · Mar 8, 2012 ·

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.

Share it:

  • Tweet

Related

BC-DR, Storage 5.0, ha, vSphere

Reader Interactions

Comments

  1. James Hess says

    8 March, 2012 at 17:23

    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…

    • Scott says

      29 September, 2012 at 01:22

      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¢

      • Duncan says

        29 September, 2012 at 07:49

        Then don’t do it, it is your environment not mine 🙂

  2. Duncan Epping says

    8 March, 2012 at 17:37

    This is the recommend work around. Indeed it would leave your VMs temp unprotected.

    • Troy Clavell says

      8 March, 2012 at 17:58

      only applies to vMotion? If you cold migrate a guest this is still applicable?

  3. Duncan Epping says

    8 March, 2012 at 19:18

    Doesn’t apply to cold migration.

  4. Martin says

    8 March, 2012 at 20:06

    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

  5. Soran says

    23 March, 2012 at 12:09

    I had the same problems. disabled HV&DRS for the cluster and reenabled and now all VMs are HV protected

  6. Cedrick says

    28 August, 2012 at 20:11

    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.

Primary Sidebar

About the author

Duncan Epping is a Chief Technologist in the Office of CTO of the Cloud Platform BU at VMware. He is a VCDX (# 007), the author of the "vSAN Deep Dive", the “vSphere Clustering Technical Deep Dive” series, and the host of the "Unexplored Territory" podcast.

Upcoming Events

Feb 9th – Irish VMUG
Feb 23rd – Swiss VMUG
March 7th – Dutch VMUG
May 24th – VMUG Poland
June 1st – VMUG Belgium

Recommended Reads

Sponsors

Want to support Yellow-Bricks? Buy an advert!

Advertisements

Copyright Yellow-Bricks.com © 2023 · Log in