As your business grows, the compute resources (vCPUs and memory), storage resources (system disk capacity), and network resources (data transfer quota and public bandwidth) of your server may no longer meet your business requirements. You can upgrade the configuration of your Simple Application Server by selecting a suitable plan.
Limits
You can only upgrade plans. You cannot downgrade plans.
You can only upgrade the entire plan. You cannot upgrade individual resources, such as the system disk, memory, or bandwidth, separately.
You cannot upgrade across instance families or disk types.
You cannot upgrade a server from one instance family to another. The instance families are: General-purpose, CPU-optimized, Multiple public IPs, International, Storage-optimized, and Previous generation.
You cannot change the disk type when you upgrade a previous generation plan. For example, you cannot upgrade from a standard SSD to an enterprise SSD (ESSD).
If the current plan for the instance family is already the highest configuration, you cannot upgrade it.
If you use a previous generation plan and the current plan for the disk type is already the highest configuration, you cannot upgrade it.
Impacts of an upgrade
Affected Items | Description |
System disk | If the upgrade involves resizing the system disk, you must resize the partition and file system after the plan upgrade for the new disk capacity to take effect. |
Bandwidth and traffic |
|
Business | The server restarts during the upgrade. Perform the upgrade during off-peak hours. |
Other | The server's public and private IP addresses, operating system, firewall, snapshots, custom images, and expiration time remain unchanged. |
Billing
When you upgrade a plan, the system calculates the price difference between the old and new plans. You must pay this difference. The actual price difference is displayed on the upgrade page.
Preparations
Before you upgrade, create a snapshot of the system disk for your Simple Application Server to back up your data. For more information, see Create a snapshot.
An upgrade failure may cause data loss. Before you upgrade, create a snapshot to back up your data. Creating a snapshot takes some time. Wait for the snapshot creation process to complete.
Procedure
Step 1: Upgrade the plan
Go to the Servers page in the Simple Application Server console.
On the server card, choose .
NoteIf the Upgrade button is grayed out, the current plan is already the highest configuration and cannot be upgraded. For more information, see Q2: Why is the Upgrade button grayed out?.

In the Precautions for Server Configuration Upgrade dialog box, read the notes and click Go to Upgrade Page.
In the Plan Configuration section, select the plan to which you want to upgrade.
You can view the configuration fee in the lower-right corner of the page.
In the Terms of Service section, read the agreements and confirm that you agree to them.
Click Buy Now. On the Payment page, confirm the order information and complete the payment as prompted.
Return to the Simple Application Server console. The server automatically restarts after the upgrade. The upgrade is successful when the server status changes to Running.
Step 2: (Conditionally required) Resize the partition and file system
If the plan upgrade includes an increase in system disk capacity, you must resize the partition and file system for the new capacity to take effect. Otherwise, you can skip this step.
Resize the partition and file system (Linux)
In this example, the system disk capacity is 40 GB before the upgrade and 50 GB after the upgrade.
The default device name of the system disk in a Simple Application Server is /dev/vda.
Remotely connect to the upgraded Linux server.
For more information, see Connect to a Linux server.
View the information about the disk and partition on the server.
Run the following command to view the disk information of the server.
sudo fdisk -luBecause the data disk on the server is not involved in the configuration upgrade, this example focuses on the system disk (
/dev/vda).
The following describes the information in the figure:Area ① in the figure: The capacity of the system disk (
/dev/vda) after the upgrade.Area ② in the figure: The
Devicecolumn shows the partition name of the system disk. TheSystemcolumn shows the partition type.Linuxindicates that the partition type is Master Boot Record (MBR). The default partition name of the system disk of a Simple Application Server is/dev/vda1, and the default partition type is MBR.
Run the following command to view the partition information.
df -ThThe default file system type of the system disk partition (
/dev/vda1) in a Simple Application Server isext4. The result in the following figure shows that the file system size is still 40 GB, which is the size before the upgrade. This means you need to resize the partition and the file system.
Resize the partition.
Run the following command to install the growpart tool.
The command that you need to run varies based on the operating system. The following commands are used as examples:
Alibaba Cloud Linux 2/3, CentOS 7 and later
sudo yum install -y cloud-utils-growpartDebian 9 and later, Ubuntu 14 and later
Update the software source.
sudo apt-get updateInstall cloud-guest-utils.
sudo apt-get install -y cloud-guest-utils
Run the following command to resize the partition.
NoteIn the command parameters, a space is required between
/dev/vdaand1.1is the partition number.sudo growpart /dev/vda 1The following figure shows the result.
If an error occurs when you run the command in this step, you can manually troubleshoot the issue. For more information, see FAQ.
Resize the file system.
Because the default file system type of the system disk partition (
/dev/vda1) in a Simple Application Server is ext4, this step describes how to resize an ext4 file system.Run a command to resize the file system based on its type.
ext4 file system
sudo resize2fs /dev/vda1xfs file system
sudo xfs_growfs /dev/vda1
Run the following command to check the result.
df -ThThe result in the following figure shows that the file system size is 50 GB, which indicates that the resize is successful.
After the resize is complete, verify that your data is intact.If the resize is successful and the applications on the server run as expected, the operation is complete.
If the resize fails, roll back the disk using the snapshot backup. For more information, see Roll back a disk using a snapshot.
Resize the file system (Windows)
In this example, the server runs the 64-bit Windows Server 2012 R2 operating system. The system disk (C drive) capacity is 40 GB before the upgrade and 60 GB after the upgrade.
Remotely connect to the upgraded Windows server.
For more information, see Connect to a Windows server.
In the lower-left corner of the Windows desktop, right-click the Start
icon and click Disk Management.
As shown in the following figure, the Disk Management window displays the unallocated capacity of the system disk after the upgrade.

Right-click the primary partition of Disk 0 and select Extend Volume.

In the Extend Volume Wizard, follow the wizard and use the default settings to extend the volume.
After the extend volume operation is complete, the new space is automatically added to the original volume, as shown in the following figure.

After the resize is complete, verify that your data is intact.
If the resize is successful and the applications on the server run as expected, the operation is complete.
If the resize fails, roll back the disk using the snapshot backup. For more information, see Roll back a disk using a snapshot.
FAQ
Q1: Can I upgrade resources in a plan, such as the system disk or bandwidth, separately?
Q2: Why is the Upgrade button grayed out?
References
If your system disk has insufficient storage space, you can attach a data disk to increase the storage capacity. This is an alternative to upgrading the plan. For more information, see Attach a data disk.
If the used space on a data disk becomes insufficient due to business growth, you can resize the data disk to increase its storage capacity. For more information, see Resize a data disk.
