2018-09-29
@@ -105,7 +110,7 @@Added the following content:
- Descriptions of the job execution status in Querying the Job Status
- Descriptions of the active-active domain in Querying an Active-Active Domain
- Error codes SDRS.0221 and SDRS.0222
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"
Creating a Protected Instance
Function
This API is used to create a protected instance. When a protected instance is created, the default name of the server at the DR site is the same as that of the server at the production site, but their IDs are different. To modify a server name, click the server name on the protected instance details page to switch to the server details page and modify the server name. Alternatively, you can call the API in Changing the Name of a Protected Instance to modify the name.
Constraints and Limitations
- status of the protection group must be available or protected.
- No shared disk has been attached to the server.
- No protected instance has been created using the server.
- 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.
+@@ -161,7 +161,7 @@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.
Type
Description
+Description