Restore data across regions

Restore to a new instance across regions

1. Log on to the ApsaraDB RDS console, click Backups in the left-side navigation pane, and select a region from the top navigation bar.

2. On the Cross-region Backup tab, click the Backup Instances tab. Then, click the ID of the target instance to open the Cross-region Backup and Restoration page.

3. In the Actions column of the target backup set, click Restore.

4. In the dialog box that appears, click OK.

   Note

   You can restore data only to a new instance. Restoring data to an existing instance is not supported.

5. On the Restore Database page, configure the following parameters.

   Parameter	Description
   Billing Method	Subscription : A prepaid billing method where you pay for resources in advance. This option is cost-effective for long-term use and offers greater discounts for longer subscription periods. Pay-As-You-Go: A postpaid billing method where you are billed hourly for the resources you use. This option is ideal for short-term needs because you can release the instance at any time to save costs.
   Restore Mode	By Backup Set: Restores the data from a specific backup set to the new instance. By Time: Restores data to a specific point in time within the log retention period.
   By Backup Set	If you set Restore Mode to By Backup Set, select the backup set that you want to restore.
   Restoration Time	If you set Restore Mode to By Time, select the point in time to which you want to restore the data. Note Both local and cross-region log backups can be used for a point-in-time recovery (PITR).
   Region	The destination region for the new instance.
   Zone	You can deploy the instance in a Single-zone Deployment or across Multi-zone Deployment: Single-zone Deployment: The primary and secondary nodes are in the same zone. Multi-zone Deployment (Recommended): The primary and secondary nodes are deployed in different zones for disaster recovery. Note After the instance is created, you can view the information about the primary and secondary nodes on the Service Availability page. Instances of Basic Edition support only single-zone deployment.
   Instance Type	Each instance type offers different vCPU cores, memory, maximum connections, and maximum IOPS. For more information, see Primary instance types.
   Capacity	The storage capacity, which includes space for data, system files, binlog files, and transaction files.
   Duration	This parameter is required only if you select Subscription for the billing method.

   Note

   Parameters such as the database engine, version, and edition are inherited from the source instance and cannot be changed.

6. Click Next: Instance Configuration and configure the network and resource group parameters.

   Parameter	Description
   Network Type	VPC: A virtual private cloud (VPC) is an isolated network environment that offers better security and performance than the classic network. If you select this network type, you must specify the VPC and VSwitch of Primary Node. If you selected Multi-zone Deployment in the previous step, you must also specify the VSwitch of Secondary Node.
   Resource Group	The resource group for the new instance.

7. Click Next: Confirm order.

8. Confirm the Parameter Configuration, select the Quantity and Duration (for subscription instances only), click Pay Now, and complete the payment.

   Note

   For subscription instances, we recommend that you select Auto-renewal. This saves you from the need to perform manual renewals and prevents service interruptions caused by overdue payments.

9. (Optional) After the instance is created, log on to it to verify the data. For more information, see Connect to an ApsaraDB RDS for PostgreSQL instance.

Related topics

After you create an instance, you must configure an IP address whitelist and create an account. If you want to connect to the instance over the public network, you must also apply for a public endpoint. You can then connect to the instance.

If the connection to the instance fails, see Troubleshoot connection issues.