vRealize Operations Manager tracks and analyzes the operation of multiple data sources within the SDDC by using specialized analytic algorithms. These algorithms help vRealize Operations Manager to learn and predict the behavior of every object it monitors. Users access this information by using views, reports, and dashboards.


vRealize Operations Manager is available as a pre-configured virtual appliance in OVF format. Using the virtual appliance allows you to easily create vRealize Operations Manager nodes with pre-defined identical sizes.

You deploy the OVF file of the virtual appliance once for each node. After node deployment, you access the product to set up cluster nodes according to their role, and log in to configure the installation.


vRealize Operations Manager contains functional elements that collaborate for data analysis and storage, and support creating clusters of nodes with different roles. 

Figure 1. vRealize Operations Manager Architecture

The high-level architecture of a vRealize Operations Manager deployment includes a master node, master replica node, data node, and remote collector.

Types of Nodes

For high availability and scalability, you can deploy several vRealize Operations Manager instances in a cluster to track, analyze, and predict the operation of monitored systems where they can have either of the following roles.

Master Node

Required initial node in the cluster. In large-scale environments, manages all other nodes. In small-scale environments, the master node is the single standalone vRealize Operations Manager node.

Master Replica Node

Optional. Enables high availability of the master node. 

Data Node

Optional. Enables scale-out of vRealize Operations Manager in larger environments. Data nodes have adapters installed to perform collection and analysis. Data nodes also host vRealize Operations Manager management packs.

Remote Collector Node

Overcomes data collection issues, such as limited network performance, across the enterprise network. Remote collector nodes only gather statistics about inventory objects and forward collected data to the data nodes. Remote collector nodes do not store data or perform analysis.

The master and master replica nodes are data nodes that have extended capabilities.

Types of Node Groups

Analytics Cluster

Tracks, analyzes, and predicts the operation of monitored systems. Consists of a master node, data nodes, and optionally of a master replica node.

Remote Collector Group

Because it consists of remote collector nodes, only collects diagnostics data without storage or analysis.

Application Functional Components 

The functional components of a vRealize Operations Manager instance interact with each other to analyze diagnostics data from the data center and visualize the result in the Web user interface. 

Figure 2. vRealize Operations Manager Logical Node Architecture

The functional components in a vRealize Operations Manager master node include the product/admin UI and the Rest API, collector, transaction locator, transaction service, analytics, and databases.

The components of vRealize Operations Manager node perform these tasks:

Product/Admin UI and Suite API

The UI server is a Web application that serves as both user and administration interface, and hosts the API for accessing collected statistics.


The Collector collects data from all components in the data center.

Transaction Locator

The Transaction Locator handles the data flow between the master, master replica and remote collector nodes.

Transaction Service

The Transaction Service is responsible for caching, processing, and retrieving metrics for the analytics process.


The analytics engine creates all associations and correlations between various data sets, handles all super metric calculations, performs all capacity planning functions, and is responsible for triggering alerts.

Common Databases

Common databases store the following types of data that is related to all components of a vRealize Operations Manager deployment:

  • Collected metric data

  • User content, metric key mappings, licensing, certificates, telemetry data and role privileges

  • Cluster administration data

  • Alerts and alarms including the root cause, and object historical properties and versions

Replication Database

The replication database stores all resources, such as metadata, relationships and so on, collectors, adapters, collector groups, and relationships between them.

Authentication Sources

You can configure vRealize Operations Manager user authentication to utilize one or more of the following authentication sources:

  • vCenter Single Sign-On

  • VMware Identity Manager

  • OpenLDAP via LDAP

  • Active Directory via LDAP

Management Packs

Management packs contain extensions and third-party integration software. They add dashboards, alert definitions, policies, reports, and other content to the inventory of vRealize Operations Manager. You can learn more details about and download management packs from VMware Solutions Exchange.

Multi-Region vRealize Operations Manager Deployment

The scope of the VMware Validated Design for Software-Defined Data Center uses vRealize Operations Manager in a large scale implementation designed across multiple regions. This is achieved through the use of a load balancer configured for the analytics cluster running multiple nodes that are protected by Site Recovery Manager to failover across regions and multiple remote collector nodes assigned to a remote collector group in each region.