ApsaraDB RDS:Configure automatic storage expansion for an ApsaraDB RDS for SQL Server instance

Prerequisites

• Your RDS instance uses cloud disks and runs RDS High-availability Edition or RDS Cluster Edition.

  Note

  • You cannot separately configure automatic storage expansion for read-only RDS instances.

  • For more information about how to configure automatic storage expansion for RDS instances that run different database engines, see the following topics:

    • ApsaraDB RDS for MySQL instances: Use the automatic storage expansion feature for an ApsaraDB RDS for MySQL instance

    • ApsaraDB RDS for PostgreSQL instances: Use the automatic storage expansion feature for an ApsaraDB RDS for PostgreSQL instance

• The balance of your Alibaba Cloud account is sufficient to pay for the resources that are required to expand the storage.
• A service-linked role is created for DAS. For more information, see AliyunServiceRoleForDAS role.
  Note If the role does not exist, a service-linked role is automatically created for DAS when you enable the automatic storage expansion feature.

Usage notes

From February 28, 2023, the automatic storage expansion feature is optimized for database instances in different regions. If your instance has read-only instances, DAS automatically checks the storage capacity of each read-only instance when automatic storage expansion is enabled for the primary instance. If the storage capacity of one or more read-only instances is smaller than that of the primary instance, DAS first scales up the storage capacity of the read-only instances. After the storage capacity of each read-only instance is scaled up, DAS automatically scales up the storage capacity of the primary instance. For more information, see [Notice] Optimization of automatic storage expansion for ApsaraDB RDS for MySQL instances and ApsaraDB RDS for PostgreSQL instances.

Billing

The billing rules for automatic storage expansion are the same as those for manual storage expansion of ApsaraDB RDS instances. For more information, see Specification changes.

Procedure

1. Log on to the DAS console.
2. In the left-side navigation pane, click Instance Monitoring.
3. On the page that appears, click the ID of the database instance that you want to manage. The instance details page appears.
4. In the left-side navigation pane, click Autonomy Center.
5. On the Autonomy Center tab, click Autonomy Service Settings in the upper-right corner.
6. On the Autonomous Function Settings tab of the Autonomous Function Management panel, turn on the switch.
7. On the Optimization and Throttling tab, select Automatic Space Expansion and specify the parameters that are described in the following table.

   Parameter	Description
   Available Storage Space	When the remaining storage of the database instance is less than or equal to the value specified by the Available Storage Space parameter, the system automatically expands the storage based on the larger value of the following items: Storage capacity of 5 GB 15% of the current storage capacity of the instance
   Maximum Storage of Automatic Expansion	The maximum storage capacity that is allowed by automatic storage expansion. The value of this parameter must be greater than or equal to the current storage capacity of your database instance. If your instance uses ESSDs, the maximum value of this parameter can be set to 32,000 GB. If your instance uses standard SSDs, the maximum value of this parameter can be set to 6,000 GB. Note The standard SSD storage type is phased out. We recommend that you upgrade the storage type to ESSDs. For more information, see Upgrade the storage type of an ApsaraDB RDS for MySQL instance from standard SSDs to ESSDs.

   Note The interval between two storage expansions is at least 10 minutes.
8. In the message that is displayed, click OK.

Billing

The billing rules for automatic storage expansion are the same as those for manual storage expansion of ApsaraDB RDS instances. For more information, see Specification changes.