Use ReprotectDiskReplicaGroup to enable reverse replication for a replication pair-consistent group - Elastic Compute Service - Alibaba Cloud - Elastic Compute Service

Enables the reverse replication feature for replication pairs that belong to a replication pair-consistent group. After reverse replication is enabled, data stored on the original secondary disks is replicated to the original primary disks. When a reverse replication is being performed, the primary and secondary sites of the replication pair-consistent group remain unchanged, but data is replicated from the secondary site to the primary site.

Operation description

Usage notes

For information about the regions in which the replication pair-consistent group feature is available, see Overview.
The replication pair-consistent group for which you want to enable reverse replication must be in the Failovered (failovered) state. You can call the FailoverDiskReplicaPair operation to enable failover.
Before a reverse replication is performed, the primary disks must be detached from its associated Elastic Compute Service (ECS) instance and must be in the Unattached state. You can call the DetachDisk operation to detach the disks.
After you enable reverse replication, you must call the StartDiskReplicaPair operation again to enable the async replication feature before data can be replicated from the original secondary disks to the original primary disks.
You can set the ReverseReplicate parameter to false to cancel the Failovered (failovered) state and restore the original replication direction.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

ebs:ReprotectDiskReplicaGroup

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. You can call the DescribeDiskReplicaGroups operation to query the IDs of replication pair-consistent groups.	cn-shanghai
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 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****
ReverseReplicate	boolean	No	Specifies whether to enable the reverse replication sub-feature. Valid values: true and false. Default value: true.	true

Response elements

Element	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID.	C123F94F-4E38-19AE-942A-A8D6F44F****

Examples

Success response

JSON format

{
  "RequestId": "C123F94F-4E38-19AE-942A-A8D6F44F****"
}

Error codes

HTTP status code	Error code	Error message
500	InternalError	The request processing has failed due to some unknown error, exception or failure.
403	OperationDenied	The operation is not allowed.
403	OperationDenied.InvalidStatus	The operation is not allowed in current status.
403	OperationDenied.NoPairInGroup	The operation is not allowed because no pair in the group.
403	OperationDenied.OperateNotAllowedForPrimary	Operation is not allowed on the primary site.
403	OperationDenied.OperateNotAllowedForStandby	Operation is not allowed on the secondary site.
403	Forbidden	User is not authorized to operate.
403	Forbidden.Action	User is not authorized to operate this action.
404	NoSuchResource	The specified resource does not exist.
504	RequestTimeout	The request is timeout, please try again later.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.