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

The entire restoration process consists of the following steps:
  1. Restore the data from a data backup file to a new RDS instance. This process was known as instance cloning.
  2. Log on to the new RDS instance and verify the data on the new RDS instance.
  3. Migrate the data from the new RDS instance to the original RDS instance.

Precautions

  • The new RDS instance has the same IP address whitelists, backup settings, and parameter settings as the original RDS instance.
  • The information about the data of the new RDS instance is the same as the information about the data in the data backup file that you select.
  • The new RDS instance contains the account information in the data backup file that you select.

Billing

The fee for the data restoration is the same as the price of a new RDS instance. The price of a new RDS instance varies based on the instance configuration, such as the region, instance type, and storage capacity. For more information, visit the ApsaraDB RDS buy page.

Prerequisites

The original RDS instance must meet the following requirements:

  • The original RDS instance is in the Running state and is not locked.
  • No data is being migrated from or to the original RDS instance.
  • At least one data backup file is available for the original RDS instance.

Restore data to a new RDS instance

  1. Access RDS Instances, select a region at the top, and then click the ID of the target RDS instance.
  2. In the left-side navigation pane, click Backup and Restoration.
  3. In the upper-left corner of the page that appears, click Restore Database.
  4. Configure the following parameters.
    Parameter Description
    Billing Method
    • Subscription: A subscription instance is an instance for which you pay an upfront fee. For long-term use, the subscription billing method is more cost-effective than the pay-as-you-go billing method. You can 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. For short-term use, we recommend that you select the pay-as-you-go billing method. If you no longer need a pay-as-you-go instance, you can release the instance to reduce costs.
    Restore Mode The method that is used to restore data. Select By Backup Set.
    Edition The RDS edition of the new RDS instance. Select High-availability. In this edition, your database system consists of a primary RDS instance and a secondary RDS instance. These instances work in a high-availability architecture.
    Note The available RDS editions vary based on the region and database engine version that you select. For more information, see Overview of ApsaraDB RDS editions.
    Zone of Primary Node

    The zone of the new RDS instance. Each zone is an independent physical location within a region. Zones in the same region do not have substantial differences. The multi-zone deployment method provides zone-disaster recovery.

    If you select the single-zone deployment method, you must specify only the Zone of Primary Node parameter. If you select the multi-zone deployment method, you must specify the Zone of Primary Node parameter and ApsaraDB RDS automatically specifies the Zone of Secondary Node parameter.

    Instance Type
    • General-purpose (Entry-level): provides general-purpose instance types. A general-purpose RDS instance exclusively occupies the allocated memory and I/O resources, but shares CPU and storage resources with the other general-purpose RDS instances that are deployed on the same server.
    • Dedicated (Enterprise-level): provides dedicated instance types and dedicated host instance types. A dedicated RDS instance exclusively occupies the allocated CPU, memory, storage, and I/O resources. Dedicated host instance types provide higher specifications than dedicated instance types. A dedicated host RDS instance occupies all CPU, memory, storage, and I/O resources on the server in which the RDS instance is deployed.
    Note Each instance type supports a specific number of cores, memory capacity, maximum number of connections, and maximum IOPS. For more information, see Primary ApsaraDB RDS instance types.
    Storage Capacity The maximum amount of storage that is provisioned to store data files, system files, binary log files, and transaction files on the new RDS instance. You can adjust the storage capacity at a step size of 5 GB.
    Note A dedicated RDS instance that is equipped with local SSDs is allocated exclusive resources, and its storage capacity varies based on the instance type. For more information, see Primary ApsaraDB RDS instance types.
  5. Click Next: Instance Configuration.
  6. Configure the following parameters.
    Parameter Description
    Network Type The network type of the new RDS instance. ApsaraDB RDS for MariaDB TX supports virtual private clouds (VPCs). A VPC is an isolated virtual network that provides higher security and higher performance than the classic network.
    Note You must make sure that the new RDS instance has the same network type as the Elastic Compute Service (ECS) instance that you want to connect. If these instances both reside in VPCs, you must make sure that these instances reside in the same VPC. If these instances reside in different VPCs, these instances cannot communicate over an internal network.
    Resource Group The resource group to which the new RDS instance belongs.
  7. Click Next: Confirm Order.
  8. Confirm the settings in the Parameters section, specify the Purchase Plan and Duration parameters, read and select Terms of Service, click Pay Now, and then complete the payment. You must specify the Duration parameter only when the new RDS instance uses the subscription billing method.

Verify data on the new RDS instance

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

Migrate data to the original RDS instance

After you verify the 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 The migration of data between two RDS instances does not interrupt the workloads that are run on the source RDS instance.