Logically back up and restore an ApsaraDB RDS for MySQL database - Data Management

Data Disaster Recovery provides features such as geo-redundancy, long-term archiving, and single-table restoration for MySQL databases. This topic describes how to use Data Disaster Recovery to automatically back up an ApsaraDB RDS for MySQL instance and restore data of the instance.

Create a backup schedule

For more information, see Create a backup schedule.

Note

When you purchase a backup schedule, set the Data Source Type parameter to MySQL and the Backup Method parameter to Logical Backup.
For information about the granularity based on which Data Disaster Recovery backs up and restores MySQL databases, see Supported database types and features.
In addition to logical backups, Data Disaster Recovery also allows you to back up full data, incremental data, and binary logs of self-managed MySQL databases by using physical backup. For more information, see Physically back up or restore a MySQL database hosted on a third-party cloud or a self-managed MySQL database and Logical backup, physical backup, and snapshot.

Configure a backup schedule

Log on to the DMS console V5.0.
In the top navigation bar, choose Security and Specifications (DBS) > Disaster Recovery for Data (DBS) > Backup Plan.
Note
If you use the DMS console in simple mode, move the pointer over the icon in the upper-left corner of the DMS console and choose All Features > Security and Specifications (DBS) > Disaster Recovery for Data (DBS) > Backup Plan.
On the Backup Schedules page, find the backup schedule that you want to configure and click Configure Backup Schedule in the Actions column.

In the Configure Backup Source and Destination step, configure the backup source and destination, and click Next in the lower-right corner of the page.

Table 1. Parameters

Section	Parameter	Description
N/A	Schedule Name	The name of the backup schedule. Data Disaster Recovery automatically generates a backup schedule name. We recommend that you enter a descriptive name that is easy to identify. Backup schedule names do not need to be unique.
Backup Source Information	Backup Mode	The method that is used to back up data. By default, the backup method that you selected when you purchased the backup schedule is used. In this example, Logical Backup is used.
	Database Location	RDS Instance
	Instance Region	The region in which the source database instance resides. Note This parameter is displayed only if you set the Database Location parameter to RDS Instance, PolarDB, ECS-Hosted Database, or No public network IP: Port's self-built database (accessed through the database gateway).
	RDS Instance ID	The ID of the ApsaraDB RDS instance that you want to back up.
	Database Account	The username of the account that is used to connect to the source database. The account must have permissions to back up the database. For more information, see Account permissions. Note For ApsaraDB RDS databases, read-only permissions are required for backup, and read and write permissions are required for backup and restoration.
	Password	The password of the account that is used to connect to the source database. After you enter the username and password of the database account, click Test Connection next to the password to check whether the database information is valid. If the specified parameters are valid, the Test Passed message is displayed. If the Test Failed message is displayed, click Check next to Test Failed. Modify the information about the source database based on the check results.
	SSL Encryption	The connection method that is used to transmit the backup data. Valid values: Non-encrypted. SSL-encrypted: SSL encrypts network connections at the transport layer to improve the security and integrity of data in transit. However, SSL increases the network connection response time. Note If you want to select SSL-encrypted, you must enable SSL encryption for the ApsaraDB RDS instance before you configure the backup schedule. For more information, see the Step 1: Enable the SSL encryption feature for an RDS instance section of the "Use a cloud certificate to enable SSL encryption" topic.
	Compliance warranty regarding cross-border data transfers	Read and agree to the compliance commitment by selecting the check box.
