From e1bbc4dd5e82794f1fb17efea60d03642824bd83 Mon Sep 17 00:00:00 2001 From: weihongmin1 Date: Mon, 2 Mar 2026 07:56:21 +0000 Subject: [PATCH] SDRS API 0228 Version Reviewed-by: Muller, Martin Co-authored-by: weihongmin1 Co-committed-by: weihongmin1 --- docs/sdrs/api-ref/en-us_topic_0108184469.html | 11 ++++++++--- docs/sdrs/api-ref/en-us_topic_0113127626.html | 6 +++--- docs/sdrs/api-ref/sdrs_05_0501.html | 5 +++-- 3 files changed, 14 insertions(+), 8 deletions(-) diff --git a/docs/sdrs/api-ref/en-us_topic_0108184469.html b/docs/sdrs/api-ref/en-us_topic_0108184469.html index dec19cec9..bfbb8056f 100644 --- a/docs/sdrs/api-ref/en-us_topic_0108184469.html +++ b/docs/sdrs/api-ref/en-us_topic_0108184469.html @@ -8,7 +8,12 @@ -

2025-10-20

+

2026-02-26

+ +

Added constraints in Creating a Protected Instance.

+ + +

2025-10-20

Optimized some descriptions.

@@ -97,7 +102,7 @@

2018-10-12

Modified the following content:

- +

2018-09-29

@@ -125,7 +130,7 @@

Added the following content:

Modified the following content:

-
  • Error code descriptions in Error Codes
  • Changed SDRS.0218 to SDRS.0219.
  • Descriptions of dr_type
+
  • Error code descriptions in Error Codes
  • Changed SDRS.0218 to SDRS.0219.
  • Descriptions of dr_type

Deleted the following content:

  • Section "Adding a NIC to a Protected Instance"
  • Section "Deleting a NIC from a Protected Instance"
diff --git a/docs/sdrs/api-ref/en-us_topic_0113127626.html b/docs/sdrs/api-ref/en-us_topic_0113127626.html index 17252fbe3..05ad82249 100644 --- a/docs/sdrs/api-ref/en-us_topic_0113127626.html +++ b/docs/sdrs/api-ref/en-us_topic_0113127626.html @@ -286,7 +286,7 @@

Invalid offset value. The value cannot be negative and must be an integer.

-

Use a valid offset value.

+

Use a valid offset value.

400

@@ -2168,7 +2168,7 @@

The subnet quota is insufficient.

-

Delete unused subnets or customer service to increase the subnet quota.

+

Delete unused subnets or contact customer service to increase the subnet quota.

400

@@ -2342,7 +2342,7 @@

Null value in the matches parameter

-

The value in the matches parameter is null.

+

The value in the matches parameter is null.

Enter the correct parameter value and then try again.

diff --git a/docs/sdrs/api-ref/sdrs_05_0501.html b/docs/sdrs/api-ref/sdrs_05_0501.html index c6d5bed1f..50392f350 100644 --- a/docs/sdrs/api-ref/sdrs_05_0501.html +++ b/docs/sdrs/api-ref/sdrs_05_0501.html @@ -5,7 +5,8 @@

Constraints and Limitations

  • status of the protection group must be available or protected.
  • No shared disk has been attached to the server.
  • One server can be used to create only one protected instance.
  • The server must be in the same VPC as the protection group.
  • The physical host housing the production site server cannot be a DeH.
  • If protection is enabled for servers created during capacity expansion of an Auto Scaling (AS) group, these servers cannot be deleted when the capacity of the AS group is reduced.
  • If the server at the production site runs Windows and you choose the key login mode, ensure that the key pair of the server exists when you create a protected instance. Otherwise, the server at the DR site may fail to create, causing the protected instance creation failure.

    If the key pair of the production site server has been deleted, create a key pair with the same name.

    -
  • After you create a protected instance and enable protection on servers at the production site, modifications to the Hostname, Name, Security Group, Agency, ECS Group, Tags, and Auto Recovery configurations of servers on the production site will not synchronize to the servers at the DR site. You can manually add the configuration items to the servers at the DR site on the management console.
+
  • After you create a protected instance and enable protection on servers at the production site, modifications to the Hostname, Name, Security Group, Agency, ECS Group, Tags, and Auto Recovery configurations of servers on the production site will not synchronize to the servers at the DR site. You can manually add the configuration items to the servers at the DR site on the management console.
  • GPU-accelerated, FPGA-accelerated, C6, C9, S9, I9, and M9 ECSs are not supported.
    • Kunpeng ECSs are not supported.
    • x86 ECSs with GPU-accelerated and FPGA-accelerated types are not supported.
    +

    • URI

    • URI format

      POST /v1/{project_id}/protected-instances

    • Parameter description @@ -161,7 +162,7 @@

      Type

      -

      Description

      +

      Description