diff --git a/docs/rds/umn/ALL_META.TXT.json b/docs/rds/umn/ALL_META.TXT.json index 42feb58f7..18f594659 100644 --- a/docs/rds/umn/ALL_META.TXT.json +++ b/docs/rds/umn/ALL_META.TXT.json @@ -1681,7 +1681,7 @@ "node_id":"en-us_topic_scale_cluster.xml", "product_code":"rds", "code":"94", - "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.If your storage space usage reaches up to 95% for a disk l", + "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.You are advised to set alarm rules for the storage space u", "doc_type":"usermanual", "kw":"scale up storage space,scale up storage space,MySQL,Scaling up Storage Space,Instance Modifications,", "search_title":"", @@ -3373,7 +3373,7 @@ "node_id":"rds_pg_scale_cluster.xml", "product_code":"rds", "code":"188", - "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.The DB instance needs to preserve at least 15% of its capa", + "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.You are advised to set alarm rules for the storage space u", "doc_type":"usermanual", "kw":"scale up storage space,scale up storage space,Scaling up Storage Space,Instance Modifications,User G", "search_title":"", @@ -4813,7 +4813,7 @@ "node_id":"rds_sqlserver_scale_cluster.xml", "product_code":"rds", "code":"268", - "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.The DB instance needs to preserve at least 15% of its capa", + "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.You are advised to set alarm rules for the storage space u", "doc_type":"usermanual", "kw":"scale up storage space,scale up storage space,Scaling up Storage Space,Instance Modifications,User G", "search_title":"", diff --git a/docs/rds/umn/CLASS.TXT.json b/docs/rds/umn/CLASS.TXT.json index 020149081..9e33688e5 100644 --- a/docs/rds/umn/CLASS.TXT.json +++ b/docs/rds/umn/CLASS.TXT.json @@ -837,7 +837,7 @@ "code":"93" }, { - "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.If your storage space usage reaches up to 95% for a disk l", + "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.You are advised to set alarm rules for the storage space u", "product_code":"rds", "title":"Scaling up Storage Space", "uri":"en-us_topic_scale_cluster.html", @@ -1683,7 +1683,7 @@ "code":"187" }, { - "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.The DB instance needs to preserve at least 15% of its capa", + "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.You are advised to set alarm rules for the storage space u", "product_code":"rds", "title":"Scaling up Storage Space", "uri":"rds_pg_scale_cluster.html", @@ -2403,7 +2403,7 @@ "code":"267" }, { - "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.The DB instance needs to preserve at least 15% of its capa", + "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.You are advised to set alarm rules for the storage space u", "product_code":"rds", "title":"Scaling up Storage Space", "uri":"rds_sqlserver_scale_cluster.html", diff --git a/docs/rds/umn/en-us_topic_0000001191146839.html b/docs/rds/umn/en-us_topic_0000001191146839.html index 8b7c5e6fc..3f1f08a93 100644 --- a/docs/rds/umn/en-us_topic_0000001191146839.html +++ b/docs/rds/umn/en-us_topic_0000001191146839.html @@ -8,7 +8,13 @@ -

2024-08-26

+

2024-10-12

+ +

Modified the following content:

+ + + +

2024-08-26

Modified the following content:

Supported PostgreSQL 16. Added RDS for PostgreSQL Versioning Policy.

diff --git a/docs/rds/umn/en-us_topic_0000002023864553.html b/docs/rds/umn/en-us_topic_0000002023864553.html index 6e93bc4df..5e09d909c 100644 --- a/docs/rds/umn/en-us_topic_0000002023864553.html +++ b/docs/rds/umn/en-us_topic_0000002023864553.html @@ -18,7 +18,20 @@ -

15

+

16

+ +

Commercial use

+ +

September 2023

+ +

November 2028

+ +

August 2024

+ +

November 2029

+ + +

15

Commercial use

@@ -83,19 +96,6 @@

January 2025

-

16

- -

Commercial use

- -

September 2023

- -

November 2028

- -

August 2024

- -

November 2029

- - diff --git a/docs/rds/umn/en-us_topic_scale_cluster.html b/docs/rds/umn/en-us_topic_scale_cluster.html index c08ec94d5..681f49a5f 100644 --- a/docs/rds/umn/en-us_topic_scale_cluster.html +++ b/docs/rds/umn/en-us_topic_scale_cluster.html @@ -2,11 +2,38 @@

Scaling up Storage Space

Scenarios

If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.

-

If your storage space usage reaches up to 95% for a disk less than 1 TB or the remaining space becomes 50 GB for a disk no less than 1 TB, the DB instance status becomes Storage full and data cannot be written to databases. In this case, scale up storage space to make the DB instance preserve at least 15% of its capacity to work properly.

You are advised to set alarm rules for the storage space usage by referring to Setting Alarm Rules.

-

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

RDS allows you to scale up storage space of DB instances but you cannot change the storage type. During the scale-up period, services are not interrupted.

+

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 Available Storage 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.
+
+
+

Constraints

Scaling up a Primary DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  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:

    @@ -17,7 +44,7 @@

    If the DB instance is running the MySQL DB engine, you can view the detailed progress and result of the task on the Task Center page. For details, see section 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.

+

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 and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click in front of it. Locate a 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 target DB instance to enter the Basic Information page. In the Storage Space area, click Scale.

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

    The minimum increment for each scaling is 10 GB.

    diff --git a/docs/rds/umn/rds_01_0029.html b/docs/rds/umn/rds_01_0029.html index 05dfb5fa0..996b7b0fb 100644 --- a/docs/rds/umn/rds_01_0029.html +++ b/docs/rds/umn/rds_01_0029.html @@ -145,39 +145,17 @@

    32

    -

    Dedicated

    +

    Dedicated

    -

    rds.mysql.x1.medium.2.ha

    +

    rds.mysql.x1.large.2.ha

    -

    rds.mysql.x1.medium.2.rr

    +

    rds.mysql.x1.large.2.rr

    -

    rds.mysql.x1.medium.2

    +

    rds.mysql.x1.large.2

    -

    1

    +

    2

    -

    2

    - - -

    rds.mysql.x1.medium.4.ha

    - -

    rds.mysql.x1.medium.4.rr

    - -

    rds.mysql.x1.medium.4

    - -

    1

    - -

    4

    - - -

    rds.mysql.x1.large.2.ha

    - -

    rds.mysql.x1.large.2.rr

    - -

    rds.mysql.x1.large.2

    - -

    2

    - -

    4

    +

    4

    rds.mysql.x1.large.4.ha

    @@ -476,40 +454,18 @@

    32

    -

    Dedicated

    +

    Dedicated

    -

    rds.pg.x1.medium.2.ha

    +

    rds.pg.x1.large.2.ha

    -

    rds.pg.x1.medium.2.rr

    +

    rds.pg.x1.large.2.rr

    -

    rds.pg.x1.medium.2

    +

    rds.pg.x1.large.2

    -

    1

    +

    2

    -

    2

    - - -

    rds.pg.x1.medium.4.ha

    - -

    rds.pg.x1.medium.4.rr

    - -

    rds.pg.x1.medium.4

    - -

    1

    - -

    4

    - - -

    rds.pg.x1.large.2.ha

    - -

    rds.pg.x1.large.2.rr

    - -

    rds.pg.x1.large.2

    - -

    2

    - -

    4

    +

    4

    rds.pg.x1.large.4.ha

    diff --git a/docs/rds/umn/rds_pg_scale_cluster.html b/docs/rds/umn/rds_pg_scale_cluster.html index 7edfb55d6..1f09632a7 100644 --- a/docs/rds/umn/rds_pg_scale_cluster.html +++ b/docs/rds/umn/rds_pg_scale_cluster.html @@ -2,10 +2,38 @@

    Scaling up Storage Space

    Scenarios

    If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.

    -

    The DB instance needs to preserve at least 15% of its capacity to work properly. The new minimum storage space required to make this instance available has been automatically calculated for you. You are advised to set alarm rules for the storage space usage by referring to Setting Alarm Rules.

    -

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

    +

    You are advised to set alarm rules for the storage space usage by referring to Setting Alarm Rules.

    RDS allows you to scale up storage space of DB instances but you cannot change the storage type. During the scale-up period, services are not interrupted.

    +

    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 Available Storage 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.
    +
    +
    +

    Constraints

    • The maximum allowed storage is 4,000 GB. There is no limit on the number of scale-ups.
    • For primary/standby DB instances, scaling up the primary DB instance will cause the standby DB instance to also be scaled up accordingly.
    • You cannot reboot or delete a DB instance that is being scaled up.
    • Storage space can only be scaled up.
    • If you scale up a DB instance with disks encrypted, the expanded storage space will be encrypted using the original encryption key.

    Scaling up a Primary DB Instance

    1. Log in to the management console.
    2. Click in the upper left corner and select a region and a project.
    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
    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:

      @@ -15,7 +43,7 @@

    5. View the scale-up result.

      Scaling up storage space takes 3-5 minutes. During the time period, the status of the DB instance on the Instances page will be Scaling up. Click the DB instance and view the utilization on the displayed Basic Information page to verify that the scale-up is successful.

    -

    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.

    +

    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 and a project.
    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
    4. On the Instances page, locate the target DB instance and click in front of it. Locate a 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 target DB instance to enter the Basic Information page. In the Storage Space area, click Scale.

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

      The minimum start value of each scaling is 10 GB. A read replica can be scaled up only by a multiple of 10 GB. The allowed maximum storage space is 4,000 GB.

      diff --git a/docs/rds/umn/rds_sqlserver_scale_cluster.html b/docs/rds/umn/rds_sqlserver_scale_cluster.html index c12ce6298..090289365 100644 --- a/docs/rds/umn/rds_sqlserver_scale_cluster.html +++ b/docs/rds/umn/rds_sqlserver_scale_cluster.html @@ -2,10 +2,38 @@

      Scaling up Storage Space

      Scenarios

      If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.

      -

      The DB instance needs to preserve at least 15% of its capacity to work properly. The new minimum storage space required to make this instance available has been automatically calculated for you. You are advised to set alarm rules for the storage space usage by referring to Setting Alarm Rules.

      -

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

      +

      You are advised to set alarm rules for the storage space usage by referring to Setting Alarm Rules.

      RDS allows you to scale up storage space of DB instances but you cannot change the storage type. During the scale-up period, services are not interrupted.

      +

      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 Available Storage 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.
      +
      +
      +

      Constraints

      • DB instances can be scaled up numerous times.
      • The maximum allowed storage is 4,000 GB. There is no limit on the number of scale-ups.
      • For primary/standby DB instances, scaling up the primary DB instance will cause the standby DB instance to also be scaled up accordingly.
      • You cannot reboot or delete a DB instance that is being scaled up.
      • Storage space can only be scaled up.
      • If you scale up a DB instance with disks encrypted, the expanded storage space will be encrypted using the original encryption key.

      Procedure

      1. Log in to the management console.
      2. Click in the upper left corner and select a region and a project.
      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
      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: