The topic describes how use backups to restore data of an ApsaraDB RDS for PostgreSQL instance.

You can restore ApsaraDB RDS for PostgreSQL data by backup set or by time. The procedure is as follows:
  1. Restore data to a new instance (formerly known as cloning an instance).
  2. Log on to the new instance to verify the data.
  3. Migrate the data to the original instance.


  • The new instance must have the same whitelist, backup, and parameter settings as the original instance.
  • The new instance must have the same data and account information as the backup set or instance at the time point.


It is the same as purchasing a new instance. For more information, see Pricing.


The original instance must meet the following conditions:

  • It is running and is not locked.
  • It is not undergoing any migration tasks.
  • To restore data by time, you must make sure that the log backup function is enabled.
  • To restore data by backup set, you must make sure that the original instance has at least one backup set.

Restore data to a new instance

  1. Log on to the ApsaraDB for RDS console.
  2. In the upper-left corner of the page, select the region where the target instance is located.
  3. Find the target instance and click the ID of the instance.
  4. In the left-side navigation pane, select Backup and Restoration.
  5. In the upper-right corner of the page, click Restore Database (Previously Clone Database).
  6. Configure the following parameters.
    Parameter Description
    Billing Method
    • Subscription: A subscription instance is an instance that you subscribe to for a period of time and pay for up front. We recommend that you select subscription billing for long-term use because it is more cost-effective than pay-as-you-go billing. You receive larger discounts for longer subscription periods.
    • Pay-As-You-Go: A pay-as-you-go instance is charged per hour based on your actual resource usage. We recommend that you choose pay-as-you-go billing for short-term use. You can release your pay-as-you-go instance to reduce costs when you no longer need it.
    Restore Mode
    • By Time: You can select any time point within the retention period of log backups. For more information about how to view or change the retention period of log backups, see Back up an ApsaraDB RDS for PostgreSQL instance.
    • By Backup Set
    Note By Time is displayed only when the log backup feature is enabled.
    • Basic: The database system consists of only one instance. Computing is separated from storage to increase cost-efficiency.
    • High-availability: The database system adopts the classic high-availability architecture that consists of one primary instance and one secondary instance.
    Note The RDS editions that are available vary based on the region and database engine version you select. For more information, see ApsaraDB for RDS edition overview.

    The zone where the RDS instance resides. Each zone is an independent physical location within a region. The zones that are located in the same region are similar. Multi-zone deployment provides zone-disaster recovery for your business.

    You only need to specify the primary zone. The system automatically assigns a secondary zone to the RDS instance.

    Instance Type
    • Entry-level: belongs to the general-purpose instance family. A general-purpose instance occupies exclusive memory and I/O resources. However, it shares CPU and storage resources with other general-purpose instances on the same server.
    • Enterprise-level: belongs to the dedicated instance family. A dedicated instance occupies exclusive CPU, memory, storage, and I/O resources allocated to it. The top configuration of the dedicated instance family is the dedicated host. A dedicated host instance occupies all CPU, memory, storage, and I/O resources on the server where it resides.
    Note 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 is used to store data files, system files, binlog files, and transaction files. The storage capacity increases in increments of 5 GB.
    Note The dedicated instance family supports exclusive allocations of resources. Therefore, the storage capacity of each instance type with local SSDs in this family is fixed. For more information, see Primary instance types.
  7. Click Next: Instance Configuration.
  8. Configure the following parameters.
    Parameter Description
    Network Type
    • Classic Network: a traditional type of network.
    • VPC: A virtual private cloud (VPC) is an isolated virtual network with higher security and better performance than a classic network. If you select the VPC network type, you must also specify VPC and VSwitch of Primary Node.
    Note Make sure that the primary RDS instance has the same network type as the ECS instance to which you want to connect. If both their network types are VPC, you must also make sure that they reside in the same VPC. Otherwise, they cannot communicate over an internal network.
    Resource Group The resource group to which the RDS instance belongs.
  9. Click Next: Confirm Order.
  10. Confirm the settings in the Parameters section, specify Purchase Plan and Duration, read and select Terms of Service, and click Pay Now. You need to specify Duration only when you create a subscription instance.

Log on to the new instance and verify the data

For more information about logging on to an instance, see Connect to an ApsaraDB RDS for PostgreSQL instance.

Migrate data to the original instance

After you verify the data in the new instance, you can migrate the data that you require from the new instance to the original instance. For more information, see Migrate data between ApsaraDB for RDS instances.

Note During migration, data is copied from a source instance to a destination instance. Migration does not affect the source instance.