Help Center/ Relational Database Service/ User Guide/ Working with RDS for MySQL/ Instance Management/ Instance Modifications/ Scaling Up Storage Space
Updated on 2024-10-28 GMT+08:00
View PDF
Share

Scaling Up Storage Space

Scenarios

If the storage space is not enough for your workloads, you can scale up storage space of your DB instance. The backup space will also increase with the storage.

You can configure an alarm rule for the storage space usage, so you are alerted if the threshold is reached. For details, see Setting Alarm Rules.

During scale-up, services are not interrupted. If you need to change the storage type, refer to Instance Class Type Change.

Instance Becomes Read-Only When Storage Is Full

For details about the causes and solutions of insufficient storage space, see What Should I Do If My Data Exceeds the Database Storage Space of an RDS DB Instance?

Table 1 Conditions under which an instance becomes read-only if it is out of storage

Storage Size

Condition

Any storage size

If the available storage space is less than 5 GB, the instance becomes read-only.

NOTE:

This rule takes precedence over other rules that can be used to set the instance read-only.

Storage size is less than 1 TB.
  • If the storage usage reaches 97%, the instance becomes read-only.
  • If the storage usage decreases to 87%, the instance exits the read-only state.

Storage size is greater than or equal to 1 TB.
  • If the available storage space is less than 30 GB, the instance becomes read-only.
  • If the available storage space is greater than or equal to 150 GB, the instance exits the read-only state.
Figure 1 Checking storage usage

Constraints

  • You can scale up storage space only when your account balance is greater than or equal to $0 USD.
  • You can scale up storage space only when your instance status is Available or Storage full.
  • The maximum allowed storage is 4,000 GB. If you want to increase the storage upper limit to 10 TB, contact customer service.
  • When storage space is being scaled up, the DB instance is in Scaling up state and the backup tasks of the instance are not affected.
  • For primary/standby DB instances, scaling up the primary DB instance will cause the standby DB instance to also be scaled up accordingly.
  • Reboot is not required during scale-up.
  • You cannot reboot or delete a DB instance that is being scaled up.
  • Storage space can only be scaled up, not down.
  • If you scale up a DB instance with disk encryption enabled, the expanded storage space will also use the original key for encryption.

Billing

Table 2 Billing

Billing Mode

Operation

Impact on Fees

Yearly/Monthly

Storage scale-up

You need to pay for the difference in price based on the remaining period.

The following prices are for reference only. Final prices on the console may differ.

Suppose you purchased a one-month RDS for MySQL 5.7 single DB instance (instance class: general-purpose, 2 vCPUs | 8 GB; storage: cloud SSD, 40 GB) in CN-Hong Kong on June 1, 2023. The unit price of storage space is $0.214 USD/GB per month.

On June 15, 2023, you scaled up the storage by 60 GB. The total storage after scale-up is 100 GB.

Price difference = Scale-up volume x Unit price x Remaining period

The remaining period is the remaining days of each calendar month divided by the maximum number of days in each calendar month.

In this example, the remaining period and price difference are calculated as follows:

Remaining period = 15 (Remaining days in June)/30 (Maximum number of days in June) = 0.5

Price difference = 60 GB x $0.214 USD x 0.5 = $6.42 USD

Pay-per-use

Storage scale-up

The new storage space is billed by hour. For details, see Product Pricing Details.

Scaling Up a Primary DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region.
  3. Click in the upper left corner of the page and choose Databases > Relational Database Service.
  4. On the Instances page, locate the target DB instance and choose More > Scale Storage Space in the Operation column.

    You can also perform the following operations to scale up storage space:

    • Click the target instance name to enter the Overview page. In the Storage & Backup area, click Scale Storage Space.
    • If the storage space is full, locate the target DB instance on the Instances page and click Scale in the Status column.

  5. On the displayed page, specify the new storage space and click Next.

    The minimum increment for each scaling is 10 GB.

  6. Confirm specifications.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify the settings, click Submit for a pay-per-use instance or click Pay Now for a yearly/monthly instance.

  7. View the scale-up result.

    Scaling up storage space takes 3-5 minutes. During this time period, the status of the DB instance on the Instances page will be Scaling up. After a while, click the DB instance and view the new storage space on the displayed Overview page to verify that the scale-up is successful.

    You can view the detailed progress and result of the task on the Task Center page. For details, see Task Center.

Scaling Up a Read Replica

Scaling up the storage space of a read replica does not affect that of the primary DB instance. Therefore, you can separately scale read replicas to meet service requirements. New storage space of read replicas after scaling up must be greater than or equal to that of the primary DB instance.

  1. Log in to the management console.
  2. Click in the upper left corner and select a region.
  3. Click in the upper left corner of the page and choose Databases > Relational Database Service.
  4. On the Instances page, locate the target DB instance and click in front of it. Locate the read replica to be scaled and choose More > Scale Storage Space in the Operation column.

    You can also perform the following operations to scale up storage space:

    • Click the read replica name to enter the Overview page. In the Storage & Backup area, click Scale Storage Space.
    • If the storage space is full, locate the read replica on the Instances page and click Scale in the Status column.

  5. On the displayed page, specify the new storage space and click Next.

    The minimum increment for each scaling is 10 GB.

  6. Confirm specifications.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings and the read replica uses pay-per-use billing, click Submit.

  7. View the scale-up result.

    Scaling up storage space takes 3-5 minutes. During this time period, the status of the read replica on the Instances page will be Scaling up. After a while, click the read replica name and view the new storage space on the displayed Overview page to verify that the scale-up is successful.

    You can view the detailed progress and result of the task on the Task Center page. For details, see Task Center.

Parent Topic: Instance Modifications