This topic describes how to restore the data of an ApsaraDB RDS for PPAS instance by using a data backup.

You can restore the data of an RDS instance from a backup set or to a point in time. You can perform the following operations to restore the data:
  1. Restore data to a new RDS instance (formerly known as cloning an instance).
  2. Verify the data on the new RDS instance.
  3. Migrate the data to the original RDS instance.

Precautions

  • The new RDS instance must have the same IP address whitelist, backup, and parameter settings as the original RDS instance.
  • The data information of the new RDS instance is the same as the information indicated by the data or log backup file of the original RDS instance.
  • The account information of the new RDS instance contains the data or log backup file of the original RDS instance.

Billing methods

The billing method is the same as purchasing a new RDS instance. For more information, see Pricing.

Prerequisites

The original RDS instance 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 an ongoing migration task.
  • If you want to restore the original RDS instance to a point in time, the log backup function is enabled for the original RDS instance.
  • If you want to restore the original RDS instance from a backup set, the original RDS instance has at least one backup set.

Restore data to a new RDS instance

  1. Log on to the ApsaraDB for RDS console.
  2. Select the region where the original RDS instance resides.
  3. Find the original RDS instance and click its ID.
  4. In the left-side navigation pane, click 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: You must pay the subscription fee when you create an RDS instance. 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 select 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 restore data to a point in time within the log backup retention period. For more information about how to view or change the log backup retention period, see Back up the data of an RDS PPAS instance.
    • By Backup Set
    Note By Time is displayed only when the log backup function is enabled.
    Edition The edition of the new RDS instance. Only the High-availability edition is supported. In this edition, one primary instance and one secondary instance are deployed to implement high-availability.
    Note The RDS editions that are available vary based on the region and database engine version. For more information, see ApsaraDB for RDS edition overview.
    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. Multi-zone deployment provides zone-level disaster recovery for your business.

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

    Instance Type
    • Entry-level: belongs to the general-purpose instance family. A general-purpose instance exclusively occupies the memory and I/O resources allocated to it, but shares CPU and storage resources with other general-purpose instances that are deployed on the same server.
    • Enterprise-level: belongs to the dedicated instance family. A dedicated instance exclusively occupies the 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 of the 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, 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 instance has available to store data files, system files, binary log 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 network with higher security and better performance than the classic network. If you select the VPC network type, you must also specify the VPC and the VSwitch of Primary Node parameters.
    Note The new RDS instance must have the same network type as the Elastic Compute Service (ECS) instance to which you want to connect. If both the RDS and ECS instances have the VPC network type, 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 new 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 only need to specify Duration when you create a subscription instance.

Verify the data on the new RDS instance

For more information, see Connect to an ApsaraDB RDS for PPAS instance.

Migrate data to the original RDS instance

After you verify data on the new RDS instance, you can migrate the data from the new RDS instance to the original RDS instance. For more information, see Migrate data between RDS instances.

Note Data migration copies data from the source RDS instance to the destination RDS instance. The migration process does not affect the source RDS instance.