The vRealize Operations clusters consist of a master node, an optional replica node for high availability, optional data nodes, and optional remote collector nodes.
You can access and interact with the product by using the product UI available on the master and data nodes. The remote collector nodes do not contain a product UI and are used for data collection only. The product UI is powered by a Tomcat instance that resides across each node but is not load balanced out of the box. You can scale up vRealize Operations environment by adding nodes when the environment grows larger.
vRealize Operations supports high availability by enabling a replica node for the vRealize Operations master node. A high availability replica node can take over the functions that a master node provides. When a problem occurs with the master node, fail-over to the replica node is automatic and requires only 2 to 3 minutes of vRealize Operations downtime. Data stored on the master node is always backed up on the replica node. In addition, with high availability enabled, the cluster can survive the loss of a data node without losing any data.
Node Role |
Functions |
|---|---|
Master Node |
It is the initial, required node in the cluster. All other nodes are managed by the master node. It contains the product UI. In a single-node installation, the master node performs data collection and analysis as it is the only node where vRealize Operations adapters are installed. |
Data Node |
In larger deployments, only data nodes have adapters installed to perform collection and analysis. It contains the product UI. |
Replica Node |
To enable high availability, the cluster requires that you convert a data node in to a replica of the master node. It does not contain product UI. |
