Scaling up a node in vRealize Operations Manager 6.x and later
search cancel

Scaling up a node in vRealize Operations Manager 6.x and later

book

Article ID: 344726

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

A vRealize Operations Manager node may need to be scaled up if the node has run out of space, to align with other node sizes, to resolve performance issues, or to account for new data.
Throughout the lifespan of a vRealize Operations Manager, the cluster may need to grow following the vRealize Operations Manager Sizing Guidelines.

​It is better to scale up before you scale out.
For more information on scaling out by adding additional nodes, see Expand an Existing Installation of vRealize Operations Manager.

Environment

VMware vRealize Operations Manager 6.7.x
VMware vRealize Operations 8.1.x
VMware vRealize Operations 8.10.x
VMware vRealize Operations 8.6.x
VMware vRealize Operations 8.2.x
VMware vRealize Operations Manager 7.0.x
VMware vRealize Operations Manager 6.6.x
VMware vRealize Operations 8.5.x
VMware vRealize Operations 8.4.x
VMware vRealize Operations 8.3.x
VMware vRealize Operations 8.0.x

Resolution

Important notes:
  • You cannot scale down a vRealize Operations Manager node.
  • All Analytic nodes must match in vCPU, RAM, and Disk.
  • Stay within the supported sizing guidelines for your version.
  • After resizing Analytic nodes, review remote collector sizes and consider the number of collecting objects per node to see if the remote collector size can, or needs to be increased.
To resize a vRealize Operations Manager node, follow the steps below.
  1. Log in to vRealize Operations Manager admin UI as the local admin user.
Examplehttps://IP_or_FQDN/admin

Note: Replace IP_or_FQDN with the actual IP or FQDN of vRealize Operations Manager UI.
  1. Click Take Offline under Cluster Status.
Note: Wait for Cluster Status to show as Offline.
  1. As an administrator, navigate to the node you want to scale up in the vSphere Web UI.
  2. Right-Click on the node and select Power > Shut Down Guest OS.
  3. Once the node is powered off, ensure the Virtual Hardware version is upgraded to the latest version:
  • Right-Click the node and click Compatibility > Upgrade VM Compatibility.
  • Read the warning and click Yes.
  • In the Compatible with box, select the desired compatibility level and click OK.
  1. Right-click on the node and select Edit Settings.
  2. Edit the CPU and/or Memory to the desired level, based on the vRealize Operations Manager Sizing Guidelines.
Note: To add disk space, follow steps 4-11 in Adding additional storage to a node in vRealize Operations Manager 6.x.
  1. Click OK.
  2. If the node selected in step 3 was an Analytic node, repeat steps 4-8 on all other Analytic nodes so their resources match.
  3. Right-click the node(s) and select Power > Power On.
  4. Once all nodes have powered back on, navigate back to the vRealize Operations Manager admin UI (https://IP_or_FQDN/admin) as the local admin user.
  5. Click Bring Online under Cluster Status.
Note: Wait for the Cluster Status to show as Online.

Additional Information

If the /storage/log partition fills up, see Safely cleaning up log files in vRealize Operations 6.x.

vRealize Operations Manager Sizing Guidelines
Adding additional storage to a node in vRealize Operations Manager 6.x and later
Upgrading the Virtual Hardware version of the vRealize Operations Manager 6.x and later Nodes