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

Yellow Bricks

by Duncan Epping

  • Home
  • Unexplored Territory Podcast
  • HA Deepdive
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

MSCS Clustered vCenter Server 4.x not supported?

Duncan Epping · Jul 16, 2010 ·

Yes you are reading it correctly. Today I was verifying links I added to a document. Both links referred to an MSCS based vCenter Server.

Although not everyone will have an environment where a Clustered vCenter Server is a must there are many where availability of vCenter is critical. To those who vCenter Server running clustered please note the following extract of a  newly published KB article:

vCenter Server 4.x has not been qualified with third party clustering products such as Microsoft Clustering Service and Veritas Cluster Services. VMware does not support third party clustering products.

This means that as mentioned in the KB article the only supported method to increase resilience of the vCenter Service currently is VMware Heartbeat.

Related

Server

Reader Interactions

Comments

  1. LucD says

    16 July, 2010 at 18:05

    I know the KB mentions HA as well but from your post it looks as if only VMware Heartbeat is supported.
    Or do I interpret this incorrectly ?

  2. Dave Lawrence says

    16 July, 2010 at 18:08

    Makes sense. VMware charges for heartbeat, they don’t make any money off MSCS.

    -Dave

  3. Jason Boche says

    16 July, 2010 at 18:11

    I belive Chris Skinner (my kick ass VI2 ICM instructor) wrote the vCenter clustering document.

    Duncan, how many customers do you know of that are providing high availability of vCenter outside of vCenter Heartbeat using either MSCS or Veritas?

  4. Duncan Epping says

    16 July, 2010 at 18:18

    @LucD, please note that I was talking about the vCenter Server service! Not the VM itself. HA would be perfect for VM level resiliency but currently not for service level resiliency.

  5. Duncan says

    16 July, 2010 at 18:54

    @Jason : I know many who use MSCS. Reason usually being that MSCS is their standard for App level clustering.

  6. Dave Crown says

    16 July, 2010 at 19:41

    its been a while since my 3.5 class, but is hosting the DB off box on an SQL Cluster supported?

  7. Duncan says

    16 July, 2010 at 20:04

    Yes Dave that is supported.

  8. cdm says

    19 July, 2010 at 10:34

    What’s all the fuss about MSCS? Its a primitive option at best. Just SAN boot your vCenter server and set up array based snapshots.

  9. Roggy says

    19 July, 2010 at 11:11

    Not Support/Not qualified is not the same thing.

    I’m going to play around with this in a lab, but my bet is that you can do it, but either they haven’t got around to qualifying it yet or it will be an unsupported option.

  10. Carlos says

    19 July, 2010 at 23:50

    The KB states that “VMware does not support third party clustering products” but in the vSphere 4.1 “Setup for Failover Clustering and Microsoft Cluster Service” guide we can read the following sentence clearly “VMware® vSphere supports clustering using MSCS across virtual machines”.

  11. Duncan Epping says

    20 July, 2010 at 15:24

    Yes Carlos but those are two different things
    1) clustering of virtual machines on ESX/vSphere
    2) clustering of the product vCenter

  12. burdweiser says

    21 July, 2010 at 20:07

    I’m sure you can get vCenter to work with MSCS, but they clearly state they are not going to support any MSCS issues. If something goes wrong, VMware just directs you to get with Microsoft (and the endless vendor loop begins). Maybe there is a way to get vCenter to work on windows 95, but I’m sure VMware won’t support it. I like VMware Heartbeat, it has some cool features. I can’t knock them for the change, it’s just another way for a business to make money.

  13. virtuallysi says

    13 August, 2010 at 10:42

    It’s a shame VMware don’t support vCenter with a 1 vCPU configuration. That way you could protect vCenter by using FT. They could stipulate that they will only support this configuration if the vCenter database is installed on a clustered\resilient server and not installed locally on the FT enabled vCenter VM. Obviously this configuration would make the need for VMware Heartbeat obsolete so it would never happen.

  14. RameshGeddam says

    19 August, 2010 at 18:24

    Hi Duncan,

    Nice information!

    I believe there is a slight change here. Further to statement of third party clustering solutions, there is some more info….

    http://kb.vmware.com/kb/1024051

    “VMware will provide support for any issues encountered with an environment that uses third party solutions for protecting against VMware vCenter Server downtime. However if your issue is deemed to be related to the third party clustering solution, VMware will refer to our third-party software policy.”

    Which mean, cross product support for customer still exists. Means, vmware will provide support for vCenter server downtime, if the issue is with MSCS, then customer has to run through MS which is nothing but cross product support.

    So bottom line, we CAN set it up!

  15. forex says

    20 September, 2010 at 13:18

    I have been previously exploring for a time for that good study dealing with this unique idea . Researching in Yahoo and google I eventually picked up this blog post. Looking at this data So i’m pleased to imply that I get a nice sense I uncovered exactly what I wanted. I’ll ensure to remember this website and look it over constantly.

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist and Distinguished Engineering Architect at Broadcom. Besides writing on Yellow-Bricks, Duncan is the co-author of the vSAN Deep Dive and the vSphere Clustering Deep Dive book series. Duncan is also the host of the Unexplored Territory Podcast.

Follow Us

  • X
  • Spotify
  • RSS Feed
  • LinkedIn

Recommended Book(s)

Advertisements




Copyright Yellow-Bricks.com © 2025 · Log in