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

Data Disaster Recovery provides features for MariaDB databases, such as single-table restoration, geo-redundancy, and long-term archiving. This topic describes how to use Data Disaster Recovery to logically back up and restore a MariaDB database hosted on a third-party cloud or a self-managed MariaDB database.

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 MariaDB and the Backup Method parameter to Logical Backup.
For more information about the granularity based on which Data Disaster Recovery backs up and restores MariaDB databases, see Supported database types and features.

Configure a backup schedule

Log on to the Data Management (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 ID of 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	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 where 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 Instance 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 where 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 where the source database is deployed. Note This parameter is displayed only when 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 source database 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.
	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 storage type of 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.
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. For more information, see Server-side encryption. Non-encrypted: The stored data is not encrypted.

In the Edit Backup Objects step, find the database or table that you want to back up and add it to the Selected section. Then, click Next.
Note
- If you selected Logical Backup when you purchased a backup schedule, Data Disaster Recovery allows you to specify the databases and tables to be backed up during full backups. You can back up a single table, a single database, multiple databases, or an entire database instance for some types of databases during full backups. Data Disaster Recovery supports incremental backups only for some types of databases. By default, all the incremental data is backed up during incremental backup.
  - You can click Select All in the lower-left corner of the Available section to back up the entire database. The database objects that can be backed up and the backup granularity vary based on the database type. 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 configured. To back up the database, you can add the database to the backup schedule on the Edit Backup Objects page of the backup schedule. For more information, see Modify backup objects.
- If you selected Physical Backup when you purchased a backup schedule, you must back up an entire database instance.

In the Configure Backup Time step, configure 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 In scenarios where incremental data needs to be restored, we recommend that you select Periodic Backup and perform a full backup at least once a week. Otherwise, a large number of binary logs must be replayed during restoration. This process is prone to errors and may result in a prolonged recovery time objective (RTO).
Full Data Backup Recurrence	This parameter is required if you set the Full-scale Backup Frequency parameter to Periodic Backup. You can select the days of the week where Data Disaster Recovery runs the backup schedule. Select at least one day of the week.
Start At	The point in time at which Data Disaster Recovery starts a full backup. This parameter must be specified if the Full-scale Backup Frequency parameter is set to Periodic Backup. We recommend that you set a point in time within off-peak hours. Example: 01:00. Note If a previous full data backup is not complete at the start time of the next backup, Data Disaster Recovery skips the next backup.
Incremental Backup	Specifies whether to enable incremental backup. If you enable incremental backup, make sure that the binary logging feature is enabled for the source database. For information about how to check whether the binary logging feature is enabled for an ApsaraDB RDS for MariaDB instance or enable the binary logging feature for an ApsaraDB RDS for MariaDB instance, see Back up an ApsaraDB RDS for MariaDB instance. To check whether the binary logging feature is enabled for a self-managed MariaDB database, run the `SHOW VARIABLES LIKE 'log_bin';` command. If the value of `log_bin` is `ON`, the binary logging feature is enabled. If the value of `log_bin` is `OFF`, the binary logging feature is disabled. Note 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. Note This parameter is displayed only when you configure a backup schedule for a MySQL database.

In the Edit Lifecycle step, configure the lifecycle for full backup data in the Configure Full Data Backup Lifecycle section.
Note
If you set the Incremental Backup parameter to Enable in Step 6, you must configure the lifecycle for incremental backup data.
After the 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 backup schedule status 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 a MariaDB database

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 use 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, configure the parameters in the Set Time Restored To and Configure Destination Database sections, and click Next.

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 is easy to identify. 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 value must be within the time range that is specified by the Time Range Available to Restore parameter. Note If incremental log backup is enabled, Data Disaster Recovery allows you to restore the data to a point in time within the range 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 is complete.
Configure Destination Database	Database Location	The location of the destination database. In this example, this parameter is set to RDS Instance. Make sure that the destination database is running. Data Disaster Recovery also allows you to set the parameter to the following values: User-Created Database with Public IP Address <IP Address:Port Number> ECS-Hosted Database Express Connect DB/VPN Gateway/Intelligent Gateway No public network IP: Port's self-built database (accessed through the database gateway)
	Instance Region	The region where the destination database resides.
	RDS Instance ID	The ID of the destination ApsaraDB RDS instance.
	Database Account	The username of the account that is used to connect to the destination database. The account must have the write permissions on the database.
	Password	The password of the account that is used to connect to the destination database.
	Compliance warranty regarding cross-border data transfers	Read and agree to the compliance commitment 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 some databases by database or table. This reduces the amount of data to be restored and shortens the 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 restoration duration depends on the specifications of the backup schedule and the size of the database to be restored. The restoration duration is shorter for a backup schedule with higher specifications. For more information, see Performance tests on logical backup and physical backup.

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.