If you have created data backups for your RDS for MariaDB instance, you can restore its data by using a backup set.

This topic describes how to restore data of an RDS for MariaDB instance. 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 data information of the new instance must be the same as that of the backup set.
  • The new instance contains the account information of the backup set.

Billing method

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


The original instance must meet the following conditions:

  • The instance is in the Running state and is not locked.
  • No migration task is being performed for the instance.
  • At least one backup set is available for the instance.

Restore data to a new instance

  1. Log on to the ApsaraDB for RDS console.
  2. Select the region where the RDS instance resides.
  3. Click the ID of the instance.
  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 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 durations.
    • Pay-As-You-Go: A pay-as-you-go instance is billed 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 the instance to reduce costs when you no longer need it.
    Restore Mode Currently, only By Backup Set is supported.
    Edition The edition of the 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.

    The zone where the RDS instance resides. Each zone is an independent physical location within a region. There are no technical differences among zones in the same region. Deploying your RDS instances in multiple zones provides zone-level disaster recovery for your business.

    You only need to select a primary zone. The system automatically allocates a secondary zone.

    Instance Type
    • Entry-level: 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: the dedicated instance family. A dedicated instance occupies exclusive CPU, memory, storage, and I/O resources. 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, system files, binary log files, and transaction files. You can increase the storage capacity in increments of at least 5 GB.
    Note RDS instances with local SSDs in the dedicated instance family occupy exclusive resources. The storage capacities are determined by instance types. For more information, see Primary instance types.
  7. Click Next: Instance Configuration.
  8. Configure the following parameters.
    Parameter Description
    Network Type RDS for MariaDB instances are deployed in Virtual Private Clouds (VPCs). A VPC is an isolated virtual network that provides higher security and better performance than a classic network.
    Note Make sure that the network types of the RDS instance and the ECS instance to which it connects are the same. If their network types are VPC, make sure that both instances reside in the same VPC. Otherwise, the ECS instance and RDS instance 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 only need to specify Duration when you create a subscription instance.

Log on to the new RDS instance and verify data

For more information, see Connect to an RDS instance.

Migrate data to the original instance

After you verify data on the new instance, you can migrate the data from the new instance to the original 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.