Data Management:Logically back up and restore a MySQL database hosted on a third-party cloud or a self-managed MySQL database

Features

Create a backup schedule

For more information, see Create a backup schedule.

Configure a backup schedule

1. Log on to the DMS console V5.0.

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

3. On the Backup Schedules page, find the backup schedule that you want to configure and click Configure Backup Schedule in the Actions column.

   

4. 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	The location of the source database. Valid values: No public network IP: Port's self-built database (accessed through the database gateway): backs up a self-managed database by using a database gateway. If you select this option, you must configure the Gateway instance ID parameter. Configure a database gateway for the database in advance. User-Created Database with Public IP Address <IP Address:Port Number>: backs up a self-managed database by using the public IP address of the database. If you select this option, you must also configure the Address and Port Number parameters. ECS-Hosted Database: backs up a database hosted on an Elastic Compute Service (ECS) instance. You must also configure the ECS Instance ID and Port Number parameters. Express Connect DB/VPN Gateway/Intelligent Gateway: backs up a self-managed database by using a virtual private cloud (VPC). If you select this option, you must configure the Peer VPC parameter. Configure a VPC for the database in advance. PolarDB: backs up a PolarDB for MySQL cluster. You must also configure the PolarDB Instance ID parameter.
   	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).
   	PolarDB Cluster ID	The ID of the PolarDB cluster that you want to back up.
   	Database Type	The type of the source database. 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).
   	Peer VPC	The VPC in which the source database resides. Note This parameter is displayed only if you set the Database Location parameter to Express Connect DB/VPN Gateway/Intelligent Gateway.
   	ECS Instance ID	The ID of the ECS instance in which the source database is deployed. Note This parameter is displayed only if you set the Database Location parameter to ECS-Hosted Database.
   	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).
   	Address	The endpoint that is used to connect to the source 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 source 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 source database. The account must have permissions to back up the database. For more information, see Required permissions for different types of database accounts. 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 information about the source database 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 "Configure the SSL encryption feature" 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 Storage fees. 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 you want to store a large amount of data, we recommend that you purchase a subscription storage plan to offset Data Disaster Recovery built-in storage fees. Storage plans are more cost-efficient than the pay-as-you-go billing method.
   	Storage Encryption	The method that is used to encrypt the stored data. Valid values: Encrypted: recommended. Data Disaster Recovery uses AES-256 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.

5. 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 the 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.

6. 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 a 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 the incremental backup feature. 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 if 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.

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

8. After the preceding configurations are complete, click Precheck in the lower-right corner of the page.

9. 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? If your issue persists after you use the solution that is provided in the preceding topic, contact technical support in the DingTalk group (ID: 35585947).

Restore backup data

Assume that the data is lost, damaged or maliciously tampered due to hardware failure, software error, human misoperation or natural disaster after you back up a database. In this case, you can restore the database from a logical backup to the most recent usable state.

Related operations

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

• You can modify the backup source and backup objects of a backup schedule. You can also modify the backup strategies of a backup schedule such as the backup time and backup retention policy. For more information, see Manage a backup schedule.

• You can check the fees that may be charged for a backup schedule. For more information, see Billing FAQ.

• To reduce costs, you can pause a backup schedule that you do not need. For more information, see Pause or start a backup schedule.