High availability creates a replica for the vRealize Operations Manager master node and protects the analytics cluster against the loss of a node.

Cluster Management

Clusters consist of a master node and a replica node.

When you enable High Availability, information is stored in two different analytics nodes within the cluster which consist of a master node, a replica node, or data nodes.

If either the master node or replica node is permanently lost, then you must disable and re-enable high availability to reassign the master role or replica role. This process, which includes a hidden cluster rebalance, can take a long time.

Analytics Nodes

Analytics nodes consist of a master node, replica node, and data nodes.

Enabling High Availability within vRealize Operations Manager is not a disaster recovery solution. Enabling High Availability duplicates data in the system, and doubles the system's compute and capacity requirements. When you enable high availability, you protect vRealize Operations Manager from data loss in the event that a single node is lost. If two or more nodes are lost, there may be permanent data loss.

Deploy all analytics nodes to separate hosts to reduce the chance of data loss in the event that a host fails. You can use DRS anti-affinity rules to ensure that VMs remain on separate hosts.

Remote Collectors

In vRealize Operations Manager 6.1 and later, you can create a collector group. A collector group is a collection of nodes (analytic nodes and remote collectors). You can assign adapters to a collector group, rather than assigning an adapter to a single node.

If the node running the adapter fails, the adapter is automatically moved to another node in the collector group.

Assign all normal adapters to collector groups, and not to individual nodes. Do not deploy hybrid adapters in collector groups. For more information about adapters, see the documentation for the specific adapters.