Cloud Backup:Back up a MySQL database

Limitations

Be aware of the following limitations when using the MySQL backup feature:

• Supported systems: The feature supports specific database versions, operating systems, and backup types. For example, you cannot back up a MySQL database that is deployed on Windows. For details, see Supported systems and limits.

• Feature incompatibility: The MySQL backup feature cannot be used if the anti-ransomware service is enabled for your database.

• Container support: Backing up databases that are running in containers is not supported.

• Multiple instances: The MySQL backup feature does not support backing up multiple MySQL instances on a single machine (on-premises server or ECS instance).

• Multi-version tables: The MySQL backup feature does not support backing up multi-version tables, such as tables for which the INSTANT ADD/DROP column feature is enabled. Rebuild the table to clear the multi-version information before you perform a backup operation.

Important considerations

To avoid data loss, unexpected charges, or backup failures, follow these best practices:

• Run an initial full backup
  We strongly recommend running a full backup immediately after creating a new plan. This establishes the necessary baseline for all subsequent incremental and log backups, ensuring your data is fully recoverable.

• Avoid using other backup tools concurrently
  If you use other backup software or scripts to perform full, incremental, or log backups at the same time, incremental or log backups performed by Cloud Backup are not affected. However, some third-party software locks the MySQL database during a full backup. This can block Cloud Backup jobs and cause delays. A delay may also occur when you run a full backup in the Cloud Backup console.

• Use one backup vault per database instance
  Do not back up a single database to different backup vaults. This can cause incremental or log backups to be converted into full backups, consuming unnecessary storage space.

• Plan retention policies carefully

  Restoring from incremental or log backups requires the latest full backup. Consequently, a full backup is retained until all its dependent backups have expired. Configure your retention periods carefully, as this behavior can increase storage consumption and costs. For more information, see How does Cloud Backup clear expired database backup files?

Procedure

After you register a MySQL instance, you must create a backup plan for the instance. Cloud Backup runs MySQL backup jobs based on the specified start time and backup interval. Perform the following steps:

1. Log on to the Cloud Backup console.

2. In the navigation pane on the left, choose Backup > Database Backup. Select a region and click the MySQL tab. Click the ECS Database Instance or Local Database Instance tab. Find the target MySQL instance and click Back Up in the Actions column.

   

3. In the Create Backup Plan panel, configure the following parameters.

   1. Configure the backup content and click Next.

      1. Enter a Plan Name.

      2. Select the database instance to back up.

         

   2. Configure the backup plan and click Next.

      Parameter	Description
      Recommended Plan	Choose from the following pre-defined backup policies, or select Customize to build your own. Typical Plan: Enables the Full Backup and Incremental Backup features. Critical Application: Enables the Full Backup, Incremental Backup, and Log Backup features. Customize: Define a custom backup policy. This option lets you combine different backup types (such as incremental and real-time) and configure their schedules, including start times and intervals.
      Full Backup	A full backup is a complete, point-in-time snapshot of all database files. It can be used to restore the entire database to the exact moment the backup was captured. This backup can be run once or scheduled to run periodically (hourly, daily, weekly, or monthly).
      Incremental Backup	An incremental backup captures only the data that has changed since the last backup. It lets you restore the database to its state at the time the incremental backup was taken. Both one-time and scheduled backups are supported. Important If your MySQL database (earlier than MySQL 5.5) uses the MyISAM engine, you cannot perform incremental backups for the database. In this case, Cloud Backup performs full backups by default. The retention of this backup type depends on the associated full backup. For details on storage implications, see Important considerations.
      Log Backup	Backs up database logs, which can be used for point-in-time recovery. Both one-time and scheduled backups are supported. Important The retention of this backup type depends on the associated full backup. For details on storage implications, see Important considerations. If the node to be backed up is a slave node, set the log_slave_updates=1 parameter in the configuration file to enable this feature. This ensures that log backups run as expected. After you modify the configuration, perform a full backup before you perform a log backup.
      Realtime Backup	Backs up database log data in real time. An initial full backup is required before enabling real-time backup. Once enabled, the feature continuously backs up database logs, achieving a Recovery Point Objective (RPO) of seconds. This feature is free during the trial period, after which charges will apply for the storage used. For more information, see Pricing. Important Only one backup plan that includes real-time backup can be created for a single MySQL database instance.

   3. Configure backup options and click Next.

      Parameter	Description
      Concurrent Threads	The number of concurrent threads for data backup.
      Retry Time	The time interval between two consecutive reconnection attempts if the database is disconnected during backup. Unit: minutes.
      Speed Limit	The maximum data size to back up per second. Unit: MB/s. A value of 0 means no speed limit.

   4. Configure a backup vault and click OK.

      Important

      An instance can be backed up to only one backup vault.

      Parameter	Description
      Backup Vault	Configure the backup vault where backups are stored. Create Vault: Enter a name for the new backup vault. If you leave this blank, a random name is assigned. Select Vault: Select an existing backup vault from the drop-down list. Important After a backup vault is created, you are charged a rental fee for the database backup vault, regardless of whether backup data is generated. For more information, see Billing methods and billable items. The system automatically selects the redundancy type based on what the region supports. In regions that support zone-redundant storage (ZRS), a ZRS-enabled archive vault is created by default. In other regions, a locally redundant storage (LRS)-based archive vault is created. You do not need to select the type manually.
      Vault Name	The name of the backup vault.
      Backup Retention Period	The retention period for backups. Unit: Day, Week, Month, or Year. This setting can be changed on the vault management page. The change applies to all new backup data in the vault. Important The retention of full backups is automatically extended to support dependent backups. For a detailed explanation, see Important considerations.

Verify backup results

• After a backup plan is created, its details are displayed on the Backup Plans tab. The details include the next run time and the backup interval for Full Backup, Incremental Backup, and Log Backup. Cloud Backup uses the specified start time and backup interval to run MySQL database backup jobs.

• At the scheduled time, Cloud Backup starts to run the backup plan. The current backup is complete when the backup job Status is Idle and a time is displayed in the Next Run field.

FAQ

• What do I do if the database instance status is "Database Offline"?

• How to check the client process status, find the log path, and restart the client

• What do I do if the database client status is "Offline"?

• Are there limits on the supported MySQL database versions and operating systems for backup?

• How does a database backup vault purge expired data?

• How do I view the backup data size and backup vault usage? What is the billing basis?

• How do I cancel a database backup?

• How do I back up a newly created database in MySQL?

• What do I do if a database backup fails?

• What is a database backup vault?

More operations

On the Backup Plan tab, find the target backup plan. The following operations are available in the Actions column:

• Edit a backup plan

  Click Edit to modify the backup plan.

• Configure alert settings

  Click ⋮ and select Alert Settings, and then select a backup alert method.

  Backup alert method	Description
  Disabled	The client no longer sends alert notifications.
  Same as Backup Vault	The client uses the same alert method as the backup vault.
  Notify Alibaba Cloud Account	Backup alert notifications for the client are sent by email to the Alibaba Cloud account.
  Custom	Select one or more contacts or contact groups. After configuration, the client sends backup alerts to the selected contacts or groups.

• Delete a backup plan

  Deleting a backup plan will interrupt any running backup or restore jobs.

  Click ⋮ and select Delete Backup to delete a backup plan that is no longer needed.

References

• Register an ECS-hosted MySQL database

• Register an on-premises MySQL database

• To learn about the benefits, working principles, procedures, and limits of database backup, see Feature overview (ECS database) and Feature overview (on-premises databases).

• Cloud Backup supports cross-account backup.