Configure your initial deployment of vRealize Operations Manager based on anticipated usage.

Analytics Nodes

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

For enterprise deployments of vRealize Operations Manager, deploy all nodes as 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 Manager supports various node sizes.

Table 1. Analytics Nodes Deployment Sizes

Node Size

vCPU

Memory

Extra small

2

8 GB

Small

4

16 GB

Medium

8

32 GB

Large

16

48 GB

Extra large

24

128 GB

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 Manager vApp Node. You cannot modify the disks of virtual machines that have a snapshot. You must remove all snapshots before you increase disk size.

Scaling Horizontally (Adding nodes)

vRealize Operations Manager 6.7 supports up to 6 extra large analytic nodes in a cluster.

To maintain a supported configuration, analytics nodes deployed in the cluster must be the same node size.

Remote Collectors

vRealize Operations Manager 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 Manager 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.

Table 2. Supported Remote Collector Sizes

Collector Size

Resources

End Point Operations Management Agents

Standard

6000

250

Large

32,000

2,000

For more information about sizing see the following KB article 54370.