Configure your initial deployment of vRealize Operations based on the anticipated use.

For more information about sizing, see the KB article vRealize Operations Manager Sizing Guidelines (KB 2093783).

Analytics Nodes

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

For enterprise deployments of vRealize Operations, deploy all nodes as medium, large or extra-large deployments, depending on sizing requirements and your available resources.
Scaling Vertically by Adding Resources
If you deploy analytics nodes in a configuration other than large, you can reconfigure the vCPU and memory. It is recommended to scale up the analytics nodes in the cluster before scaling out the cluster with additional nodes. vRealize Operations supports various node sizes.
Scaling Vertically by Increasing Storage
You can increase storage independently of vCPU and Memory.
To maintain a supported configuration, data nodes deployed in the cluster must be the same node size.
For more information about increasing storage, see the topic, Add Data Disk Space to a vRealize Operations vApp Node. You cannot modify the disks of virtual machines that have a snapshot. You must remove all snapshots before you increase the disk size.
Scaling Horizontally (Adding nodes)
vRealize Operations supports up to eight extra-large analytics nodes in a cluster, or up to 10 extra-large nodes in a cluster when continuous availability is enabled.
To maintain a supported configuration, analytics nodes deployed in the cluster must be the same node size.
Witness Node
vRealize Operations provides a single size regardless of the cluster size since the witness node does not collect nor process data.
Remote Collectors
vRealize Operations supports two sizes for remote collectors, standard and large. The maximum number of resources is based on the aggregate resources that are collected for all adapters on the remote collector. In large scale vRealize Operations monitored environment, you might experience a slow responding UI, and metrics are slow to be displayed. Determine the areas of the environment in which the latency is greater than 20 milliseconds and install a remote collector in those areas.
Cloud Proxy
vRealize Operations supports two sizes for Cloud Proxy, small and large. The maximum number of resources is based on the aggregate resources that are collected for all adapters on the Cloud Proxy. In large scale vRealize Operations monitored environment, you might experience a slow responding UI, and metrics are slow to be displayed. Determine the areas of the environment in which the latency is greater than 20 milliseconds and install a remote collector Cloud Proxy in those areas.