This topic describes how to restore the data of an ApsaraDB RDS for MariaDB TX instance. If data backups are created for your RDS instance, you can restore the data of your RDS 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.
  3. Migrate the data 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 restoration fee is the same as the fee that is required to purchase an RDS instance. 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 migration tasks are being performed for the original RDS instance.
  • At least one data backup file is available for the original RDS instance.

Restore the data to a new RDS instance

  1. Log on to the ApsaraDB 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 that appears, click Restore Database (Previously Clone Database).
  6. Configure the following parameters.
    Parameter Description
    Billing Method
    • Subscription: A subscription instance is an instance that you can subscribe to for a specified period of time and pay for up front. 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. We recommend that you select the pay-as-you-go billing method for short-term use. If you no longer need a pay-as-you-go instance, you can release it 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 one primary RDS instance and one secondary RDS instance. These instances work in the 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 provide the same services. The multi-zone deployment method provides zone-level disaster recovery.

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

    Instance Type
    • General-purpose (Entry-level): belongs to the general-purpose instance family. A general-purpose instance exclusively occupies the allocated memory and I/O resources. However, it shares CPU and storage resources with the other general-purpose instances that are deployed on the same server.
    • Dedicated (Enterprise-level): belongs to the dedicated instance family or the dedicated host instance family. A dedicated instance exclusively occupies the allocated CPU, memory, storage, and I/O resources. The dedicated host instance family is the highest configuration of the dedicated instance family. A dedicated host instance occupies all the CPU, memory, storage, and I/O resources on the server where it is deployed.
    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 the new RDS 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 the exclusive allocation 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 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 an RDS instance has the same network type as the Elastic Compute Service (ECS) instance that you want to connect to the RDS instance. If the network types of these instances are VPC, you must also make sure that these instances reside in the same VPC. Otherwise, these instances 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 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 the data on the new RDS instance

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

Migrate the 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 During the migration process, your workloads on the original RDS instance run as normal.