Database Backup:Configure a backup schedule

Procedure

This topic describes the procedure for configuring a logical backup schedule for an ApsaraDB RDS for MySQL instance. The specific configuration procedure varies based on the database type. For more information about how to configure backup and restoration for different types of databases, see Backup and restoration overview.

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 of the Configure Backup Schedule wizard, configure the backup source and destination, and click Next in the lower-right corner of the page.

   

   Table 1. Database 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 selected.
   	Database Location	The location of the database that you want to back up. Valid values: RDS Instance User-Created Database with Public IP Address <IP Address:Port Number> ECS-Hosted Database Express Connect DB/VPN Gateway/Intelligent Gateway PolarDB No public network IP: Port's self-built database (accessed through the database gateway) Note In this example, RDS Instance is selected. If you select other location types, you must configure more parameters. For more information, see the Other parameters section of this topic.
   	Instance Region	The region in which the ApsaraDB RDS instance that you want to back up resides. If you set the Database Location parameter to PolarDB or ECS-Hosted Database, select the region in which the instance that you want to back up resides.
   	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 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 instances, 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 of 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 instance that you want to back up 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. 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 Configure the SSL encryption feature. Note This parameter is displayed only if you set the Database Type parameter to MySQL.
   	Compliance warranty regarding cross-border data transfers:	Read the statement of compliance and select Acknowledge and Agree.
   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. 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, 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.
   	OSS Bucket Name	The name of the Object Storage Service (OSS) bucket that you want to use to store data. This parameter is displayed only if you set the Backup Storage Type parameter to OSS For User.

   Table 2. Other parameters

   Section	Parameter	Description
   Backup Source Information	Database Type	The type of the database that you want to back up. Default value: MySQL.
   	Gateway instance ID	The ID of the database gateway.
   	Address	The endpoint used to connect to the database that you want to back up.
   	Port Number	The port used to connect to the database that you want to back up.
   	ECS Instance ID	The ID of the Elastic Compute Service (ECS) instance on which the database that you want to back up is deployed.
   	Peer VPC	The virtual private cloud (VPC) in which the database that you want to back up is deployed.
   	PolarDB Instance ID	The ID of the PolarDB for MySQL cluster that you want to back up.

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. Note This parameter is displayed only if you set the Full-scale Backup Frequency parameter to Periodic Backup. By default, the binary logging feature is enabled for an ApsaraDB RDS for MySQL instance. If you use a self-managed database, you must manually enable the binary logging feature.
   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. 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 needs. Default value: 0, which indicates that the network bandwidth is unlimited. Note This parameter is displayed only if you set the Database Type parameter to MySQL.

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

10. (Optional) After data is backed up, you can view the backup schedule or restore the backup data. For more information, see View a backup schedule or Restore a database.

Related API operations

FAQ

• Q: How do I handle an abnormal backup schedule in DBS?

  

  A: If your backup schedule is abnormal, at least one task becomes abnormal in the backup schedule. In most cases, the abnormal task may be a full backup task or an incremental backup task. The abnormal task may also be a task of other types. For more information, see How do I fix errors for an abnormal backup schedule in DBS?

• Q: Is the data stored in a OSS User deleted if a backup schedule is expired and not renewed? Can the backup data of an expired backup schedule be restored by using a new backup schedule?

  A: After a backup schedule is expired or unsubscribed, the data stored in the OSS User is not deleted. However, you cannot restore backup data of a released backup schedule by using a new backup schedule. We recommend that you manually download the backup set before you release or unsubscribe from a backup schedule. This way, you can restore the backup set after the backup schedule is released or unsubscribed. For more information, see Manually download a backup set.

  Note

  • If a backup schedule is expired or disabled because of overdue payment, the backup schedule is in the Locking state and unavailable for use. To continue using the backup schedule, you must renew the backup schedule within seven days. After you renew the backup schedule, the backup schedule is automatically enabled. For more information, see Renew backup schedules. If you do not renew the backup schedule within seven days, DBS assumes that you choose to stop using the backup schedule and your data in DBS will be permanently deleted. The deleted data cannot be restored.

  • If the storage type of the backup schedule is DBS Backup Storage, you can restore the downloaded backup set to a database instance. For more information, see Restore the downloaded backup data.

• Q: What factors affect the time required to back up data? How do I change the maximum backup speed?

  A: The time required to back up data is affected by various factors such as the backup data size, the database workloads, and the network transmission speed. You can change the maximum backup speed in DBS by specifying the maximum number of parallel threads for a full backup and Backup network speed limit parameters for a backup schedule. For more information, see How do I change the maximum backup speed?