ApsaraDB RDS:Restore MariaDB data

Prerequisites

The source instance must meet the following requirements:

• The instance is in the Running state and is not locked.

• No data migration tasks are in progress on the instance.

• The source instance must have at least one backup set.

Usage notes

• The new instance inherits the IP address whitelist, backup settings, and parameter settings from the source instance.

• The data on the new instance matches the data from the selected backup set.

• The new instance includes all account information from when the backup set was created.

Billing

You are charged for the new instance used in the restoration. You can view the cost details when you create the instance.

Restore data to a new instance

1. Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the instance ID.

2. In the navigation pane on the left, click Backup and Restoration.

3. In the upper-left corner of the page, click Restore Instance (Previously Clone Instance).

4. Configure the following parameters.

   Parameter	Description
   Billing Method	Subscription: This is a prepaid billing method where you pay for an instance upon creation. It is suitable for long-term needs, more affordable than Pay-As-You-Go, and offers greater discounts for longer purchase durations. Pay-As-You-Go: This is a post-paid billing method that charges you on an hourly basis. This method is ideal for short-term needs because you can release instances immediately after use to save costs.
   Restore Mode	Currently, restoration is only supported By Backup Set.
   By Backup Set	Select the backup set from which you want to restore data.
   Edition	High-availability Edition: One primary node and one secondary node, a classic high-availability architecture. Note Supported editions vary by region and database version. For more information about each edition, see Editions.
   Product Type	The default is Standard Edition. For more information, see Product types.
   Zone of Primary Node	Select the availability zone for the primary node of the instance.
   Deployment Method	Multi-zone Deployment (Recommended): The primary and secondary nodes are located in different availability zones within the same region, providing cross-AZ disaster recovery. Single-zone Deployment: The primary node and the secondary node are located in the same availability zone. Note Availability zones within the same region have no substantial differences. An ECS instance has slightly better network performance when accessing an RDS instance in the same availability zone compared to a different one in the same region. If the upper-right corner of the target availability zone displays Sold Out, select another availability zone.
   Zone of Secondary Node	If you select Multi-zone Deployment for the Deployment Method, you must select the availability zone for the instance's secondary node.
   Instance Type	General-purpose Instance Types (Entry-level): A shared, general-purpose instance type that provides dedicated memory and I/O resources, while sharing CPU and storage resources with other general-purpose instances on the same server. Dedicated Instance Types(Enterprise): Refers to dedicated or exclusive instance types. A dedicated instance type provides exclusive access to the allocated CPU, memory, storage, and I/O resources. An exclusive instance type is a top-tier dedicated instance type that exclusively occupies all CPU, memory, storage, and I/O resources of an entire physical server.
   Capacity	This is the total space for your data, system files, log files, and transaction files. You can adjust the storage capacity in increments of 5 GB. Note For specific instance types that use high-performance local SSDs, the storage capacity is bound to the instance type due to dedicated resource allocation. For more information, see Primary instance types.

5. Click Next: Instance Configuration.

6. Configure the following parameters.

   Parameter	Description
   Network Type	ApsaraDB RDS for MariaDB supports Virtual Private Cloud (VPC). A VPC is an isolated network that offers more security and better performance than the classic network. Note To ensure internal network connectivity, ensure the RDS and ECS instances are in the same network type. If you select VPC, they must also be in the same VPC.
   Resource Group	Select the resource group to which the instance belongs.

7. Click Next: Confirm Order.

8. Confirm the Parameter Configuration, select the Quantity and Subscription Duration (for Subscription instances only), select the service agreement, and click Pay Now to complete the payment.

Verify data on the new instance

For information about how to log on to an instance, see Connect to an ApsaraDB RDS for MariaDB instance.

Migrate data to the source instance

After confirming the data on the new instance is correct, you can migrate it back to the source instance. For more information, see Migrate data between ApsaraDB RDS instances.