Database Backup:Back up a MariaDB database by using logical backup

Create a backup schedule

Configure a backup schedule

In this example, an ApsaraDB RDS for MariaDB backup schedule is configured.

1. Log on to the Database Backup (DBS) console.

2. In the left-side navigation pane, click Backup Schedules. In the top navigation bar, select a region.

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

   

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. DBS automatically generates a backup schedule name. We recommend that you set 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 type of the database instance to be backed up. In this example, RDS Instance is selected. Valid values: RDS Instance: backs up an ApsaraDB RDS instance. If you select this option, you must also configure the RDS Instance ID parameter. PolarDB: backs up a PolarDB instance. If you select this option, you must also configure the POLARDB Instance ID parameter. ECS-Hosted Database: backs up a database hosted on an Elastic Compute Service (ECS) instance. If you select this option, you must also configure the ECS Instance ID and Port Number parameters. 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. 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. For more information, see topics such as Back up a self-managed database in a data center connected to Alibaba Cloud over Express Connect to OSS or DBS and Back up a user-created database in an on-premises data center connected to Alibaba Cloud through VPN Gateway or Smart Access Gateway to OSS or DBS. 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. For more information about the configurations, see Use Database Gateway to back up on-premises databases or private databases on a third-party cloud to Alibaba Cloud.
   	Instance Region	The region in which the source database instance resides. 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 for MariaDB instance.
   	Database Account	The username of the account that is used to connect to the database that you want to back up. 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 database that you want to back up. 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 database that you want to back up 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 database that you want to back up 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 type of storage that is used to store the backup data. Valid values: DBS Storage (recommended): Backup data is stored in DBS without requiring you to create storage space. You are charged based on the volume of your data that is stored in DBS. For more information about the billing method, see Storage fees. To reduce storage costs, we recommend that you use subscription storage plans. For more information, see Use storage plans. OSS For User: You must create a bucket in the Object Storage Service (OSS) console in advance. Note In this example, DBS Storage (recommended) is selected. If you select OSS For User, you must configure the OSS Bucket Name parameter, and only the Standard storage class is supported.
   	Storage Encryption	The method that is used to encrypt the stored data. Valid values: Encrypted: recommended. DBS uses AES-256 to encrypt the stored data. AES-256 is one of the advanced encryption standard ciphers. The server-side encryption feature is used in OSS. When you upload an object to OSS, 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 backup data is not encrypted.

5. 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, DBS 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. DBS supports incremental backups only for some types of databases. By default, all the incremental data is backed up during incremental backups.

     • You can click Select All in the lower-left corner of the page to select all databases. The database objects that can be backed up and the backup granularity vary based on the database type. For more information, see Database engines 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 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.

6. In the Configure Backup Time step, configure the parameters that are described in the following table. Then, click Next in the lower-right corner of the page.

   Parameter	Description
   Full-scale Backup Frequency	The frequency of the backup schedule. Valid values: Periodic Backup and Single Backup. Note In scenarios in which 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	The days of the week on which DBS runs the backup schedule. This parameter must be specified if the Full-scale Backup Frequency parameter is set to Periodic Backup. Select at least one day of the week.
   Full Backup Started At	The point in time at which DBS 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 specify a point in time during off-peak hours. Example: 01:00. Note If a previous full data backup is not complete at the start time of the next backup, DBS 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 database that you want to back up. 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 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 available for a full backup. You can set this parameter to adjust the backup speed. For example, you can reduce the number of backup threads to minimize impacts on the database. Note The maximum number of actual concurrent threads varies based on backup schedule specifications. For more information, see How do I change the maximum backup speed?
   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.

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

8. After the 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 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).

Related operations

• After a database is backed up, you can view the backup schedule or restore the database. For more information, see View a backup schedule or Restore an ApsaraDB RDS for MariaDB database.

• You can also directly create, or create, configure, and start a backup schedule by calling an API operation. 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 retention period of the backup set. For more information, see Manage a backup plan.

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

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