ApsaraDB RDS：Restore individual databases and tables

Comparison of the modes of restoration for individual databases and tables

The standard restoration feature and the fast restoration feature for individual databases and tables are provided. The fast restoration feature for individual databases and tables is implemented by using performance-type sandbox instances. If the volume of data remains unchanged, the fast restoration feature for individual databases and tables accelerates data restoration by approximately 50% to 95% compared with the standard restoration feature for individual databases and tables. For more information, see Use the emergency recovery feature of an ApsaraDB RDS for MySQL instance and Restore individual databases and tables of an ApsaraDB RDS for MySQL instance.

Prerequisites

Usage notes

• By default, the standard restoration feature for individual databases and tables is enabled for new RDS instances and cannot be disabled. For more information about the usage notes of the standard restoration feature and the fast restoration feature for individual databases and tables, see the Prerequisites section in this topic.

• If you want to restore data of your RDS instance to a point in time, you must make sure that the log backup feature is enabled for the RDS instance. For more information, see Use the automatic backup feature.

• If you restore data of your RDS instance that uses local disks to the same RDS instance, a primary/secondary switchover is triggered during the restoration. The switchover may cause a service interruption that lasts approximately 30 to 120 seconds. Make sure that your application is configured to automatically reconnect to the RDS instance. If you restore the data of the RDS instance to a new RDS instance, no primary/secondary switchovers are triggered during the restoration.

  Important

  If you use the restoration feature for individual databases and tables to restore data of your RDS instance that uses cloud disks to the same RDS instance, no primary/secondary switchovers are triggered during the restoration. However, in some cases, the performance of the RDS instance may decrease and an instance switchover may occur. For more information about the impacts of an instance switchover, see Impacts of an instance switchover.

• You cannot suspend or cancel a restoration task after it is started.

Limits

• If you use the fast restoration feature for individual databases and tables to restore individual databases or tables of an RDS instance that uses local disks, you can restore the data only to the original RDS instance rather than a new RDS instance.

• If binary logs involved in the restoration record the operation to rename a table or a generated column exists in the table, the restoration feature for individual databases and tables is not supported for the table.

• If the restoration involves a large number of databases and tables or a large volume of data or a large number of binary logs are generated within the specified period of time, the restoration is prolonged.

Billing rules

Enable the fast restoration feature for individual databases and tables

To use the fast restoration feature for individual databases and tables for data restoration, you must perform the following steps to enable the feature and then restore databases and tables. The feature is supported only for RDS instances that use local disks and meet the requirements in the "Prerequisites" section of this topic. For more information, see Procedure. Enabling the feature does not affect your workloads.

1. 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.

2. In the left-side navigation pane of the page that appears, click Backup and Restoration.

   Note

   • If your RDS instance uses local disks, the free and paid editions are provided for the fast restoration feature for individual databases and tables. The free edition allows you to restore data only to the point in time at which the last full backup is performed. The paid edition allows you to restore data to any point in time. For more information about billing, see Billing rules.

   • If the [Notice] Fast Restoration Becomes Commercially Available and Billed dialog box appears, you can select Do not show again. and then enable the free or paid edition based on your business requirements. If the dialog box does not appear, you can proceed with the subsequent steps.

3. On the Backup and Restoration page, click the Backup Strategy tab.

4. In the Basic Backup section, click Edit. In the dialog box that appears, turn on Fast Database/Table Restoration.

   Note

   • For RDS instances that use local disks, if Database/Table Restoration is turned off, the Restore Speed option is not displayed. You must turn on Database/Table Restoration. For more information, see Usage notes.

   • If your RDS instance uses local disks, you must configure the CDM Billing Method and CDM Retention Period parameters.

     • Free edition: Set the CDM Billing Method parameter to Previous Full Backup Point in Time (Free Edition). The restored data is retained for one day.

     • Paid edition: Set the CDM Billing Method parameter to Any Point in Time (Paid Edition). You can set the retention period of restored data to 1 to 730 days.

5. Click OK.

Procedure

1. 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.

2. In the left-side navigation pane of the page that appears, click Backup and Restoration. On the page that appears, click Restore Individual Database/Table.

   Note

   If the Restore Individual Database/Table button is not displayed in the ApsaraDB RDS console, check whether the requirements that are described in the Prerequisites section are met.

