Restore the data of an RDS MySQL instance

Precautions

• The whitelist settings, backup settings, and parameter settings of the new RDS instance must be the same as those of the original RDS instance.
• The data information of the new RDS instance must be the same as that of the used backup file or that from the specified time point.
• The new RDS instance carries the account information in the used backup file or that from the specified time point.

Fees

For more information, see ApsaraDB RDS MySQL pricing.

Prerequisites

The original RDS instance must meet the following conditions:

• The instance is in the Running state and is not locked.
• No migration task is being performed for the instance.
• If you want to restore the data from a time point, the log backup function is enabled.
• If you want to restore the data from a backup set, at least one backup set is available for the instance.

Restore data to a new RDS instance.

1. Log on to the RDS console.
2. Select the target region.
3. Find the target RDS instance and click the instance ID.
4. In the left-side navigation pane, click Backup and Restoration.
5. In the upper-right corner, click Restore Database (Previously Clone Database).
6. On the displayed Restore Database (Previously Clone Instance) page, select a billing method:
   • Pay-As-You-Go: Fees are calculated by hour according to the actual job size. This billing method is suitable to a short-term RDS instance, which can be released immediately after you finish the data restoration.
   • Subscription: Fees are estimated in advance, and the relevant usage allocation is paid for when you create an RDS instance. This billing method is suitable to a long-term RDS instance, which is cheaper than a pay-as-you-go instance. Additionally, a longer duration of purchase indicates a higher discount rate.
   Note You can change the billing method of an RDS instance from pay-as-you-go to subscription but not from subscription to pay-as-you-go.
7. Set the parameters of the new RDS instance.

   Parameter	Description
   Restore Mode	By Time: You can select any time point within the specified log retention period. For more information about how to view or change the log retention period, see Back up an ApsaraDB RDS MySQL instance. By Backup Set Note The By Time option is available only when the log backup function is enabled.
   Zone	A zone is a physical area within a region. Different zones in the same region are basically the same. You can create an RDS instance in the same or different zone from the corresponding ECS instance. Note The new RDS instance must be located in the same region as the original RDS instance.
   Edition	Basic: The DB system has only one instance. In this edition, compute is separated from storage, which is cost-effective. However, we recommend that you do not use this edition in production environments. High-availability: The DB system has two instances: one master instance and one slave instance. The two instances work in a classic high-availability architecture. Edition: The DB system has three instances: one master instance and two slave instances. The three instances are located in three different zones in the same region to guarantee service availability. This edition is available to the China (Hangzhou), China (Shanghai), China (Shenzhen), and China (Beijing) regions. For more information about the product series, see ApsaraDB for RDS edition overview. The product series available in the console vary depending on the used DB engine version.
   CPU and Memory	The type (including the CPU and memory specifications) of the new RDS instance. The CPU, memory, and storage capacity specifications of the new RDS instance must be higher than hose of the original RDS instance. Otherwise, the data restoration may take a long time. Each instance type supports a specific number of CPU cores, memory size, maximum number of connections, and maximum IOPS. For more information, see Instance types. RDS instances fall into the following three type families: General-purpose instance: A general-purpose instance owns dedicated memory and I/O resources, but shares CPU and storage resources with the other general-purpose instances on the same server. Dedicated instance: A dedicated instance owns dedicated CPU, memory, storage, and I/O resources. Dedicated host: A dedicated-host instance owns all the CPU, memory, storage, and I/O resources on the server where it is located. For example, 8 Cores, 32 GB indicates a general-purpose instance, 8 Cores, 32 GB (Dedicated Instance) indicates a dedicated instance, and 30 Cores, 220GB (Dedicated Host)30 Cores, 220 GB (Dedicated Host) indicates a dedicated-host instance.
   Capacity	Used for storing data, system files, binlog files, and transaction files.
   Network Type	Classic Network: a classic network. VPC (recommended): A VPC is an isolated network environment that provides better security and performance than a classic network.

8. Optional. If the new RDS instance uses the subscription billing method, set the Duration and Quantity parameters.
9. Click Buy Now.
10. On the Order Confirmation page, select Terms of Service, Service Level Agreement, and Terms of Use, then click Pay Now to complete the payment.

Verify data in the new RDS instance

For more information, see Connect to an RDS MySQL instance.

Migrate data to the original RDS instance

After verifying the data in the new RDS instance, you can migrate the data to the original RDS instance.

Data migration refers to migrating data from one RDS instance (the source RDS instance) to another (the destination RDS instance). The data migration operation does not interrupt the source RDS instance.

Precautions

Do not perform DDL operations during the data migration. Otherwise, the data migration may fail.

Procedure

1. Log on to the DTS console.
2. In the left-side navigation pane, click Data Migration.
3. In the upper-right corner, click Create Migration Task.
4. Enter the migration task name, source database information, and destination database information.

   Parameter description:

   • Task Name: By default, DTS automatically generates a name for each migration task. You can change the name as needed.
   • Source Database
     • Instance Type: Select RDS Instance.
     • Instance Region: Select the region where the new RDS instance is located.
     • RDS Instance ID: Select the ID of the new RDS instance.
     • Database Account: Enter the username of the account for the new RDS instance.
     • Database Password: Enter the password of the account for the new RDS instance.
     • Connection: Select Non-encrypted. If the new RDS instance supports SSL encryption and has SSL encryption enabled, then you must select SSL-encrypted.
     Note The values of the Instance Type and RDS Instance ID parameters determine which of the other parameters are displayed.
   • Destination Database
     • Instance Type: Select RDS Instance.
     • Instance Region: Select the region where the original RDS instance is located.
     • RDS Instance ID: Select the ID of the original RDS instance.
     • Database Account: Enter the username of the account for the original RDS instance.
     • Database Password: Enter the password of the account for the original RDS instance.
     • Connection: Select Non-encrypted. If the original RDS supports SSL encryption and has SSL encryption enabled, then you must selectSSL-encrypted.
     Note The values of the Instance Type and RDS Instance ID parameters determine which of the other parameters are displayed.
   
5. Click Set Whitelist and Next.
6. Select Schema Migration and Full Data Migration next to Migration Types.
7. In the Available section, select the objects you want to migrate. Then click > to move the selected objects to the Selected section.
   Note DTS checks for objects that have the same name. If the destination RDS instance has an object whose name is the same as the name of an object to be migrated, the data migration fails.

   In such case, take one of the following two operations:

   • In the Selected section, move the pointer over the object whose name you want to change, click Edit, and in the displayed dialog box enter the new object name.
   • Rename the object in the destination RDS instance.
   
8. Click Precheck.
9. Optional. If the migration task fails the precheck, click next to the check item whose Result is Failed, and resolve the problem according to the failure information.
   
10. On the page that displays migration tasks, select the migration task you created, then click Start.
    
11. When the migration task passes the precheck, click Next.
12. In the Confirm Settings dialog box, confirm the configuration, select Data Transmission Service (Pay-As-You-Go) Service Terms, and click Buy and Start.