Creates a replication pair-consistent group.
Operation description
Operation Description
Replication pair-consistent groups help you manage asynchronous replication for multiple disks in disaster recovery scenarios. You can centrally manage operations for these disks. The groups ensure that data on all disks can be recovered to the same point in time. This provides disaster recovery protection for one or more instances.
When you create a replication pair-consistent group, note the following:
For information about the regions that support replication pair-consistent groups, see Async replication overview.
Replication pair-consistent groups support asynchronous disaster recovery across zones in the same region or across regions.
A replication pair can be added to a replication pair-consistent group only if the pair and the group have the same data replication direction. This means their production regions, production zones, disaster recovery regions, and disaster recovery zones must be the same.
After a replication pair is added to a replication pair-consistent group, the original Recovery Point Object (RPO) of the pair becomes invalid. Data is then replicated based on the RPO of the group.
Try it now
Test
RAM authorization
Action | Access level | Resource type | Condition key | Dependent action |
ebs:CreateDiskReplicaGroup | create | *DiskReplicaGroup
| None | None |
Request parameters
Parameter | Type | Required | Description | Example |
RegionId | string | Yes | The ID of the region where the replication pair-consistent group resides. This is the same as the region of the production site. | cn-beijing |
SourceZoneId | string | Yes | The ID of the zone where the production site is located. | cn-beijing-f |
DestinationRegionId | string | Yes | The ID of the region where the disaster recovery site is located. | cn-shanghai |
DestinationZoneId | string | Yes | The ID of the zone where the disaster recovery site is located. | cn-shanghai-e |
GroupName | string | No | The name of the replication pair-consistent group. The name must be 2 to 128 characters in length. It must start with a letter or a Chinese character, 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 | A client token to ensure the idempotence of the request. Generate a unique value from your client for this parameter. The `ClientToken` parameter value 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 | integer | No | The recovery point objective (RPO) of the replication pair-consistent group, in seconds. The only supported value is 900. Valid values:
| 900 |
Bandwidth | integer | No | The bandwidth in Kbps. Note This parameter is not yet available. | 5 |
ResourceGroupId | string | No | The ID of the resource group to which the replication pair-consistent group belongs. | rg-acfmvs******* |
| Tag | array<object> | No | The tags to add to the resource. You can add up to 20 tags. | |
object | No | |||
Value | string | No | The value of the tag. | tag-value |
Key | string | No | The key of the tag. | tag-key |
EnableRtc | boolean | No | Specifies whether to enable replication time control (RTC). Valid values:
Default value: false. Note If you set this parameter to true, RTC is enabled for the replication pair-consistent group. RTC is also enabled for all asynchronous replication pairs that are added to the group. | true |
Response elements
Element | Type | Description | Example |
object | The response schema. | ||
RequestId | string | The request ID. | C123F94F-4E38-19AE-942A-A8D6F44F**** |
ReplicaGroupId | string | The ID of the replication pair-consistent group. | pg-xxxxxxx |
Examples
Success response
JSON format
{
"RequestId": "C123F94F-4E38-19AE-942A-A8D6F44F****",
"ReplicaGroupId": "pg-xxxxxxx"
}Error codes
HTTP status code | Error code | Error message | Description |
500 | InternalError | The request processing has failed due to some unknown error, exception or failure. | An internal error has occurred. |
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. |
504 | RequestTimeout | The request is timeout, please try again later. | The request has timed out. Try again later. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.