Backup Destination Information	Backup Storage Type	The type of storage that is used to store the backup data. Valid values: DBS Storage (recommended): Backup data is stored in Data Disaster Recovery without the need to create an Object Storage Service (OSS) bucket. You are charged based on the volume of your data that is stored in Data Disaster Recovery. For more information about the billing method, see Pricing. OSS For User: You must create a bucket in the OSS console in advance. For more information, see Create buckets. Note In this example, DBS Storage (recommended) is selected. If you select OSS For User, you must configure the OSS Bucket Name parameter. Only the Standard storage class is supported. If the volume of data to be backed up is large, we recommend that you purchase subscription storage plans to offset fees. Storage plans are more cost-efficient than the pay-as-you-go billing method.
Backup Destination Information	Storage Encryption	The method that is used to encrypt the stored data. Valid values: Encrypted (recommended): AES-256 is used to encrypt the stored data. The server-side encryption feature is used in OSS. When you upload an object to a bucket for which server-side encryption is enabled, OSS encrypts and stores the object. When you download the encrypted object from OSS, OSS decrypts the object and returns the decrypted object to you. Non-encrypted: The backup data is not encrypted.

In the Edit Backup Objects step, find the database or table that you want to back up in the Available section. Click the rightwards arrow to add the selected database or table to the Selected section. Then, click Next.
Note
- Data Disaster Recovery allows you to back up a single table, a single database, or multiple databases. You can click Select All in the lower-left corner of the Available section to select all databases. The supported backup objects vary based on the database types. For more information, see Supported database types and features.
- By default, a backup schedule cannot be used to back up a database that is created after the backup schedule is created. To back up such a database, you can add the database to the backup schedule on the Configure Task page of the backup schedule. For more information, see Modify backup objects.

In the Configure Backup Time step, set the parameters that are described in the following table and click Next.

Parameter	Description
Full-scale Backup Frequency	The frequency of the backup schedule. Valid values: Periodic Backup and Single Backup. Note If you select Periodic Backup, you must configure the Full Data Backup Recurrence and Start At parameters.
Full Data Backup Recurrence	The days of the week on which Data Disaster Recovery runs the backup schedule. You can select one or more days of the week. Select at least one day of the week.
Start At	The start time of the backup. We recommend that you specify a point in time during off-peak hours. Example: 01:00. Note If a previous full data backup is not finished at the start time of the next backup, Data Disaster Recovery skips the next backup.
Incremental Backup	Specifies whether to enable incremental backup. Note Before you enable incremental backup, make sure that the binary logging feature is enabled for the database that you want to back up. By default, the binary logging feature is enabled for an ApsaraDB RDS for MySQL database. If you use a self-managed database, you must manually enable the binary logging feature. This parameter is displayed only when you set the Full-scale Backup Frequency parameter to Periodic Backup.
Maximum Concurrent Threads for Full Data Backup	The maximum number of concurrent threads that are available for a full backup. You can configure this parameter to adjust the backup speed. For example, you can reduce the number of backup threads to minimize impacts on the database.
Backup network speed limit	The limit on the network bandwidth. Unit: MB/s. You can set the limit based on your business requirements. The default value 0 indicates that the network bandwidth is unlimited.

In the Edit Lifecycle step, configure the lifecycle for full backup data in the Configure Full Data Backup Lifecycle section.
If you set the Incremental Backup parameter to Enable in Step 6, you must configure the lifecycle for incremental backup data. For more information about the lifecycle rules of backup data, see How do I manage the lifecycle rules of backup sets?.
After the preceding configurations are complete, click Precheck in the lower-right corner of the page.
If the Precheck Passed message appears, click Start Task.
Note
- If the state of the backup schedule changes to Running, the backup schedule takes effect.
- If an exception or error occurs when you start the backup schedule, troubleshoot the exception or error at the earliest opportunity. For more information, see How do I fix errors for an abnormal backup schedule in DBS? If your issue persists after you use the solution that is provided in the preceding topic, contact technical support in the DBS DingTalk group (ID: 35585947).

Restore data

Log on to the DMS console V5.0.
In the top navigation bar, choose Security and Specifications (DBS) > Disaster Recovery for Data (DBS) > Backup Plan.
Note
If you use the DMS console in simple mode, move the pointer over the icon in the upper-left corner of the DMS console and choose All Features > Security and Specifications (DBS) > Disaster Recovery for Data (DBS) > Backup Plan.
On the Backup Schedules page, find the backup schedule that you want to manage and click Manage in the Actions column.
On the Configure Task page, click Restore Database in the upper-right corner.