3. Configure the following parameters.

   Parameter	Description
   Restore To	Current Instance New Instance: Follow Step 5 to automatically create an RDS instance. The databases and tables are restored to the new RDS instance. The restoration does not affect the original RDS instance. After you verify the data in the new RDS instance, you can migrate the data back to the original RDS instance. For more information, see Migrate data between ApsaraDB RDS for MySQL instances. Note The New Instance option is available only for RDS instances that use local disks.
   Restore Speed	Standard Fast: The fast restoration feature for individual databases and tables uses performance-type sandbox instances to accelerate data restoration by approximately 50% to 95% compared with the standard restoration feature for individual databases and tables. For more information, see Create a sandbox instance for emergency disaster recovery of an ApsaraDB RDS for MySQL database. Note If you use the fast restoration feature for individual databases and tables to restore individual databases or tables of an RDS instance, you can restore the data only to the original RDS instance rather than a new RDS instance.
   Restore Method	By Backup Set: If you select this option, you can restore the data from a data backup file. By Time: If you select this option, the system restores full backup data and then incremental log backup data. You can select any point in time within the log backup retention period. For information about how to view or change the log backup retention period, see Use the automatic backup feature. For example, if the both data backup retention period and the log backup retention period of an RDS instance are seven days, you can restore data that is generated within the last seven days. Backup sets that are generated seven days ago are not retained and cannot be restored. Note The By Time option is available only after the log backup feature is enabled. For more information about how to enable the feature, see Use the automatic backup feature.

4. Select the databases and tables that you want to restore. You can also specify the name of each restored database or table. Then, click OK.

   Note

   • You can select up to 50 databases or tables at a time.

   • When you restore databases and tables to the original RDS instance, the names of the restored databases can be the same as the names of the original databases, but the names of the restored tables cannot be the same as the names of the original tables. By default, the system adds _backup to the name of a restored database. You can rename the restored database or table.

   • If you restore the databases and tables to the original RDS instance, you must make sure that the available storage of the RDS instance is sufficient to store the data from these databases and tables.

5. Select a billing method and configure the parameters related to the new RDS instance. This step is required only when you select New instance and Standard.

   • Subscription: A subscription instance is an instance for which you pay an upfront fee. For long-term use, the subscription billing method is more cost-effective than the pay-as-you-go billing method.

   • Pay-as-you-go: You are charged an hourly fee for a pay-as-you-go instance based on your actual resource usage. The pay-as-you-go billing method is suitable for short-term use. If you no longer need a pay-as-you-go instance, you can release the instance to reduce costs.

   Parameter	Description
   Zone	The zone in which the new RDS instance resides. Each zone is an independent physical location within a region. Zones in the same region do not have substantial differences. The new RDS instance can reside in the same zone as the Elastic Compute Service (ECS) instance that you want to connect or in a different zone. Note The new RDS instance must reside in the same region as the original RDS instance. You cannot change the region.
   Instance Type	The instance type of the new RDS instance. Each instance type supports a different number of CPU cores, memory capacity, maximum number of connections, and maximum IOPS. For more information, see Primary ApsaraDB RDS instance types.
   Capacity	The amount of storage that is provisioned to store data files, system files, log files, and transaction files in the new RDS instance.
   Network Type parameter	Classic Network: the traditional type of network. VPC: the recommended type of network. A virtual private cloud (VPC) is an isolated virtual network that provides higher security and higher performance than the classic network.

   Note

   You can go to the Tasks page to view the creation progress of the RDS instance. You can also use one of the following methods to restore individual databases and tables:

   • Use Database Backup (DBS) to create a logical backup. Then, restore data from the generated logical backup file. For more information, see Back up an ApsaraDB RDS for MySQL or self-managed MySQL instance by using logical backup and Restore a MySQL database from a logical backup.

   • Manually create a logical backup. Then, restore data from the generated logical backup file to a self-managed database. For more information, see Manually back up an ApsaraDB RDS for MySQL instance and Restore the data of an ApsaraDB RDS for MySQL instance from a logical backup file to a self-managed MySQL instance.

   • Use mysqldump to back up and restore the RDS instance. For more information, see Use mysqldump to back up and restore an ApsaraDB RDS for MySQL instance.

6. Optional. Connect to the RDS instance and view the data that is restored to the original RDS instance or the new RDS instance. For more information, see Connect to an ApsaraDB RDS for MySQL instance.

   Note

   Make sure that the account that you use to connect to the RDS instance has the permissions to view or manage databases on the RDS instance. We recommend that you use a privileged account to connect to the RDS instance. For more information, see Create an account on an ApsaraDB RDS for MySQL instance.

What to do next

Related operations

FAQ