Resizing a virtual server instance

You can resize your virtual server instance and vertically scale to any supported profile size in minutes. You can increase or decrease the amount of vCPU and RAM available for greater flexibility in workload management to address resource requirement changes, optimize cost or workload performance.

Virtual servers are configured by using profiles, or a combination of instance attributes, such as the number of vCPUs, amount of RAM, network bandwidth, and more that define the size and capabilities of the virtual server instance. When you upgrade or downgrade an existing server, you choose another profile that has the pre-defined specifications that you need. You cannot customize the configuration of a virtual server. The virtual server profile that you select determines the valid cores, RAM, bandwidth, and disk sizes on the resized instance. For more information about profiles, see Instance Profiles.

When you resize an instance, keep the following information in mind:

You need to stop, update, and start the instance that you want to resize
Data isn't deleted from the primary volume or the data volume
RAM is wiped from the resized instance
All network configurations are maintained, such as private IPs, floating IPs, vNICs, and security groups
The instance name doesn't change
The location doesn't change. The location includes the location geography, region, and zone that were used when creating the virtual server instance.
You must select a secure execution enabled profile when you want to resize an IBM Cloud Hyper Protect Virtual Servers for IBM Cloud® Virtual Private Cloud instance. Selecting a profile that is not secure execution enabled will cause the provisioning to fail.

After the instance is resized, you are billed the hourly rate of the new instance profile.

You can track the instance resize in Activity Tracker and IBM® Log Analysis for troubleshooting and audit purposes.

Resizing virtual servers on dedicated hosts

Virtual servers that run on dedicated hosts can be resized only to profiles that are supported by the dedicated host that the instance is hosted on. For example, a virtual server that is provisioned with a profile from the Memory family can resize to other profiles that belong to the Memory family.

Resizing virtual servers on dedicated hosts is not supported for LinuxONE (s390x processor architecture).

Resizing virtual servers with instance storage

When you stop a virtual server instance with an instance storage profile, that storage is temporary storage and is available only while your virtual server is running. Data on the drive is unrecovered after the instance stops.

Resizing virtual servers with data volumes

Attached data volumes remain intact and are attached in the resized instance.

When resizing an instance to a smaller profile (one with fewer vCPUs), it might be necessary to adjust the instance’s storage bandwidth allocation. To successfully resize, the instance’s storage bandwidth must be at least 500 Mb/s less than the preallocated bandwidth in the target profile.

For example:

Current profile: mx2-8x64 (total bandwidth: 16000 Mb/s, 12000 Mb/s network, 4000 Mb/s storage) (Assume that the instance is using default network and storage bandwidth allocation.)
Target profile: bx2-2x8 (total bandwidth: 4000 Mb/s, 3000 Mb/s network, 1000 Mb/s storage)

The resize operation will fail because the current amount of storage bandwidth (4000 Mb/s) is not at least 500 Mb/s less than the target profile’s total bandwidth (4000 Mb/s). To successfully resize, you must adjust the instance’s storage bandwidth amount to 3500 Mb/s or less prior to attempting the resize operation.

Resizing instances associated with instance templates and instance groups

When you resize an instance that's provisioned from an instance template or that's provisioned as part of an instance group, the following rules apply.

An instance that is provisioned from an instance template can be resized with a new instance profile.
Instance templates are not editable, except for the name. You cannot update an instance profile within an instance template. To choose a different profile for an instance template, you must create a new template.
Resizing an instance that is part of an instance group removes it from the instance group. An instance must be stopped to resize it. When the instance is stopped, the instance group replaces it with a new instance with the same profile as the instance template describes.

Resizing instances between Gen 2 and Gen 3 profiles

3rd generation profiles are available in the Dallas, London, Frankfurt, Washington DC, Toronto, and Madrid regions to provision virtual server instances on 4th Generation Intel® Xeon® Scalable processors, the Intel 8474C processor (previously code named Sapphire Rapids). For more information about the capabilities of the new profiles, see Next generation instance profiles.