In the Set Time Restored To step of the Create Restore Task wizard, configure the parameters that are described in the following table and click Next.

Note

In this example, backup data is restored to a new database instance. If you set the Target database instance type parameter to Use Exists, you must configure more parameters. For more information, see Table 1 in the Back up an ApsaraDB RDS for MySQL instance or a self-managed MySQL database by using logical backup topic.

Section	Parameter	Description
N/A	Task Name	The name of the task. Data Disaster Recovery automatically generates a task name. We recommend that you specify a name that can help you identify the task. Task names do not need to be unique.
Set Time Restored To	Time Range Available to Restore	The time range from the point in time when the first full backup set is created to the point in time when the latest full backup set is created. The source database can be restored to a point in time within the time range.
Set Time Restored To	Restore To	The point in time to which you want to restore the source database. The point in time must be within the time range that is specified by the Time Range Available to Restore parameter. Note If the incremental backup feature is enabled, Data Disaster Recovery allows you to restore the data to a point in time from the completion of the first full backup to the completion of the last incremental backup. If the incremental backup feature is disabled, Data Disaster Recovery allows you to restore the data to a point in time when a full backup was completed.
Configure Destination Database	Target database instance type	The type of the destination database instance. Valid values: New(Recommend) and Use Exists. Note If you select Use Exists, make sure that the destination database is available when you perform the restore operation.
	Database Location	If Target database instance type is set to New(Recommend), select RDS Instance. If Target database instance type is set to Use Exists, you can select one of the following options: No public network IP: Port's self-built database (accessed through the database gateway) User-Created Database with Public IP Address <IP Address:Port Number> ECS-Hosted Database RDS Instance Express Connect DB/VPN Gateway/Intelligent Gateway PolarDB
	Instance Region	The region in which the new database instance resides. Select the region in which the destination database instance resides. Note This parameter is displayed only if you set the Database Location parameter to RDS Instance, PolarDB, ECS-Hosted Database, No public network IP: Port's self-built database (accessed through the database gateway), or Express Connect DB/VPN Gateway/Intelligent Gateway.
	VPC	The virtual private cloud (VPC) in which the new database instance is deployed. Note For information about how to create a VPC, see Create and manage a VPC.
	DB InstanceClass	The type of the new database instance. Select an instance type from the available instance types that are displayed in the console. Note We recommend that you select the same instance type as that of the source database instance or an instance type with higher specifications.
	Storage Space(GB)	The storage space of the new database instance. Select a size from the available storage space sizes that are displayed in the console. Note To ensure that the database instance has enough space to restore the backed-up data, we recommend that you select a storage space size that is at least 1.3 times the size of the source database instance or five to six times the size of the full backup set. Data is compressed when Data Disaster Recovery performs backup.
	Database Type	The database type. Default value: MySQL. Note This parameter is displayed only if you set the Database Location parameter to User-Created Database with Public IP Address <IP Address:Port Number>, PolarDB, ECS-Hosted Database, Express Connect DB/VPN Gateway/Intelligent Gateway, or No public network IP: Port's self-built database (accessed through the database gateway).
	Gateway instance ID	The ID of the database gateway. Note This parameter is displayed only if you set the Database Location parameter to No public network IP: Port's self-built database (accessed through the database gateway).
	PolarDB Instance ID	The ID of the PolarDB cluster to which you want to restore data.
	RDS Instance ID	The ID of the ApsaraDB RDS instance to which you want to restore data.
	ECS Instance ID	The ID of the Elastic Compute Service (ECS) instance on which the destination database is deployed. Note This parameter is displayed only if you set the Database Location parameter to ECS-Hosted Database.
	Address	The endpoint that is used to connect to the destination database. Note If network security settings, such as firewall settings, are specified on the server where the instance is deployed, click Set Whitelist to obtain the CIDR blocks of Data Disaster Recovery, and then add the CIDR blocks to the whitelist of the server. This allows Data Disaster Recovery to access the server. This parameter is displayed only if you set the Database Location parameter to No public network IP: Port's self-built database (accessed through the database gateway), Express Connect DB/VPN Gateway/Intelligent Gateway, or User-Created Database with Public IP Address <IP Address:Port Number>.
	Port Number	The port number that is used to connect to the destination database. Note This parameter is not displayed if you set the Database Location parameter to ApsaraDB for MongoDB.
	Database Account	The username of the account that is used to connect to the database. The account must have permissions to back up the database. For more information, see Account permissions. Note For ApsaraDB RDS databases, read-only permissions are required for backup, and read and write permissions are required for backup and restoration.
	Password	The password of the account that is used to connect to the destination database. Note After you enter the username and password of the database account, click Test Connection next to the password to check whether the database information is valid. If the specified parameters are valid, the `Test Passed` message is displayed. If the Test Failed message is displayed, click Check next to `Test Failed`. Modify the information about the destination database based on the check results.
	SSL Encryption	The connection method that is used to transmit the backup data. Valid values: Non-encrypted. SSL-encrypted: SSL encrypts network connections at the transport layer to improve the security and integrity of data in transit. However, SSL increases the network connection response time. Note If you want to select SSL-encrypted, you must enable SSL encryption for the ApsaraDB RDS instance before you configure the backup schedule. For more information, see the Step 1: Enable the SSL encryption feature for an RDS instance section of the "Use a cloud certificate to enable SSL encryption" topic.
	Peer VPC	The virtual private cloud (VPC) in which the destination database resides. Note This parameter is displayed only if you set the Database Location parameter to Express Connect DB/VPN Gateway/Intelligent Gateway.
	Compliance warranty regarding cross-border data transfers	Read and agree to the statement of compliance by selecting the check box.

