If a backup set is created for an ApsaraDB RDS for MariaDB instance, you can use the backup set to restore the backup data to a new RDS instance. This method is suitable for the analysis of historical data and the restoration of data on which unintended operations are performed.
ApsaraDB RDS for MariaDB allows you to restore data from backup sets. The entire restoration process consists of the following steps:
Restore the backup data of the original RDS instance to a new RDS instance.
Log on to the new RDS instance and verify the data on the new RDS instance.
Migrate the data from the new RDS instance to the original RDS instance.
The original RDS instance meets the following requirements:
The RDS instance is in the Running state and is not locked.
No ongoing migration tasks exist.
At least one backup set is complete. This requirement must be met if you want to restore data from backup sets.
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 backup set that you select.
The new RDS instance contains the account information in the backup set that you select.
You are charged for the new RDS instance. You can view the price of the new RDS instance when you create the instance.
If you want to temporarily use an RDS instance, you can create a pay-as-you-go RDS instance. After data is restored to the new RDS instance, you can migrate the data to the original RDS instance and then release the new RDS instance. For more information, see Migrate data between ApsaraDB RDS instances and Release or unsubscribe from an ApsaraDB RDS for MariaDB instance.
You are immediately charged for the new RDS instance after the instance is created.
Restore the data of your RDS instance to a new RDS instance
- 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 ID of the instance.
In the left-side navigation pane of the page that appears, click Backup and Restoration.
In the upper-left corner of the page that appears, click Restore Database.
Configure the following parameters.
Subscription: A subscription RDS instance is an instance for which you pay an upfront fee. The subscription billing method is more cost-effective than the pay-as-you-go billing method. You are offered lower prices for longer subscription durations.
Pay-As-You-Go: A pay-as-you-go RDS instance is billed per hour based on your actual resource usage. The pay-as-you-go billing method is suitable for short-term use. If you no longer require a pay-as-you-go RDS instance, you can release the pay-as-you-go instance to reduce costs.
The method that is used to restore data. Only By Backup Set is supported.
By Backup Set
The backup set that you want to use to restore data.
High-availability Edition: The database system adopts the classic high-availability architecture that consists of one primary RDS instance and one secondary RDS instance.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.
The default value is Standard. For more information, see Product types.
Zone of Primary Node
The zone of the primary RDS instance.
Multi-zone Deployment: The primary RDS instance and the secondary RDS instance reside in different zones to provide zone-disaster recovery. We recommend that you use this deployment method.
Single-zone Deployment: The primary RDS instance and the secondary RDS instance reside in the same zone.
No significant differences exist between the zones in the same region.
If the RDS instance resides in the same zone as the Elastic Compute Service (ECS) instance on which your application is deployed, these instances can deliver optimal performance. If the RDS instance and the ECS instance reside in different zones in the same region, the performance of the RDS instance and the ECS instance is slightly lower than the performance of the RDS instance and the ECS instance that reside in the same zone.
If Sold Out appears in the upper-right corner of a zone name, this zone does not have sufficient resources. In this case, change the zone.
Zone of Secondary Node
If you select Multi-zone Deployment for the Deployment Method parameter, you must select the zone in which the secondary RDS instance resides.
General-purpose : entry-level instance types. You can select a shared or general-purpose instance type. A shared or 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 instance types. You can select a dedicated or a dedicated host instance type. A dedicated RDS instance exclusively occupies the allocated CPU, memory, storage, and I/O resources. The dedicated host instance family is the highest specifications of the dedicated instance family. A dedicated host RDS instance occupies all the CPU, memory, storage, and I/O resources on the host on which the instance is deployed.
The storage capacity is provisioned to store data files, system files, log files, and transaction files in the RDS instance. You can adjust the storage capacity at a step size of 5 GB.Note
A dedicated RDS instance that uses local SSDs exclusively occupies the allocated resources, and its storage capacity varies based on the instance type. For more information, see Primary ApsaraDB RDS instance types.
Click Next: Instance Configuration.
Configure the following parameters.
The network type of the RDS instance. 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.Note
The network type of the new RDS instance must be the same as the network type of the ECS instance that you want to connect. If the new RDS instance and the ECS instance reside in VPCs, make sure that the instances reside in the same VPC. If the new RDS instance and the ECS instance reside in different VPCs, these instances cannot communicate over an internal network.
The resource group to which the new RDS instance belongs.
Click Next: Confirm Order.
Confirm the settings in the Parameters section, configure 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 RDS instance uses the Subscription billing method.
Verify data on the new RDS instance
For more information about how to log on to an RDS instance, see Connect to an ApsaraDB RDS for MariaDB 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.
Data migration indicates the process of replicating the data of the source RDS instance to the destination RDS instance. Data migration does not interrupt the workloads on the source RDS instances.