Help Center/ TaurusDB/ User Guide/ Instance Management/ Configuration Changes/ Manually Changing the Storage Capacity of an Instance
Updated on 2026-10-19 GMT+08:00
View PDF
Share

Manually Changing the Storage Capacity of an Instance

Scenarios

For yearly/monthly DB instances, the initially requested storage space may not always match actual usage as your data changes. TaurusDB lets you manually scale up or down storage capacity to suit your needs.

Storage of pay-per-use DB instances cannot be manually scaled up. This is because there is no limit on their storage capacity, and storage is automatically scaled up or down based on usage.

You do not need to purchase storage for serverless DB instances. You will be billed based on the actual usage. To adjust the compute configuration of a serverless DB instance, see Changing the Compute Range of a Serverless Instance.

Scaling up or down the storage space of a yearly/monthly DB instance does not interrupt your workloads or affect backups.

Constraints

  • You can manually change storage capacity by a multiple of 10 GB. You can only scale down storage of a DB instance to an amount higher than the actual used storage.
  • You can change the storage capacity of a DB instance as many times as needed.
  • If the storage space of a DB instance is being changed, you cannot reboot or delete the DB instance.

Billing

Table 1 Billing

Billing Mode

Operation

Impact on Price

Yearly/Monthly

Manually scaling up storage

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

The following prices are for reference only. The actual prices are displayed on the console.

Suppose you purchased a one-month TaurusDB cluster instance (instance specifications: dedicated, 2 vCPUs | 8 GB, 2 nodes; storage: DL6, 10 GB) in CN-Hong Kong on April 1, 2025. The unit price of storage is $0.6 USD/GB per month.

On April 15, 2025, you scaled up the storage by 50 GB. The total storage after scale-up is 60 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 April)/30 (Maximum number of days in April) = 0.5. Price difference = 50 GB x $0.6 USD/GB x 0.5 = $15 USD

Manually scaling down storage

After a scale-down, the new storage capacity takes effect within the original subscription period.

TaurusDB refunds the difference in price based on the remaining subscription period.

Example (The prices below are for reference only. The actual prices are displayed on the console.)

Suppose you purchased a one-month TaurusDB cluster instance (instance specifications: general-purpose, 2 vCPUs | 8 GB, 2 nodes; storage: DL6, 50 GB) in CN-Hong Kong on April 1, 2025. The unit price of storage is $0.6 USD/GB per month.

On April 15, 2025, you scaled down the storage capacity by 10 GB. The total storage capacity after the scale-down was 40 GB.

Price difference = Price of the original storage capacity x Remaining period – Price of the new storage capacity 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 refunded fees are calculated as follows: Remaining period = 15 (Remaining days in April)/30 (Maximum number of days in April) = 0.5. Refund = 50 x 0.6 x 0.5 - 40 x 0.6 x 0.5 = $3 USD

Yearly/Monthly

Automatically scaling up or down storage

For a yearly/monthly DB instance, the system allocates the storage space based on the storage you selected when buying the DB instance. If your purchased storage cannot meet your requirements, TaurusDB will automatically scale up the storage as needed and you will be billed on a pay-per-use basis for additional storage. For details, see Product Pricing Details. If workloads decrease later, the system preferentially scales down the storage that was automatically scaled up.

Suppose you selected 10 GB of storage when buying a DB instance. Later, as workloads increased, TaurusDB automatically scaled up the storage to 18 GB as needed and you would be billed on a pay-per-use basis for the additional 8 GB of storage. Then, you manually scaled up the storage to 20 GB, which could meet your requirements.

The 20 GB of storage will be billed on a yearly/monthly basis, whereas the 8 GB previously added through automatic scaling will be automatically scaled down and no longer incur pay-per-use fees.

Procedure

  1. Log in to the TaurusDB console.
  2. Click in the upper left corner and select a region.
  3. On the Instances page, locate the instance and choose More > Change Storage in the Operation column.

    Alternatively, click the instance name to go to the Basic Information page. In the Storage and Backup area, locate Storage Space and click Change Storage.
    Figure 1 Changing the storage capacity

  4. On the displayed page, select the new storage space and click Next.

    • Storage space can be scaled up to 128,000 GB only by a multiple of 10 GB. The price is displayed in the lower left corner of the page.
    • Storage space can be scaled down to 10 GB only by a multiple of 10 GB. The refund is displayed in the lower left corner of the page.

  5. Confirm your settings.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Pay Now.

  6. If you are scaling up the storage space, select a payment method on the displayed page and click Pay.
  7. View the new storage.

    On the Instances page, click the instance name to go to the Basic Information page and view the new storage.

APIs

Parent Topic: Configuration Changes