Docs

RDS for MySQL

Data recovery

Recover to the new instance by time point

This topic describes how to recover data to a new instance by time point.

Prerequisites

An instance has been created and its state is Running or Suspended. For details, see Creating an instance.

Precautions

The engine type, allowlist settings, backup settings, parameter settings, lower case table names setting, and time zone settings of the restored instance are consistent with those of the original instance.

The data information in the restored instance is consistent with the information at the backup point in time.

Point-in-Time Recovery supports second-level precision for restore time points. During point-in-time recovery, the system restores data generated prior to the specified restore time by one second.

Example: Three records (Data A, Data B, Data C) are inserted at timestamps 2026-06-26 15:12:02.999999, 2026-06-26 15:12:03.000000 and 2026-06-26 15:12:03.000001 respectively. If you set the restore time point to 2026-06-26 15:12:03, only Data A will be restored, while Data B and Data C will not be restored.

The restored instance contains the account information at the point in time the backup was used.

If you want to create a pay-as-you-go instance, make sure your account balance is greater than or equal to 100 CNY.

If you want to create a yearly or monthly subscription instance, make sure your account balance is sufficient to pay the order amount.

After you perform operations such as modifying the configuration, upgrading the version, or restoring to the original instance, RDS for MySQL may reset the Binlog number and restart from 000001. If you have configured Binlog monitoring, check the Binlog after these operations to prevent service impact from monitoring failures.

The instance is restored to a point in time through a Backup set + Binlog logs. If there is a long interval between the full backup set and the target recovery point‑in‑time, a large number of Binlog logs need to be replayed, resulting in increased recovery duration. Recovery duration cannot be estimated. The actual time is directly proportional to the real‑world data volume.

Procedure

Log on to the RDS for MySQL console.

In the upper-left corner of the top menu bar, select the project and region for the instance, then click Instance List in the left-side navigation bar.

tip

If the project to which the instance belongs is not set, this operation should select the project as All resources.

On the Instances page, click the target instance name.

At the top of the page, click the Backups tab, and on the Basic backup list tab, click Data recovery.

In the pop-up Restore To dialog box, select the New instance card and click OK.

Configure the following parameters by following the guide on the Restore to New Instance page.

Parameter			Description
Data recovery	Recovery range	The following options are supported: Whole instance: Restore all data from the original instance to the new instance. Specify databases and tables: Restore data from specified databases and tables in the original instance to the new instance. tip Only instances with local SSD storage support the selection of specified databases and tables.
		Restore method	Select By point in time to restore to any time within the log backup retention period.
		Select databases and tables	Select the databases and tables to restore to the new instance. tip Set this parameter only when the Recovery range is Specify databases and tables.
