Skip to main content
Use Resize on the instance page to select another VM size. Suji stops the VM, requests the size change and starts it again. Your apps are unavailable during this operation. Allow a maintenance window; completion time is not guaranteed.

​
Choose what to change

The system disk cannot shrink. Keeping its current size can preserve flexibility for later CPU and memory changes. A snapshot also cannot be restored onto a disk smaller than the snapshot’s required disk size. To move to a smaller disk, create a suitable new VM and migrate app data separately. Availability depends on the selected size, region and current VM configuration. Review the options and price shown in the form before submitting.

​
Before resizing

  1. Check Metrics to confirm whether CPU, memory or disk is the constraint.
  2. Create a snapshot or application backup. Resize does not automatically take a snapshot for you. Back up attached volumes separately.
  3. Allow for app shutdown and restart, and pause work that should not be interrupted.
  4. Submit the resize during your maintenance window.
  5. After completion, check the reported size, available disk space, app logs and public endpoints.
Resize is designed to preserve the existing system disk and app data. It is still an infrastructure operation; a tested backup is your recovery option if something goes wrong.

​
Billing

The selected size has its own VM usage rate. A completed resize records the new rate for subsequent usage while preserving earlier rate periods. The usual VM billing rules still apply, including charges while stopped. Attached volumes, snapshots and optional managed backups have their own charges; review billing and the resize price before proceeding.

​
If the resize fails

Check Activity and the instance status. A failure can occur after the infrastructure has already changed size, so do not assume the VM is still on its old size or has restarted successfully. If the reported state and the VM do not agree, contact support before retrying or restoring. Resize requests run when submitted; arrange your maintenance window yourself.

​
Next

Snapshots and backups

Prepare and test a recovery point before maintenance.

Volumes

Add or grow separate block storage.