This topic describes how to restore the data of an ApsaraDB RDS for PostgreSQL instance from a cross-region backup file to the same RDS instance or to a new RDS instance. The new RDS instance must reside in the region where the cross-region backup file is stored.
- For more information about how to restore the data of an ApsaraDB RDS for MySQL instance across regions, see Restore the data of an ApsaraDB RDS for MySQL instance across regions.
- For more information about how to restore the data of an ApsaraDB RDS for SQL Server instance cross regions, see Restore the data of an ApsaraDB RDS for SQL Server instance across regions.
- Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Cross-region Backup. In the top navigation bar, select the region where your RDS instance resides.
- Find your RDS instance and click its ID.
- On the Data Backup tab, find the data backup file that you want to use, and click Restore in the Actions column.
- On the Restore Database page, click the Subscription or Pay-As-You-Go tab and configure the following parameters.
Parameter Description Restore Mode
- By Backup Set: allows you to restore data from a backup set.
- By Time: allows you to restore data to a point in time. The point in time must be within the specified log backup retention period.
Backup Set The backup set from which you want to restore data. This parameter appears only when you set Restore Mode to By Backup Set. Restore Point The point in time to which you want to restore data. This parameter appears only when you set Restore Mode to By Time.Note Both local and cross-region log backups can be used to restore data to a point in time. Region The region to which the new RDS instance belongs. Zone The zone where the new RDS instance resides. Each zone is an independent physical location within a region. Zones in the same region provide the same services. You can create the new RDS instance and the ECS instance to which you want to connect in the same zone or in different zones. CPU and Memory The specifications of the new RDS instance. Each instance type supports a specific number of CPU cores, memory capacity, maximum number of connections, and maximum input/output operations per second (IOPS). For more information, see Primary instance types. Capacity The storage capacity that the new RDS instance has available to store data files, system files, binary log files, and transaction files. Network Type
Note The settings of some parameters cannot be modified. These parameters include Database Engine, Version, and Edition. The same settings of these parameters must be specified for both your RDS instance and the new RDS instance.
- Classic Network: the traditional type of network.
- VPC: the recommended type of network. A virtual private cloud (VPC) is an isolated virtual network that provides higher security and better performance than the classic network. If you select the VPC network type, you must also select a VSwitch that is associated with the specified VPC.
- Specify the Duration and Quantity parameters. Then, click Buy Now. You must specify the Duration parameter when the new RDS instance is billed on a subscription basis.
After you create an RDS instance, you must configure IP address whitelists or security groups and create accounts. For more information, see Configure an IP address whitelist for an ApsaraDB RDS for PostgreSQL instance and Create an account on an ApsaraDB RDS for PostgreSQL instance. If you want to connect to the RDS instance over the Internet, you must also apply for a public endpoint. For more information, see Apply for or release a public endpoint on an ApsaraDB RDS for PostgreSQL instance. After you complete these operations, you can connect to the RDS instance. For more information, see Connect to an ApsaraDB RDS for PostgreSQL instance.