The topic describes how to restore the data of an ApsaraDB RDS for PostgreSQL instance to a new RDS instance.
Prerequisites
The original RDS instance whose data you want to restore must meet the following requirements:
- The original RDS instance is in the Running state and is not locked.
- The original RDS instance does not have ongoing migration tasks.
- If you want to restore data to a point in time, the log backup feature is enabled
for the original RDS instance.
Note RDS instances that run the Basic Edition do not support the log backup feature. Therefore, you cannot restore data of such an RDS instance to a point in time.
- If you want to restore data from a backup set, the original RDS instance has at least one backup set.
Background information
ApsaraDB RDS for PostgreSQL allows you to restore data from a backup set or to a point in time. The following procedure is used to restore data:
- Restore data to a new RDS instance. This process was formerly known as instance cloning.
- Log on to the new RDS instance and verify the data.
- Migrate the data to the original RDS instance.
Precautions
- The new RDS instance and the original RDS instance must have the same IP address whitelist, backup, and parameter settings.
- The data and account information of the new RDS instance must be the same as the data and account information that is indicated by the specified data or log backup file of the original RDS instance.
Billing
The fee required to renew the subscription of an RDS instance is the same as the fee required to purchase an RDS instance.
The price of the RDS instance that you want to purchase varies based on the instance configuration, such as the region, instance type, storage capacity that you select. For more information, go to the ApsaraDB RDS buy page.
Restore data to a new RDS instance
Log on to the new RDS instance and verify the data
For more information, see Connect to an ApsaraDB RDS for PostgreSQL instance.