This topic describes how to restore the data of an ApsaraDB RDS for PostgreSQL instance from a cross-region backup file to a new RDS instance. The new RDS instance must reside in the region in which the cross-region backup file is stored.
Your RDS instance is backed up across regions. For more information, see Use the cross-region backup feature.
For more information about data restoration methods, see Methods to restore an ApsaraDB RDS for PostgreSQL instance.
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 across 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 Backups. In the top navigation bar, select the region in which your RDS instance resides.
On the Backup Instances tab of the Cross-region Backup tab, find the RDS instance and click the ID of the instance.
On the page that appears, find the backup set that you want to use, and click Restore in the Actions column.
In the message that appears, click OK.Note
You can restore data only to a new instance. You cannot restore data to an existing instance.
On the Restore Database page, configure the following parameters.
Subscription: A subscription RDS instance is an instance for which you pay an upfront fee. For long-term usage, the subscription billing method is more cost-effective than the pay-as-you-go billing method. You are charged lower prices for longer subscription periods.
Pay-As-You-Go: A pay-as-you-go RDS instance is billed per hour based on your actual resource usage. We recommend that you select the pay-as-you-go billing method for short-term use. If you no longer need your pay-as-you-go RDS instance, you can release it to reduce costs.
By Backup Set: allows you to restore the data of your RDS instance from a backup set.
By Time: allows you to restore the data of your RDS instance to a specific point in time. The point in time must be within the specified log backup retention period.
By Backup Set
The backup set from which you want to restore the data of your RDS instance. This parameter appears only when you set the Restore Method parameter to By Backup Set.
The point in time to which you want to restore the data of your RDS instance. This parameter appears only when you set the Restore Method parameter to By Time.Note
Both local and cross-region log backup files can be used to restore the data of your RDS instance to a specific point in time.
The region to which the new RDS instance belongs.
A zone is an independent physical location within a region. The Zone of Primary Node parameter specifies the zone to which the primary RDS instance belongs. The Zone of Secondary Node parameter specifies the zone to which the secondary RDS instance belongs.You can select the Single-zone Deployment or Multi-zone Development method.
- Single-zone Deployment: If you select this deployment method, the values of the Zone of Primary Node and Zone of Secondary Node parameters are the same.
- Multi-zone Development: We recommend that you select this deployment method to ensure zone-level disaster recovery. If you select this deployment method, the value of the Zone of Primary Node parameter differs from the value of the Zone of Secondary Node parameter. You must manually configure the Zone of Primary Node and Zone of Secondary Node parameters.
- After the RDS instance is created, you can view information about the new RDS instance and its secondary RDS instance on the Service Availability page.
- If you select RDS Basic Edition, the database system consists of only one primary RDS instance and supports only the single-zone deployment method.
The instance type of the new RDS instance. Each instance type supports a specific number of CPU cores, memory capacity, maximum number of connections, and maximum IOPS. For more information, see Primary ApsaraDB RDS instance types.
The maximum storage capacity that is provisioned to store data files, system files, binary log files, and transaction files in the instance.
You must configure this parameter only when the Billing Method parameter is set to Subscription.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.
Click Next: Instance Configuration to configure the network type and resource group of the RDS instance.
The network type of the RDS instance. Select VPC. A virtual private cloud (VPC) is an isolated network that provides higher security and better performance than the classic network. If you select the VPC network type, you must configure the VPC and VSwitch of Primary Node parameters. If you set the Deployment Method parameter to Multi-zone Deployment in the previous step, you must also configure the VSwitch of Secondary Node parameter.
The resource group to which the new RDS instance belongs.
- Click Next: Confirm Order.
- Confirm the settings in the Parameters section, configure the Purchase Plan and Duration parameters, read and select Terms of Service, click Pay Now, and then complete the payment. You must configure the Duration parameter only when the RDS instance uses the subscription billing method. Note If you select the subscription billing method for the new RDS instance, we recommend that you select Auto-Renew Enabled. This way, you do not need to manually renew the new RDS instance on a regular basis. This also helps prevent interruptions on your workloads on the new RDS instance if a payment becomes overdue.
Optional. Log on to the new RDS instance and verify the data. For more information, see Connect to an ApsaraDB RDS for PostgreSQL instance.
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 and Create an account. 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. After you complete these operations, you can connect to the RDS instance. For more information, see Connect to an ApsaraDB RDS for PostgreSQL instance.