Creates a replication pair-consistent group.
Operation description
Usage notes
The replication pair-consistent group feature allows you to batch manage multiple disks in disaster recovery scenarios. You can restore the data of all disks in the same replication pair-consistent group to the same point in time to allow for disaster recovery of instances.
Take note of the following items:
- For information about the regions in which the replication pair-consistent group feature is available, see Overview .
- Replication pair-consistent groups can be used to implement disaster recovery across zones within the same region and disaster recovery across regions.
- A replication pair and a replication pair-consistent group can replicate in the same direction if they have the same primary region (production region), primary zone (production zone), secondary region (disaster recovery region), and secondary zone (disaster recovery zone). A replication pair can be added to only a replication pair-consistent group that replicates in the same direction as the replication pair.
- After replication pairs are added to a replication pair-consistent group, the recovery point objective (RPO) of the group takes effect on the pairs instead of their original RPOs.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| ebs:CreateDiskReplicaGroup | Write |
|
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| RegionId | string | Yes | The ID of the region in which to create the replication pair-consistent group. The primary site is deployed in the specified region. | cn-beijing |
| SourceZoneId | string | Yes | The zone ID of the primary site. | cn-beijing-f |
| DestinationRegionId | string | Yes | The region ID of the secondary site. | cn-shanghai |
| DestinationZoneId | string | Yes | The zone ID of the secondary site. | cn-shanghai-e |
| GroupName | string | No | The name of the replication pair-consistent group. The name must be 2 to 128 characters in length. The name must start with a letter and cannot start with | myreplicagrouptest |
| Description | string | No | The description of the replication pair-consistent group. The description must be 2 to 256 characters in length and cannot start with | This is description. |
| ClientToken | string | No | The client token that is used to ensure the idempotency of the request. You can use the client to generate the token, but you must make sure that the token is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length. For more information, see How to ensure idempotence. | 123e4567-e89b-12d3-a456-42665544**** |
| RPO | long | No | The RPO of the replication pair-consistent group. Unit: seconds. Valid value: 900. | 900 |
| Bandwidth | long | No | The bandwidth value. Unit: Mbit/s. Note
This parameter is not publicly available.
| 10240 |
| ResourceGroupId | string | No | The ID of the resource group to which the replication pair-consistent group belongs. | rg-acfmvs******* |
| Tag | object [] | No | The tags. Up to 20 tags are supported. | |
| Key | string | No | The key of tag N of the replication pair-consistent group. | tag-key |
| Value | string | No | The value of tag N of the replication pair-consistent group. | tag-value |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "C123F94F-4E38-19AE-942A-A8D6F44F****",
"ReplicaGroupId": "pg-xxxxxxx"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 403 | OperationDenied | The operation is not allowed. | The operation is not supported. |
| 403 | OperationDenied.InvalidStatus | The operation is not allowed in current status. | The operation is not supported in the current state. |
| 403 | OperationDenied.QuotaExceed | The operation is not allowed due to quota exceed. | The quota for performing this operation has been exceeded. |
| 403 | OperationDenied.TooMuchEmptyGroup | Operation failed because of too many empty groups. | You have created excessive empty replication pair-consistent groups. |
| 403 | Forbidden | User is not authorized to operate. | You are not authorized to manage the resource. Check the account permissions or contact the Alibaba Cloud account. |
| 403 | Forbidden.Action | User is not authorized to operate this action. | You are not authorized to perform this operation. Check the account permissions or contact the Alibaba Cloud account. |
| 404 | NoSuchResource | The specified resource does not exist. | The specified resource does not exist. |
| 500 | InternalError | The request processing has failed due to some unknown error, exception or failure. | An internal error has occurred. |
| 504 | RequestTimeout | The request is timeout, please try again later. | The request has timed out. Try again later. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation | ||||
|---|---|---|---|---|---|---|
| 2023-03-08 | The Error code has changed | see changesets | ||||
|