Over the past few weeks I’ve heard a whole lot of arguments around vCenter design considerations. A few of the questions asked were:

  • Do I install vCenter on 32 bit or 64 bit?
  • vCenter as a physical or Virtual machine?
  • vCenter Database – Local or Remote?
  • Placement of the Update Manager Server and Database

Before I dig into the vCenter design topic, I think it would be good to put some perspective on this post and why I’ve decided to blog on this. Last week I attended a meeting with some fellow virtualisation consultants and one of the topics raised in the meeting was to find a common standard practise between us regarding vCenter Server design and specifically the “default” stance between the consultants in regards to the placement of the vCenter server and whether it should be a physical or a virtual machine. Some consultants were in favour of the idea of a default stace and others were against the idea, stating that the decision of vCenter being hosted on a physical or virtual machine is down to the circumstances of each consultancy engagement. Thinking back now, I don’t think we came to an agreement in the end.

This post is basically my opinion on vCenter design, and the steps that I take in deciding what my infrastructure design will look like.

Published in vSphere: vCenter

When you start writing GraphQL queries with filters off the top of your head without even looking at the reference… https://t.co/AbqVRGr4S3
Follow Rynardt Spies on Twitter