Help Center/ TaurusDB/ User Guide/ Instance Management/ Configuration Changes/ Configuring Autoscaling for a DB Instance (OBT)
Updated on 2025-08-21 GMT+08:00

Configuring Autoscaling for a DB Instance (OBT)

Scenarios

As your workloads grow, the used storage of a yearly/monthly DB instance may exceed the initially purchased storage. Additional storage will be billed on a pay-per-use basis. To better adapt to this change, TaurusDB provides storage autoscaling. When the required storage exceeds the initially purchased storage, the system will automatically scale up the storage and additional storage will be billed based on the storage prices for yearly/monthly subscriptions in TaurusDB Pricing Details. This meets workload growth needs while controlling costs effectively.

This section describes how to configure autoscaling after a DB instance is purchased.

Constraints

  • To use this function, submit a service ticket to obtain permissions.
  • You can only configure autoscaling when your account balance is greater than or equal to $0 USD and the instance status is Available.
  • If a yearly/monthly DB instance has pending orders, its storage cannot autoscale.
  • The maximum allowed storage for a DB instance is 128,000 GB.
  • If the product of the current storage and the increment is greater than the autoscaling limit, the storage can only autoscale to the limit.
  • Storage autoscaling is unavailable when the DB instance is in any of the following statuses: changing instance specifications, upgrading a minor version, and rebooting.

Billing

After the storage is automatically scaled up, you will be billed for the new storage based on the time remaining in the requested period of your instance. For details, see the storage prices for yearly/monthly subscriptions in TaurusDB Pricing Details.

Example:

If you have selected 40 GB storage when buying an instance but the storage used later has reached 60 GB, you can configure autoscaling as required.

  • If autoscaling is not configured, 20 GB (60 GB – 40 GB) will be billed on a pay-per-use basis.
  • If autoscaling is configured, the new storage will be billed on a yearly/monthly basis, and any additional storage will still be billed on a pay-per-use basis.

    For example, if the storage autoscales from 40 GB to 50 GB, 50 GB will be billed on a yearly/monthly basis, and the remaining 10 GB (60 GB – 50 GB) will be billed on a pay-per-use basis. If the storage autoscales to 70 GB, 70 GB will be billed on a yearly/monthly basis. Since the used storage is less than the new storage, no additional pay-per-use billing is required.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and project.
  3. Click in the upper left corner of the page and choose Databases > TaurusDB.
  4. On the Instances page, click the instance name to go to the Basic Information page.
  5. In the Storage and Backup area, click before Auto Scale-up.

    Figure 1 Viewing storage space

  6. In the displayed dialog box, set required parameters.

    Figure 2 Configuring autoscaling

    Table 1 Parameter description

    Parameter

    Description

    Enable autoscaling

    If you toggle on this switch, autoscaling is enabled.

    Trigger If Available Storage Drops To

    If the available storage drops to a specified threshold or 10 GB, autoscaling is triggered.

    Value: 5%, 10%, 15%, or 20%

    Autoscaling Limit (GB)

    The default value is 128000.

    The value must be a multiple of 10 and greater than both the total storage and the used storage of the instance.

    Increment

    Percentage of allocated storage that is automatically scaled up each time.

    Value range: 5%–50%

  7. Click OK.
  8. In the Storage and Backup area on the Basic Information page, check that Auto Scale-up is enabled.