Set database and table names	Selected database & table settings	Set the names of databases and tables after restoration. Batch name adjustment is supported.
Set database and table names		Set rollback time	Select a point in time to recover. tip The rollback time range is automatically calculated based on instance backup and Binlog logs.
New instance configurations	Instance name	Set the instance name. Naming rules are as follows: The length should be between 1 and 128 characters. It cannot start with a digit or hyphen (-). The name consists of Chinese characters, English letters, digits, underscores (_), and hyphens (-).
		Compatible version	Consistent with original instance
		Instance type	The instance type is the same as the source instance by default and cannot be changed.
		Specification type	Supports three specification types: General type (formerly "shared type"), Dedicated type (formerly "general type"), and General type (ARM). General type: Exclusive use of allocated memory and storage resources, shares CPU resources with other shared instances in the same physical machine.CPU utilization is maximized through resource reuse, with high cost performance. CPU utilization is maximized through resource reuse, with high cost performance. Dedicated type: Fully exclusive use of allocated CPU, memory, and storage resources, with stable performance, not affected by other instances in the physical machine. General type (ARM): A general type based on ARM architecture.
		Node specification	Configure the number of nodes and node specifications for the instance. The configuration rules are as follows: If the instance type is Double node: You can add up to 10 read-only nodes. The data on each node is identical to that of the primary node, and the specifications of the read-only nodes can be configured as needed. You can specify different availability zones in the same region for the primary node and the secondary node. The specification of the secondary node is consistent with that of the primary node. Primary, secondary, and read-only nodes can be deployed in up to three availability zones. If the instance type is Multiple node: The specification of the secondary node is consistent with that of the primary node. You can add up to 8 secondary nodes, and at least 1 secondary node needs to be reserved. Nodes can be distributed in at most 3 availability zones. If the instance type is Single node, you only need to set the specification and availability zone for the primary node. tip To enable availability zone-level disaster recovery for double-node and multiple-node instances, it is recommended to deploy the primary and secondary nodes in different availability zones. For double-node instances, if the specification of a read-only node is lower than that of the primary node, high load on the primary node may cause latency or even OOM on the read-only node. It is recommended to select the same or a higher specification for the read-only nodes as that of the primary node. For multi-node instances, it is recommended to reserve an independent secondary node that does not carry business, so that it can be switched to the primary node if necessary. RDS for MySQL assumes no responsibility for any risks or losses incurred due to the failure to configure independent secondary nodes or the inability to complete the primary node switching due to excessive latency of all secondary nodes. When creating an instance, its nodes are preferentially assigned to the default availability zone. You can manually adjust the assignment as needed. The default availability zone is not fixed and is periodically adjusted by RDS for MySQL.
		Storage type	Select the storage type for the instance. RDS for MySQL provides four storage types: local SSDs, Cloud ESSD PL0, Cloud ESSD FlexPL, and High performance cloud disk. The storage types you can select for the new instance depend on the storage type of the original instance. The rules are as follows: If the original instance storage type is Local SSD, you can select any cloud disk type. If the original instance storage type is Cloud ESSD FlexPL, you can select Cloud ESSD FlexPL or High performance cloud disk. If the original instance storage type is Cloud ESSD PL0, you can select Cloud ESSD PL0, Cloud ESSD FlexPL, or High performance cloud disk.
		Storage space	Storage space includes data space, system file space, Binlog file space, and transaction file space. Enter a storage space from 20 GiB to 32,000 GiB in 10 GiB increments based on your business requirements. tip Different storage types and specifications have different storage space value ranges. For detailed information on storage space value ranges, see Product specifications. If the storage type for the new instance is local disk, its storage space cannot be less than 120% of the used space of the original instance. If the storage type for the new instance is cloud disk, its storage space cannot be less than the storage space of the original instance.
		Automatic storage expansion	After enabling, the storage space of the instance can be automatically expanded within the set trigger conditions and the upper limit of automatic expansion. The trigger condition is the proportion of available storage space set, and the value range is 10% to 50%. The value range of the automatic expansion upper limit varies depending on the primary node specification. tip The size of each expansion is the maximum of 5 GiB and 15% of the current storage space, rounded up to the nearest multiple of 5 GiB. If the total storage space of the instance is less than 50 GiB and the available space is less than 10%, the storage space will be expanded by 10 GiB. If the expansion fails due to insufficient host storage space or insufficient account balance, the system will suspend the automatic expansion task and report the "InstanceStorageAutoScalingFailed" event to Cloud Monitoring. You can learn more by Viewing an event and setting alarms by Creating event policy to deal with problems in a timely manner. If the automatic expansion fails, the system will suspend subsequent expansion tasks until the cause of the failure is detected and resolved. You can view and manage automated operations rules configured for instances in the Database Workshop. For more information, refer to Automatic operation and maintenance management.
		Network protocol type	Set the network protocol type for the new instance. You can select IPv4 or IPv4 + IPv6.
		Virtual private cloud	Select the target VPC from the drop-down list. You can also click Create VPC on the right to create a new VPC. For more information on this operation, refer to Creating a VPC. tip A Virtual Private Cloud (VPC), is an isolated network environment with higher security and performance than those of the traditional classic network. You can only choose from the VPC resources under the project that can be accessed by the current account. Creating MySQL instances with shared VPCs is not supported, and shared VPCs are not displayed in the drop-down list.
		Subnet	Choose an available subnet in the selected VPC. tip A subnet is an IP address block in the VPC. All cloud resources in the VPC must be deployed in subnets. For more information, refer to Creating a subnet. By default, the subnet uses Automatic IP assignment to assign private network IP addresses. You can click the assignment method drop-down list, select Manual IP assignment, and then specify a correct and unused IP address in the pop-up box. A MySQL instance can only use subnets in the availability zones of its primary or secondary nodes. Subnet and VPC can be classified into different projects. Confirm that the target subnet and the selected VPC belong to the same project, which can be checked in the Project console.
		Associate allowlist	Set the way the instance associates with the allowlist, Immediately or Later is optional.
		Allowlists	If the way to select the associating allowlist is Immediate, you need to associate the allowlist for the instance on the Create instance page. Click the allowlist text box to enter the Associate allowlist page. On this page, after checking the allowlist, click OK and return to the Create instance page. The selected allowlist will be displayed in the allowlist text box. tip On the Associate allowlist page, you can also create a new allowlist. For more information about creating an allowlist, see Creating an allowlist. An instance can associate up to 100 allowlists. Click "×" next to an allowlist to remove the allowlist. If the region has a default allowlist and the account has privileges for the project of the default allowlist, the default allowlist is automatically associated with the new instance. If the region does not have a default allowlist or the account does not have privileges for the project of the default allowlist, a new instance cannot use the default allowlist and can only use the allowlists under the project specified in the top navigation bar.
		Database port	Specify the private network port for the default endpoint. The value range of the port number is 1000~65534. When you create a new connection endpoint or open a new address, the private network port of the default endpoint will be automatically used to configure as the default port in real time. This default value can be modified by modifying the private network address port of the default endpoint, refer to Modifying address prefix and port.
		Time zone	Consistent with original instance
		Managing parameters	You can choose a system parameter template or a custom parameter template. RDS for MySQL provides three system templates: default parameter template, asynchronous parameter template, and high performance parameter template. For more information about system templates, see About system parameter templates. Parameter templates are determined by compatible versions. If you create a MySQL 5.7 instance, the MySQL 5.7 default parameter template is selected by default. You can also select the MySQL 5.7 asynchronous parameter template or MySQL 5.7 high performance parameter template. You can click View parameter template on the right to go to Parameter template page to create a custom template. For more information, refer to Creating a parameter template.
		Affiliate project	Choose the project to which the instance belongs (optional). By default, the created instance is attributed to the default. tip A project is a virtual concept that includes a set of resources, users, and roles. A project allows you to view and manage a group of resources in a unified manner and control the permissions of users and roles to these resources. For more details, refer to Resource Management.
		Tag	Add tags to the instance (optional). tip You can classify MySQL instances by tags to facilitate instance search and resource aggregation. For more information, see Tag overview. If you need to separate accounts by tags, you need to enable tags in Bill management > Bill tags to apply corresponding tags to bill details. For more details, see Tag-based bill splitting for instances.
		Deletion protection	Deletion protection is a feature of RDS for MySQL that protects instances from accidental deletion. After enabling, the instance can not be deleted directly, it can only be deleted after disabling the deletion protection. tip When creating a new instance, delete protection is enabled by default.
		Kernel version upgrade policy	Method for upgrading the database kernel minor version. The following types are supported. Automatic: When a new kernel minor version is released, the instance is automatically upgraded to the latest kernel minor version during the configured Maintenance window. Manual: When a new kernel version is released, you need to manually upgrade to the latest kernel version in the console. For details, refer to Manually upgrading instance kernel minor versions. tip If an instance's kernel minor version exceeds its maintenance cycle, the system temporarily ignores the upgrade policy and automatically upgrades the kernel minor version.
		Database proxy	Set whether to enable the database proxy service for the instance, and if enabled, set the number of proxy cores. tip The database proxy function for a double-node instance can be configured during and after creation. The proxy function of a multi-node instance cannot be disabled. Single-node instances do not support the database proxy feature. The default is the number of recommended proxy cores. The number of recommended proxy cores is related to the instance type. For a multiple-node instance, the recommended number is the total CPU count of all serviceable nodes multiplied by 0.25 (rounded up). For a double-node instance, the recommended number is the total CPU count of all serviceable nodes multiplied by 0.5 (rounded up). For example, an instance has a primary node and a secondary node, and the number of CPUs for both the primary and secondary nodes is 8. Since (8+8)*0.25=4, the number of recommended proxy cores is 4. The upper limit of the number of proxy cores is 1024, and the lower limit is 2. RDS for MySQL provides 2 cores of free proxy resources for each instance, and the excess is charged according to the number of cores. For detailed billing information about dbatman services, please refer to Billing items and prices.
		Billing method	Select the billing method for the instance. Pay-as-you-go: If you plan to use your MySQL instance for a short period of time, choose pay-as-you-go (hourly rate). You can release the instance when it is no longer needed, saving money. Subscription: If you plan to use your MySQL instance for a long period of time, select Subscription (one-time payment) and choose the duration of the purchase in the lower left corner of the page. Subscription is more affordable than pay-as-you-go, and the longer you buy, the more discounts you get. tip You can also create a pay-as-you-go instance first and confirm that the instance meets the requirements before switching to a yearly/monthly subscription. If you choose pay-as-you-go billing, make sure your Volcano Engine account balance is at least 100 CNY. For more information on billing, see Billing overview.
		Subscription duration	If you choose subscription, you need to select the purchase duration. Support monthly purchase (can purchase 1~9 months) and yearly purchase (can purchase 1~3 years).
		Automatic renewal	If you choose Subscription, you can check the box of Automatic renewal, and the platform will automatically renew the subscription on a monthly basis before the expiration of the instance, so there is no need to renew the subscription manually. You can also modify the renewal configuration at Renewal Management.

Click Confirm order.

Complete the subsequent steps based on the billing type selected.

If Pay-as-you-go is selected: on the Confirm order page, confirm the order details, read and check Database Products and Services Terms and Unsubscription rules, and click Buy now to restore the backup to a new instance.

If Subscription is selected:

On the Confirm order page, confirm the order details, read and check the Database Products and Services Terms and Unsubscription rules, and click Submit the order.

On the Confirm order information page, reconfirm the order information, and click Next step.

On the Submit payment information page, confirm the payment details and select the payment method, click Go to payment, and complete the payment according to the prompts to restore to a new instance.

tip

If you are using a root account, point your mouse to to the right of the Configuration fee at the bottom of the page to view the fee details for purchasing the instance with the current configuration, including the original price, discount, and discounted price. If you are using a IAM account and do not have the policy that allows the QueryDiscountPrice action, you can only view the original price. For more information about policies, refer to Policy overview.

Return to the instance list page, refresh the current list, the original instance state becomes Recovering, and the new instance state becomes Creating. Wait for the backup and recovery to complete and then use it normally.

Related API

API	Description
RestoreToNewInstance	Call the RestoreToNewInstance API to restore data to a new instance.

Last updated: 2026.08.21 16:00:29