Configure your initial deployment of vRealize Operations Manager based on anticipated usage.
Analytics nodes consist of master nodes, master replica nodes, and data nodes.
For enterprise deployments of vRealize Operations Manager, deploy all nodes as medium or large deployments, depending on 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. vRealize Operations Manager supports various node sizes.
Table 1. Analytics Nodes Deployment 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 Add Disk Space to a vApp Node or Add Disk Space to Linux or Windows 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.2 supports up to 16 analytic nodes in a cluster.
To maintain a supported configuration, analytics nodes deployed in the cluster must be the same node size.
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
Endpoint Operations Management Agents