VMware vR Ops 6.x changes

VMware vR Ops 6.x changes

The last couple of weeks I’ve been busy with a couple vR Ops designs and implementation in very different environments, and the question I get a lot is what the differences are between vCOPS and vR Ops. First of all I must point at the naming difference where vR stands for v Realize and Operation manager has become a part of much larger suite. A suite that will give you the opportunity to leverage, monitor, automate and build hybrid cloud environments.

Back to the question:

The vR Ops architecture consists of 1 Virtual Machines (VM) that works on a scale out basis, which differs from ealier version that consisted of a vApp with 2 VM’s and which was based on a Scale-up architecture. You’ll get a better picture looking at figure 1 and reading the information below.


















As shown in the figure above, the deployment of vR Ops starts with a single VM (which will become the Master Node) and can easily be scaled out with additional nodes (which can be data nodes or remote collectors). To provide HA ,a master node can have a replica node (holding the same data as the MasterNode) which will take over if the master node fails. see the figure below for more information.

Screen Shot 2014-11-08 at 1.47.10 pmThe Master node as well as a replica node holds the Global xDB and is responsible for collecting data from the vCenter Server, other vR Ops suite product and 3rd party data sources (metrics, topology and change events) and storing that raw data in its scalable File System Database (FSDB).

I’ll dive into other differences and more in depth posts in a later stage, but for now I just wanted to get this information out 😉

Read More