Backup and DR Service for MySQL

MySQL is the world's most popular open source database, used by high profile web properties. This DBA guide explains how to protect MySQL application consistent database data with Backup and DR in a Linux environment.

MySQL backup API used by Backup and DR

  • Volume level (Linux change block tracking and LVM snapshot) backups: MySQL Flush tables overwriting the data area. With read lock and Unlock tables API.

  • Full+Incremental (file-based traditional) backups: MySQL mysqldump API. This provides the full backup of the database in backup format. On recovery, the restore db API recovers the database by physically overwriting the data area.

  • MySQL log backup: During a log backup, Backup and DR physically copies all the MySQL binary logs. The MySQL purge binary logs before API is used to purge the binary logs.

How it works: Backup and DR volume-based backup with Linux CBT

Only changed blocks are tracked in the bitmap: no copy-on-writes, no I/O-intensive operations.

Data backup and recovery follows these steps:

  1. The Backup and DR agent has CBT to track changed blocks in the database data area.

  2. The agent calls the database API to freeze or pause database for data backup.

  3. Agent creates LVM snapshot of database data area and synthesizes a bitmap.

  4. Agent call to database API to unfreeze database.

  5. Agent copies changed blocks to backup/recovery appliance, which then deletes the snapshot and catalogs the backup.

  6. The appliance issues an internal snapshot and synthesizes a point-in-time virtual full backup.

  7. For data recovery, Backup and DR instantly mounts a rewritable staging disk and brings the database online.

How it works: MySQL with Linux change block tracking and LVM snapshot.

How it works: traditional file-based backup

The following instructions describe the process for how to perform data backup and recovery with traditional file-based backup images:

  1. Backup and DR agent is deployed in the database server.

  2. Mount staging disk on the database server.

  3. Invoke full backup using traditional dump backup command, writing the backup to the mounted disk.

  4. Backup and DR takes an internal snapshot. Log backups are done in a similar fashion directly from the file-system at any desired schedule.

  5. For data recovery, Backup and DR instantly mounts the staging disk to the database server and initiates the database restore operation. Logs can be played to any point in time after the database is restored.

How it works: MySQL with file-based traditional backup.

What's next

Prepare the database for Backup and DR

Other documentation for Backup and DR for MySQL

This page is one in a series of pages specific to protecting and recovering MySQL databases with Backup and DR. You can find additional information at: