All vRealize Operations Manager clusters consist of a master node, an optional replica node for high availability, optional data nodes, and optional remote collector nodes.

When you install vRealize Operations Manager, you use a vRealize Operations Manager vApp deployment, Linux installer, or Windows installer to create role-less nodes. After the nodes are created and have their names and IP addresses, you use an administration interface to configure them according to their role.

You can create role-less nodes all at once or as needed. A common as-needed practice might be to add nodes to scale out vRealize Operations Manager to monitor an environment as the environment grows larger.

Master Node

The initial, required node in the cluster. All other nodes are managed by the master node.

In a single-node installation, the master node must also perform data collection and analysis because it is the sole node, and the only place where vRealize Operations Manager adapters are installed.

Data Node

In larger deployments, additional data nodes have adapters installed to perform collection and analysis.

Larger deployments usually include adapters only on data nodes, not on the master node or replica node.

Replica Node

To enable high availability (HA), the cluster requires that you convert a data node into a replica of the master node.

Remote Collector Node

Distributed deployments might require a remote collector node that can navigate firewalls, interface with a remote data source, reduce bandwidth across data centers, or reduce the load on the vRealize Operations Manager analytics cluster. Remote collectors only gather objects for the inventory, without storing data or performing analysis. In addition, remote collector nodes may be installed on a different operating system than the rest of the cluster nodes.


The main part of the cluster that does not include remote collector nodes is informally referred to as the analytics cluster.

There are some additional things to keep in mind about vRealize Operations Manager node behavior.

Cluster nodes often need to communicate with one another. When performing cluster-level actions, required node communication might cause unexpected behaviors.

For example, any manual or system action that restarts the cluster brings all vRealize Operations Manager nodes online, including any nodes that you had taken offline.

When the nodes in a vRealize Operations Manager cluster are virtual machines, you only update their virtual machine software by directly updating the vRealize Operations Manager software.

For example, going outside of vRealize Operations Manager to access vSphere to update VMware Tools is not supported.