You can resize a 2nd generation profile to a 3rd generation profile. A 3rd generation profile can be resized to a 2nd generation profile. Before resizing between profile generations, review the following information.

Prior to resizing an instance with a 2nd generation profile to a 3rd generation profile, take a snapshot of the boot volume that is attached to your virtual server instance. You can refer back to the snapshot if needed.
When you resize an instance to a 3rd generation profile, the virtual firmware defaults to Open Virtual Machine Firmware (OVMF) if your image supports UEFI. If the instance previously booted with SeaBIOS, the system attempts to preserve the firmware setting even when moving to the latest generation. If the virtual firmware changes from SeaBIOS to OVMF during the migration to the new profile, the device names might appear differently in the guest.
If you resize from a 3rd generation profile to a 2nd generation profile, any changes made to your virtual server instance while running with the 3rd generation profile are preserved. If you have the snapshot available that you took prior to migrating to the new profile, you can restore from that snapshot if something goes wrong.

When you deploy a new Windows virtual server instance with a 3rd generation profile, avoid resizing to a 2nd generation profile. The new Windows instance uses OVMF virtual firmware and cannot be resized to a 2nd generation profile as the instance will not boot. If the Windows virtual server instance was originally provisioned with a 2nd generation profile, then resized to a 3rd generation profile, it can be resized back to a 2nd generation profile successfully.

Resizing a virtual server instance by using the UI

Complete the following steps to resize an existing virtual server instance.

From the IBM Cloud Console menu, select Virtual server instances.
From the Virtual server instances for VPC list, find the virtual server that you want to resize and verify that its status is Stopped or Stopping.
Select the vertical ellipsis, and select Resize.
From the list of available profiles, select the profile that you want to use.
- If you are resizing a virtual server that is running on a dedicated host, you see only profiles that the dedicated host supports.
- If you are resizing a Hyper Protect Virtual Servers for VPC instance, ensure that you select a secure execution enabled profile. Similarly, don't select a secure execution enabled profile for an instance that doesn't support secure execution.
Review and check the Terms and Conditions.
Select Resize virtual server instance.
Start the virtual server instance.

Resizing a virtual server by using the CLI

Use the instance-update command to resize a virtual server.

ibmcloud is instance-update <instance> --profile <profile>

Where:

instance is the ID or Name of the instance that you want to resize
profile is the Name of the profile that you want to use

As an example, if you want to resize an instance to the bx2-16x64 profile, the command would look similar to the following example.

ibmcloud is instance-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --profile bx2-16x64

Resizing a virtual server by using the API

Use the instance-update command to resize a virtual server.

Run the following command to find the name of the profile that you want to use:

curl  -s -X GET "<api_endpoint>/v1/instance/profiles?generation=2&version=2021-02-01" -H "Authorization: Bearer <IAM token>"

Select a compatible profile for your instance.
- For a virtual server that is running on a dedicated host, choose a profile that the dedicated host supports.
- If you use instance storage, choose a profile that has instance storage.
- For data volumes, choose a profile that has data volumes.

Run the following command:

curl -k -sS -X PATCH "<api_endpoint>/v1/instances/<instance id>?generation=2&version=2021-02-01" \
    -H "Authorization: Bearer <IAM token>" \
    -d '
{
    "profile": {
       "name": "<new profile>"
    }
} '

Where:

instance-id is the ID of the instance that you want to resize
profile-id is the ID of the profile that you want to use

Resize a virtual server and reservations

Keep the following information in mind when you resize a virtual server that's in a reservation. For more information about reservations, see About Reservations for VPC.

If the instance that you want to resize is attached to a reservation, the instance profile can't update if the profile doesn't match the profile of its associated reservation.

If the instance that you want to resize is a new profile, you need to first detach the instance from the reservation. The instance profile can then be updated and then a new reservation attached to the instance with a matching profile.