Starting with vRealize Lifecycle Manager 8.2, Vertical Scale Up is introduced to increase the RAM, disk capacity, or vCPUs in the nodes of a cluster. The nodes of a cluster are grouped and each group consists of nodes of equal sizes. A product can have a single group or multiple groups, and if the node sizes vary across the different groups, you can scale up to standardize the node sizes.
Day 2 operations include the Vertical Scale Up operation to manage environments and avoid any performance degradation. Vertical Scale Up is supported for vRealize Log Insight, vRealize Operations, vRealize Network Insight, and VMware Identity Manager. You can increase the storage capacity for a product by scaling up the current size and adding a disk with the required capacity.
Verify that you have an existing private cloud environment in vRealize Suite Lifecycle Manager that contains supported vRealize Suite products.
- From the vRealize Suite Lifecycle Manager dashboard, click Manage Environments.
- Click View Details for a vRealize Suite product.
- Click the ellipsis (...) for the product level operation, and then select Vertical Scale Up.
- In the Proceed to Vertical Scale Up pop-up window, click Trigger Inventory Sync.
- Click Proceed when the inventory sync is complete.
- Select the Node Type, and then click Next.
- Under Vertical Scale-Up Details, select Scale Up Size from the drop-down menu. You can select the Additional Disk Size (optional).
- Under Advanced Settings, select the appropriate datastore for the nodes from the drop-down menus, and then click Next.
- Click RUN PRECHECK.
Note: If the validation is successful, a successful validation message appears. If you see an error message, follow the instructions provided in the Recommendations tab, and then click RE-RUN PRECHECK.
- When the validation succeeds, click Submit to view the details of your request.
Note: For VMware Identity Manager (vIDM), the default vIDM deployment option and vRealize Automation specified size of 8 CPU and 16 GB memory are supported. To increase the storage capacity from the additional disk space provided to vIDM, 70% can be assigned to /db and 30% to /var.