This topic describes how to restore the data of an ApsaraDB RDS for MySQL instance.
Prerequisites
The original RDS instance whose data you want to restore must meet the following requirements:
- The original RDS instance is in the Running state and is not locked.
- The original RDS instance does not have ongoing migration tasks.
- If you want to restore data to a point in time, the log backup feature is enabled for the original RDS instance.
- If you want to restore data from a backup set, the original RDS instance has at least one completed physical backup.
For more information about how to restore the data of RDS instances that run other database engines, see the following topics:
Background information
- Method 1: Restore the data of the original RDS instance to a new RDS instance, verify the data on the new RDS instance, and then migrate the data from the new RDS instance back to the original RDS instance. This function was previously known as instance cloning. This topic describes this restoration method.
- Method 2: Restore the data of individual databases or tables to the original RDS instance or to a new RDS instance. For more information, see Restore individual databases and tables of an ApsaraDB RDS for MySQL instance.
- Method 3: Restore the data of the original RDS instance to a new or existing RDS instance that resides in a different region than the original RDS instance. For more information, see Restore the data of an ApsaraDB RDS for MySQL instance across regions.
Precautions
- The new RDS instance must have the same whitelist, backup, and parameter settings as the original RDS instance.
- The data information of the new RDS instance must be the same as the data information that is indicated by the specified data or log backup file of the original RDS instance.
- The account information of the new RDS instance must be the same as the account information that is indicated by the specified data or log backup file of the original RDS instance.
Billing
You must pay for the new RDS instance. For more information, see Pricing, billable items, and billing methods.
Restore data to a new RDS instance
Verify data on the new RDS instance
For more information, see Connect to an ApsaraDB RDS for MySQL 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 back to the original RDS instance. For more information, see Migrate data between RDS instances.
FAQ
- How do I restore a database that I accidentally deleted?
ApsaraDB RDS allows you to restore only the database that you accidentally deleted. For more information, see Restore individual databases and tables of an ApsaraDB RDS for MySQL instance. If your RDS instance does not support the restoration of individual databases or tables, you can restore the data of the database that you accidentally deleted to a new RDS instance, verify the data on the new RDS instance, and then migrate the data from the new RDS instance back to the original RDS instance.
- If my RDS instance does not have a data backup, can I restore the data to a point
in time?
No, if your RDS instance does not have a data backup, you cannot restore the data to a point in time. To restore the data to a point in time, you must restore the data from a full data backup that was completed before the specified point in time. Then, you must restore the incremental data from the log backup file that was generated at the specified point in time.
- When I create an RDS instance to which data is restored, why am I unable to select
a vSwitch for my primary RDS instance?
If no vSwitches are available in the zone that you specified in the Basic Configurations step, you cannot select a vSwitch for your primary RDS instance in the Instance Configuration step. In this case, click go to the VPC console. In the VPC console, create a vSwitch. Then, you can select a vSwitch for your primary RDS instance.