If you accidentally deleted a table, need to retrieve data from a specific point in the past, or want to undo unintended changes, restore a backup set to a new ApsaraDB RDS for MariaDB instance—without touching your production instance.
How it works
Restoring data involves three stages:
Restore a backup set to a new RDS instance.
Log on to the new instance and verify the restored data.
Migrate the verified data back to the original RDS instance.
ApsaraDB RDS for MariaDB supports By Backup Set as the only restore mode.
Prerequisites
Before you begin, ensure that you have:
An original RDS instance in the Running state that is not locked
No ongoing migration tasks on the original instance
At least one complete backup set
Limitations
The new instance inherits the IP address whitelists, backup settings, and parameter settings of the original instance.
The data and account information on the new instance match those in the selected backup set, not the current state of the original instance.
Billing
The new RDS instance is billed independently. Charges begin immediately after the instance is created. The price is displayed on the order confirmation page before you pay.
Tip: To avoid unnecessary costs, create a pay-as-you-go instance for temporary use. After migrating the data back to the original instance, release the new instance. For migration instructions, see Migrate data between ApsaraDB RDS instances. For release instructions, see Release or unsubscribe from an ApsaraDB RDS for MariaDB instance.
Restore a backup set to a new RDS instance
Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region where your instance resides. Find the instance and click its ID.
In the left-side navigation pane, click Backup and Restoration.
In the upper-left corner, click Restore Database.
Configure the basic instance settings.
Parameter Description Billing method Subscription: Pay upfront for a fixed term. More cost-effective for long-term use. Pay-As-You-Go: Billed per hour based on actual usage. Suitable for temporary use. Restore mode Only By Backup Set is supported. By Backup Set Select the backup set to restore from. Edition High-availability Edition: One primary instance and one secondary instance. Available editions vary by region and database engine version. For details, see Overview of ApsaraDB RDS editions. Product type Defaults to Standard. For details, see Product types. Zone of primary node The zone where the primary instance resides. Deployment method Multi-zone Deployment (recommended): The primary and secondary instances are in different zones, providing zone-level disaster recovery. Single-zone Deployment: Both instances are in the same zone. If a zone name shows Sold Out in the upper-right corner, that zone has no available resources—select a different zone. Zone of secondary node Required for Multi-zone Deployment. Select the zone for the secondary instance. Instance type General-purpose Instance Types: Entry-level. Shares CPU and storage with other instances on the same host while exclusively using allocated memory and I/O. Dedicated Instance Types: Enterprise-level. Exclusively uses all allocated CPU, memory, storage, and I/O resources. A dedicated host instance type uses all resources on the host. Capacity Storage for data, system, log, and transaction files. Adjustable in increments of 5 GB. For dedicated instances using Premium Local SSDs, storage capacity is fixed by instance type. See Primary ApsaraDB RDS instance types. Click Next: Instance Configuration.
Configure the network settings.
Parameter Description Network type ApsaraDB RDS for MariaDB supports virtual private clouds (VPCs). A VPC is an isolated network that provides higher security and better performance than the classic network. For internal network communication, the new RDS instance and your Elastic Compute Service (ECS) instance must be in the same VPC. Resource group The resource group for the new instance. Click Next: Confirm Order.
Review the settings in the Parameters section. If the instance uses the Subscription billing method, set the Purchase Plan and Duration. Read and accept the Terms of Service, click Pay Now, and complete the payment.
Verify data on the new RDS instance
Log on to the new RDS instance and verify that the restored data is correct. For connection instructions, see Connect to an ApsaraDB RDS for MariaDB instance.
Check that the tables, records, and schema match the state you expect from the selected backup set.
What's next
After verifying the data, migrate it from the new instance back to the original instance using Data Transmission Service (DTS). Data migration runs without interrupting workloads on the source instance. For details, see Migrate data between ApsaraDB RDS instances.
After migration is complete, release the new instance if it is no longer needed.