The initial vCPU, memory, and disk resources available to a database VM are determined by the vCPU & Memory and Storage values that you selected when you created the database VM.
If you find that the database VM requires more or less resources, you can scale the vCPU and memory resource configuration up or down at runtime. Scaling the vCPU or memory is independent of the storage size; you can similarly and independently increase the size of the virtual disk in use by the database VM.
Sufficient resources must be available to scale the compute configuration or to extend the virtual disk; VMware Data Services Manager returns an error if there are insufficient resources to satisfy the request.
Only the owner of the database VM, the Organization Administrator, and the Provider Administrator have the privileges required to change the resources allotted to the database VM.
If the Namespace associated with a database VM is also associated with a Provider organization, the Provider Administrator can change compute configuration of such database VMs that are created by an Organization User or Organization Administrator.
Scaling the Compute Configuration
Depending upon the configuration of your Organization, you either explicitly select the new vCPU and memory amounts, or you choose from a predefined set of VM plans that provide vCPU/memory amount combinations.
Scaling vCPU or memory resources is an on-demand operation. When you initiate the operation, VMware Data Services Manager powers down the database VM, applies the new resource settings, and then powers the database VM back up. In addition to the service being offline during this period, the downtime affects currently running management tasks as follows:
- If an automated task is running when the scaling request is made, the task may fail, but will be automatically re-initiated in the next maintenance window.
- If scaling coincides with other running on-demand tasks, those tasks may also fail, and you may be required to re-initiate them.
Prerequisites
Before scaling the compute resources of a database VM, ensure that any currently running management and service tasks first complete, or are nonessential.
Procedure
Perform the following procedure to scale up or down the vCPU or memory resources allotted to a database VM:
Select Databases from the left navigation pane.
This action displays the Databases view, a table that lists the provisioned database VMs.
Examine the databases listed in the table, identify the database whose resource properties you wish to update, and navigate to that table row.
Click the database VM Name.
The database information Details tab displays.
Select the VM Settings tab.
This action displays information about the VM Configuration and the Environment in which the database VM runs.
Click the ACTIONS button in the top right corner of the view, and select Change Compute Configuration from the drop-down menu.
The Change Compute Configuration dialog displays. The fields available in the dialog will differ based on the configuration of your Organization.
Enter the the number of vCPUs and the amount of memory (in GBs) (You must provide both values.), or select from the predefined VM plan vCPU & Memory combinations.
Click SAVE to initiate the resource configuration changes.
VMware Data Services Manager generates a management operation of type SCALE_DB_CONFIG.
Monitor the progress of the task in the Operations tab or in the Operations view:
- Locate the SCALE_DB_CONFIG operation type and click it.
- Select the State History tab to view the subtasks of the operation and their status.
- If the operation fails, select the Error Info tab to examine the returned error information.
Extending the Virtual Disk Size
You may choose to extend the virtual disk size of a database VM when your data storage requirements for the service change. VMware Data Services Manager supports only extending the disk size; you can not reduce the size of the virtual disk.
Extending disk is an on-demand operation; VMware Data Services Manager immediately initiates the task, and performs the operation without any downtime to the database VM or the service.
By default, VMware Data Services Manager backs up the service before extending the virtual disk. While it is not recommended, you can omit this step if you choose.
Prerequisites
Before extending the virtual disk of a database VM, ensure that the database VM has no snapshots. The Determining if a virtual machine running on a snapshot and Managing snapshots in vSphere Web Client knowledge base articles may provide assistance here.
Procedure
Perform the following procedure to increase the virtual disk size of a database VM:
Select Databases from the left navigation pane.
This action displays the Databases view, a table that lists the provisioned database VMs.
Examine the databases listed in the table, identify the database whose properties you wish to update, and navigate to that table row.
Click the database VM Name.
The database information Details tab displays.
Select the VM Settings tab.
This action displays information about the VM Configuration and the Environment in which the database VM runs.
Click the ACTIONS button in the top right corner of the view, and select Extend Disk from the drop-down menu.
The Database Disk Extension dialog displays.
Examine the current Free Space in GB, and specify the amount to extend the disk size by in Extend Size in GB.
Note: VMware recommends that the extend size not exceed 90% of the current free space.If you choose to omit the backup step, click to un-check Backup Required.
Click SAVE to initiate disk extension.
VMware Data Services Manager generates a management operation of type EXTEND_DB_DISK. If a backup is required, it also generates a BACKUP_DB operation type.
Monitor the progress of the task(s) in the Operations tab or in the Operations view.
- Locate the EXTEND_DB_DISK operation type and click it.
- Select the State History tab to view the subtasks of the operation and their status.
- If the operation fails, select the Error Info tab to examine the returned error information.
