Restores the data of an instance to an existing instance across regions.
Operation Description
Before you call this operation, you can call the CheckCreateDdrDBInstance operation to check whether the data of the source instance can be restored from a cross-region backup set.
Before you call this operation, make sure that the following requirements are met:
A cross-region backup set is created for the source instance after the single-database backup feature is enabled for the instance.
If you want to restore data from a specific point in time, the log backup feature is enabled for the source instance.
The names that you want to use for the restored tables do not exist in the destination instance.
The source 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:RestoreDdrTable | WRITE |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
DBInstanceId | string | Yes | The ID of the source instance. | rm-bpxxxxx |
RegionId | string | No | The region ID of the destination instance. You can call the DescribeRegions operation to query the most recent region list. | cn-hangzhou |
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. | ETnLKlblzczshOTUbOCzxxxxxxxxxx |
RestoreType | string | Yes | The method that is used to restore data. Valid values:
Default value: 0. | 0 |
BackupId | string | No | The ID of the cross-region backup set that you want to use. You can call the DescribeCrossRegionBackups operation to query the ID of the cross-region backup set. NoteIf you set the RestoreType parameter to 0, you must also specify the BackupId parameter. | 279563 |
RestoreTime | string | No | The point in time to which you want to restore data. The specified point in time must be earlier than the current time. Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time must be in UTC. NoteIf you set the RestoreType parameter to 1, you must also specify the RestoreTime parameter. | 2020-04-25T16:00:00Z |
SourceRegion | string | No | The region ID of the source instance whose data you want to restore to a point in time. NoteIf you set the RestoreType parameter to 1, you must also specify the SourceRegion parameter. | cn-beijing |
SourceDBInstanceName | string | No | The ID of the source instance whose data you want to restore to a point in time. NoteIf you set the RestoreType parameter to 1, you must also specify the SourceRegion parameter. | rm-bpxxxxx |
TableMeta | string | Yes | The databases and tables that you want to restore. Format: | [{"type":"db","name":"testdb1","newname":"testdb1","tables":[{"type":"table","name":"test1","newname":"test1_backup"},{"type":"table","name":"test2","newname":"test2_backup"}]}] |
ResourceGroupId | string | No | The ID of the resource group. | rg-acfmy***** |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "75BBF1EF-1E90-4950-BFFB-252D26E8259B",
"DBInstanceId": "rm-uf6wjk5*****"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | InvalidRestoreType.Format | Specified restore type is not valid. | The restoration type is invalid. Specify a valid restoration type. |
400 | InvalidRestoreTime.Format | Specified restore time is not valid. | The operation failed. The point in time is invalid. Specify a valid point in time. |
400 | InvalidBakset.Invalid | Specified bakset is not valid. | - |
400 | InvalidParamTableMetaForRestore.Content | new dbname or table in TableMeta cannot be same with old when restore to source instance | - |
400 | InvalidParamTableMeta | Invalid parameter TableMeta is null or not json format | The value of the TableMeta parameter is invalid. Check the value of this parameter. |
400 | InvalidBakHistoryDO | BakHistory is inbalid when check restore TableMeta | - |
400 | InvalidParamTableMeta.Content | TableMeta missing old dbname or new dbname, please check | The value of the table_meta parameter does not contain the names of the source and destination tables. |
400 | InvalidParamTableMeta.Duplicate | TableMeta has duplicate db or table with other newname, commons or system | The operation failed. The databases and tables that you want to restore already exist in the RDS instance. |
400 | InvalidSourceRestoreDBName.NotFound | specific source restore dbname is not found in db list | The operation failed. The data backup file does not contain the data of the databases. |
400 | InvalidDBName.Duplicate | Specified DB name already exists in the This instance. | A database with the same name has been created on the RDS instance. Specify a different name. |
400 | InvalidParameters.Format | Specified parameters is not valid. | The values of some parameters are invalid. |
400 | InvalidAvZone.Format | Specified AvZone is not valid. | The value of the AvZone parameter is invalid. Check the value of this parameter. |
400 | InvalidRegion.Format | Specified Region is not valid. | The region ID is invalid. Check the region ID. |
400 | InvalidVpcParameter | Specified VPCId VSwitchId or IPAddress or TunnelId is not valid. | The values of the VPCId parameter and the VSwitchId parameter are invalid. Check the values of these parameters. |
400 | MissingUserID | The request is missing a user_id parameter. | The user ID cannot be found. |
400 | MissingUID | The request is missing a uid parameter. | The operation failed. The UID in the request is left unspecified. |
403 | IncorrectDBInstanceType | Current DB instance type does not support this operation. | The operation failed. The RDS instance is not in a ready state. |
403 | IncorrectDBInstanceState | Current DB instance state does not support this operation. | - |
403 | ChildDBInstanceExists | Current DB instance had child instance. | The read-only instance already exists. |
403 | InvalidBackupLogStatus | Current backup log enable status does not support this operation. | The operation failed. Log backups are not enabled, and therefore data cannot be restored to a specified point in time. |
403 | IncorrectBackupSetMethod | Current backup set method does not support operations. | The operation failed. The data backup file does not support the restoration of individual databases and tables. |
403 | IncorrectBackupSetState | Current backup set state does not support operations. | The operation failed. The data backup file is not in a ready state. |
404 | RestoreType.NotFound | RestoreType is not found. | RestoreType is not found. |
404 | InvalidBackupSetID.NotFound | Specified backup set ID does not exist. | The backup set does not exist. Specify an available backup set. |
404 | InsufficientResourceCapacity | There is insufficient capacity available for the requested instance. | - |
404 | InvalidBackup.NotFound | The available backup does not exist in recovery time. | No available data backup file can be used to restore data. |
404 | InvalidBinlog.NotFound | The available binlog does not exist in recovery time. | The binary log file at the specified point in time is invalid. |
404 | InvalidDB.NotFound | Specified db does not exist or DB status does not support. | - |
404 | InvalidDBInstance.NotFound | Specified instance does not exist or not support. | The RDS instance cannot be found, is deleted, or does not support the operation. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
2022-08-11 | API Description Update,The error codes of the API operation change. | |||||||||||
|