In the Configure Objects to Restore step, configure the parameters that are described in the following table and click Precheck.

Parameter	Description
Conflict Handling	By default, Rename Object with the Same Name is selected for the Conflict Handling parameter. For example, if the `job_info` table to be restored shares the same name with a table in the destination database, the system renames the restored table in the following format: `job_info_dbs_<Restore task ID>_<Timestamp>`.
Objects to Restore	Select the database or table that you want to restore in the Available section and click the rightwards arrow to add it to the Selected section. Note Data Disaster Recovery allows you to restore individual databases or tables. This reduces the amount of data to be restored and shortens the recovery time objective (RTO). For more information about the supported restoration granularity, see Supported database types and features.

If the Precheck Passed message appears in the Precheck dialog box, click Start Task.
To view the database restoration progress, click Restore Tasks in the left-side navigation pane.
Note
The amount of time required to restore a database depends on the specifications of the backup schedule and the size of the database. Higher specifications offer a higher restoration speed. For more information, see Performance tests on logical backup and physical backup.
If you restore a database to a new ApsaraDB RDS instance, the system takes about 5 to 10 minutes to create the instance. After the database is restored, you can view the new ApsaraDB RDS instance in the ApsaraDB RDS console. Alternatively, perform the following operations to view the new ApsaraDB RDS instance: On the Restore Tasks page, click the ID of the restore task. On the page that appears, click the ID of the ApsaraDB RDS instance in the Basic Information section. You are redirected to the ApsaraDB RDS console.

What to do next

You can call the CreateBackupPlan operation to create a backup schedule. You can also call the CreateAndStartBackupPlan operation to create, configure, and start a backup schedule. For more information, see CreateBackupPlan or CreateAndStartBackupPlan.
For more information about how to modify the backup source, backup objects, or backup policy parameters, such as the backup time and backup set retention time of a backup schedule, see Manage a backup schedule.
For more information about fees that may be subsequently incurred by a backup schedule, see Billing FAQ.
You can pause unnecessary backup schedules to reduce costs. For more information, see Pause or start a backup schedule.