ApsaraDB RDS:Change the storage type from Premium Local SSD to Premium ESSD or ESSD

Differences between high-performance local disks and cloud disks

Billing rules

The fee for changing the storage type depends on the region where your instance is located and the selected specifications. You can view the fee during the configuration change process.

Usage notes

• You can change the storage type only from Premium Local SSD to Premium ESSD or standard ESSD. You cannot reverse this change.

• Premium Local SSDs and ESSDs support different instance types. For some instance types, you must change the instance type when you switch from a Premium Local SSD to an ESSD. For more information about the supported instance types, see Primary ApsaraDB RDS for MySQL instances.

• The change operation is affected by various factors and may fail. For more information, see What factors affect the time that is required to change the specifications of an ApsaraDB RDS for MySQL instance?.

• The change process uses incremental data synchronization. If your application writes a large amount of data during the change, data synchronization to the target disk may lag. This may prevent the change from being completed. To ensure that the change is completed in a timely manner, we recommend that you reduce the frequency of data writes during the process.

• Before changing the storage type, ensure at least 10% of disk space remains free. If the disk space is exhausted, the instance is locked. For more information, see Resolve an RDS for MySQL instance locked due to storage exhaustion by data files.

Impacts

• Changing the storage type may trigger underlying data migration. After the migration is complete, the system performs a switchover of your workloads at the scheduled time. During the switchover, a transient disconnection that lasts about 15 seconds occurs. We recommend that you change the storage type during off-peak hours and make sure that your application is configured with an automatic reconnection mechanism.

  Note

  Changing the storage type does not change the connection address of the instance. You do not need to update your application.

• After the change, backup sets that are created before the change cannot be used to restore the upgraded instance that uses Premium ESSDs or standard ESSDs. You can use only backup sets that are created after the change for restoration.

• While the storage type is being changed, you cannot perform instance-level operations, such as upgrading or downgrading the instance, upgrading the database engine version, or migrating the instance across zones.

• Switching from a Premium Local SSD to a Premium ESSD or standard ESSD disables the full cross-region backup feature automatically due to differences in underlying storage architectures. After the change, you must reconfigure your cross-region backup policy to ensure continued cross-region backup capability. For more information, see Enable cross-region backup for an ApsaraDB RDS for MySQL instance.

Procedure

1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

2. In the Basic Information section, click Configuration Information, then click Change Specifications on the right.

   

3. On the Change Instance Type page, set Storage Type to Premium ESSD or ESSD (PL1, PL2, or PL3).

   In some zones, resources may be insufficient or cloud disks may be unavailable for purchase. As a result, you may be unable to set the storage type to a cloud disk. In this case, you can migrate the instance to a zone where cloud disks are available for purchase and then upgrade the storage type to a cloud disk.

   Note

   • The three enterprise SSDs have the following performance specifications:

     • Performance ranking: PL3 > PL2 > PL1.

     • A PL3 ESSD delivers up to 20 times the IOPS and 11 times the throughput of a PL1 ESSD.

     • A PL2 ESSD delivers up to twice the IOPS and throughput of a PL1 ESSD.

   • The minimum disk space for a PL1 ESSD, PL2 ESSD, and PL3 ESSD is 20 GB, 500 GB, and 1,500 GB, respectively.

   • The minimum disk space of a Premium ESSD is 10 GB.

4. Optional: Select a new instance type.

   1. First, for Classification, select General or Dedicated.

      Classification	Description	Features
      General-purpose	Exclusively occupies: memory and I/O. Shared: CPU and storage.	Cost-effective.
      Dedicated	Exclusively uses CPU, memory, storage, and I/O resources. Note Dedicated host is the highest configuration of the Dedicated family. A dedicated host RDS instance exclusively uses all CPU, memory, storage, and I/O resources of its host.	Better performance and stability.

   2. Select a specific instance type based on the number of CPU cores and memory size.

      • For test environments, we recommend that you select an instance type with one or more CPU cores.

      • For production environments, we recommend that you select an instance type with four or more CPU cores.

      Note

      For more information about the supported instance types, see Primary ApsaraDB RDS for MySQL instances.

5. Optional: You can increase or decrease the storage capacity as needed.

   Note

   The storage capacity of the cloud disk must be at least 1.2 times the used storage space of the original Premium Local SSD.

6. Select the Switching Time, which is when the primary/secondary switchover occurs after the storage type upgrade is complete.

   • Execute Immediately

   • Switch Within Maintenance Window: The system performs the switchover within the maintenance window.

   Note

   • The switchover causes a transient disconnection that lasts about 15 seconds. We recommend that you perform the change during off-peak hours and make sure that your application is configured with an automatic reconnection mechanism.

   • If you select Switch Within Maintenance Window, the instance remains in the Upgrading state until the switchover completes. During this time, you cannot perform instance-level operations such as upgrading or downgrading the instance, upgrading the database engine version, or migrating across zones.

7. You can read and accept the terms of service, click Pay Now, and complete payment.

   After payment, the instance status changes to Upgrading. When the status changes to Running, the upgrade is complete.

FAQ

Related API operations