Enables the async replication feature for replication pairs that belong to a replication pair-consistent group. The first time the async replication feature is enabled for the replication pairs, the system performs a full synchronization to synchronize all data from disks at the primary site (primary disks) to disks at the secondary site (secondary disks). Then, the system periodically synchronizes incremental data based on the recovery point objective (RPO) of the replication pair-consistent group.
Operation description
Usage notes
- For information about the regions in which the replication pair-consistent group feature is available, see Overview .
- If you set the
OneShottofalse, the replication pair-consistent group must be in the Created (created), Synchronizing (syncing), Normal (normal), or Stopped (stopped) state. - If you set
OneShottotrue, the replication pair-consistent group must be in the Created (created), One-time Syncing (manual_syncing), or Stopped (stopped) state. The time interval between two consecutive one-time synchronizations must be longer than one half of the recovery point objective (RPO). - After a replication pair-consistent group is activated, the group enters the Initial Syncing (
initial_syncing) state and the system performs the first async replication to replicate all data from the primary disks to secondary disks.
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:StartDiskReplicaGroup | update | *DiskReplicaGroup acs:ebs:{#regionId}:{#accountId}:diskreplicagroup/{#ReplicaGroupId} |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| RegionId | string | Yes | The ID of the replication pair-consistent group. | cn-beijing |
| ReplicaGroupId | string | Yes | The ID of the replication pair-consistent group. You can call the DescribeDiskReplicaGroups operation to query the IDs of replication pair-consistent groups. | pg-myreplica**** |
| ClientToken | string | No | The client token that is used to ensure the idempotence of the request. You can use the client to generate the value, but you must make sure that the value is unique among different requests. The ClientToken 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**** |
| OneShot | boolean | No | Specifies whether to immediately synchronize data once. Valid values:
Default value: false. | false |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "C123F94F-4E38-19AE-942A-A8D6F44F****"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | OperationDenied.StandbyDeviceAttached | The secondary disk is attached. | The secondary disk is attached to the instance at the secondary site. Stop the instance or detach the disk from the instance. |
| 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.ManualSyncLimit | One shot start manual syncing too frequently, please try again later. | The requirements of the cooldown period after manual synchronization operations are not met. |
| 403 | OperationDenied.NoPairInGroup | The operation is not allowed because no pair in the group. | The operation is not supported while the specified replication pair-consistent group has no replication pairs. |
| 403 | OperationDenied.PairGroupStatusConflict | The operation is not allowed due to pair and group status are not consistent. | The operation is not supported while the state of the replication pair is not the same as that of the replication pair-consistent group. |
| 403 | OperationDenied.PairGroupAZoneConflict | The operation is not allowed due to pair and group having different RegionId or ZoneId. | The operation is not supported while the replication pair-consistent group and the replication pair do not belong to the same region and zone. |
| 403 | OperationDenied.PairNotInGroup | The operation is not allowed because pair is not in any group. | The operation is not supported while the specified replication pair belongs to no 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-30 | The Error code has changed | View Change Details |