You can call the DescribeInstanceCrossBackupPolicy operation to query cross-region backup settings of an instance.
Operation Description
Before you call this operation, make sure that the instance runs one of the following database engines:
- MySQL. For more information, see Back up an ApsaraDB RDS for MySQL instance across regions.
- SQL Server. For more information, see Back up an ApsaraDB RDS for SQL Server instance across regions.
- PostgreSQL. For more information, see Enable cross-region backups for an ApsaraDB RDS for PostgreSQL instance.
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 Resources
is 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 |
---|---|---|---|---|
rds:DescribeInstanceCrossBackupPolicy | READ |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
DBInstanceId | string | Yes | The ID of the instance. | rm-uf6wjk5xxxxxxxxxx |
RegionId | string | Yes | The region ID of the instance. You can call the DescribeRegions operation to query the IDs of regions. | cn-hangzhou |
Response parameters
Examples
Sample success responses
JSON
format
{
"DBInstanceStatusDesc": "ACTIVATION",
"LockMode": "Unlock",
"BackupEnabledTime": "2019-06-12T05:44:21Z",
"CrossBackupType": "1",
"LogBackupEnabled": "Enable",
"BackupEnabled": "Enable",
"RetentType": 1,
"DBInstanceId": "rm-bpxxxxx",
"DBInstanceDescription": "",
"Retention": 15,
"Engine": "mysql",
"LogBackupEnabledTime": "2019-06-12T05:44:21Z",
"CrossBackupRegion": "cn-shanghai",
"StorageOwner": "rds",
"RegionId": "cn-hangzhou",
"RequestId": "CB7667B2-72C8-497B-9BD8-3B343CEF51AB",
"EngineVersion": "5.6",
"StorageType": "oss",
"Endpoint": "",
"DBInstanceStatus": "1"
}
XML
format
<DescribeInstanceCrossBackupPolicyResponse>
<DBInstanceStatusDesc>ACTIVATION</DBInstanceStatusDesc>
<LockMode>Unlock</LockMode>
<BackupEnabledTime>2019-06-12T05:44:21Z</BackupEnabledTime>
<CrossBackupType>1</CrossBackupType>
<LogBackupEnabled>Enable</LogBackupEnabled>
<BackupEnabled>Enable</BackupEnabled>
<RetentType>1</RetentType>
<DBInstanceId>rm-bpxxxxx</DBInstanceId>
<DBInstanceDescription></DBInstanceDescription>
<Retention>15</Retention>
<Engine>mysql</Engine>
<LogBackupEnabledTime>2019-06-12T05:44:21Z</LogBackupEnabledTime>
<CrossBackupRegion>cn-shanghai</CrossBackupRegion>
<StorageOwner>rds</StorageOwner>
<RegionId>cn-hangzhou</RegionId>
<RequestId>CB7667B2-72C8-497B-9BD8-3B343CEF51AB</RequestId>
<EngineVersion>5.6</EngineVersion>
<StorageType>oss</StorageType>
<Endpoint></Endpoint>
<DBInstanceStatus>1</DBInstanceStatus>
</DescribeInstanceCrossBackupPolicyResponse>
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | InvalidRegion.Format | Specified Region is not valid. | The region ID is invalid. Check the region ID. |
403 | CrossBackupNotSupport | Specified region not support cross region backup. | Cross-zone backup is not supported in the specified region. |
404 | not found | Page not found. | - |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
2022-09-01 | The error codes of the API operation change. | |||||||||
|