Mike's Realm chown -R us ./base

1Jul/110

vCenter: Physical or Virtual? High Availability? Clustered?

First please know that vCenter being down does not take your whole vSphere environment down.  It limits you on creating new tasks (like deploying a new VM from template) until vCenter is back up.  When vCenter is down HA/FT continue to function.

Physical or Virtual

vCenter is the heart of VMware's virtualized infrastructure, but many folks are reluctant to virtualize their vCenter.   Running vCenter as a VM is completely supported by VMware.  You get all kinds of benefits from running vCenter as a Virtual Machine:

  • HA will also protect vCenter in the event the host it is running on goes down
  • You can vMotion vCenter from one host to another for maintenance and other things
  • Prior to upgrading vCenter to a newer version you can snapshot to help with rolling back more easily
  • Best of all--You gain the benefit of virtualizing yet another system and move towards virtualizing 100% of your data center.

If you are thinking about Virtualizing vCenter glance over this page out of the VMware Library:
VMware Online Library: Install vCenter Server in a Virtual Machine

High Availability

First the biggest thing is that you should remember  HA/FT will continue to operate without vCenter--all decisions will be made using a snapshot of what the extra resources were in the cluster prior to vCenter going down.

Lets look at the major things vCenter does:

  • VMware Distributed Resource Scheduler (DRS)
  • VMware High Availability (HA)/Fault Tolerance (FT) - Configuration
  • VMware VMotion + Storage VMotion
  • VMware Update Manager (Guest and Host)

After reviewing those items--does anything stick out that makes you think vCenter needs to be up 24/7?  Would HA be sufficient protection so you only have a small amount of downtime in the event the host running your vCenter VM went down?  I think yes.

Clustered?

You can look into vCenter Server Heartbeat, this is licensed as an addon to vCenter.  vCenter Server Heartbeat is basically an Active/Passive cluster for vCenter that can be setup to run locally or across your WAN.  vCenter Server Heartbeat also has the advantage that it can protect more then just the vCenter, it also protects the addons like vCenter Converter and vCenter Update Manager--even Guided Consolidation can be protected.  It is more costly then just running vCenter as a VM and protecting it with HA but the benefit of having an Active/Passive clustered vCenter + addons across the LAN/WAN may be beneficial for your organization.

Microsoft Cluster Services / Veritas Cluster Services

vCenter can be protected via "third party solutions" such as MSCS or VCS and VMware will support you to some degree but they do not certify these configurations.  If you have an issue VMware may determine the cause to be the third party software and not be of much assistance beyond that...  If you are thinking of going this route read over this VMware KB: Supported vCenter Server high availability options

Share
Comments (0) Trackbacks (0)

No comments yet.


Leave a comment

No trackbacks yet.