Stay organized with collections
Save and categorize content based on your preferences.
MySQL is the world's most popular open source database, used by high profile web
properties.
This page 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:
The Backup and DR agent has CBT to track changed blocks in the database data
area.
The agent calls the database API to freeze or pause database for data backup.
Agent creates LVM snapshot of database data area and synthesizes a bitmap.
Agent call to database API to unfreeze database.
Agent copies changed blocks to backup/recovery appliance, which then deletes
the snapshot and catalogs the backup.
The appliance issues an internal snapshot and synthesizes a point-in-time
virtual full backup.
For data recovery, Backup and DR instantly mounts a rewritable staging disk
and brings the database online.
How it works: file-based backup
The following instructions describe the process for how to perform data backup
and recovery with file-based backup images:
Backup and DR agent is deployed in the database server.
Mount staging disk on the database server.
Invoke full backup using the dump backup command, writing the backup
to the mounted disk.
Backup and DR takes an internal snapshot.
Log backups are done in a similar fashion directly from the file-system at
any schedule that you configure.
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.
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:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eBackup and DR protects MySQL databases in Linux environments using both volume-level backups with Linux change block tracking (CBT) and LVM snapshots, and file-based backups via the \u003ccode\u003emysqldump\u003c/code\u003e API.\u003c/p\u003e\n"],["\u003cp\u003eVolume-level backups utilize MySQL APIs to freeze and unfreeze the database, create LVM snapshots, track changed blocks with CBT, and copy only changed blocks to the backup/recovery appliance.\u003c/p\u003e\n"],["\u003cp\u003eFile-based backups use the \u003ccode\u003emysqldump\u003c/code\u003e API to write full backups to a mounted staging disk, and log backups are performed directly from the file-system.\u003c/p\u003e\n"],["\u003cp\u003eFor recovery, Backup and DR mounts a rewritable staging disk and brings the database online instantly in the volume-level method, and in the file-based method, it mounts the staging disk and restores the database, with logs being able to be played to any point in time after restoration.\u003c/p\u003e\n"],["\u003cp\u003eMySQL binary logs can be purged via the \u003ccode\u003epurge binary logs before\u003c/code\u003e API during a log backup, which also copies all the binary logs.\u003c/p\u003e\n"]]],[],null,["# Backup and DR Service for MySQL\n\nMySQL is the world's most popular open source database, used by high profile web\nproperties.\nThis page explains how to protect MySQL application consistent database\ndata with Backup and DR in a Linux environment.\n\n**MySQL backup API used by Backup and DR**\n\n- **Volume level (Linux change block tracking and LVM snapshot) backups** :\n MySQL `Flush tables overwriting the data area. With read lock` and\n `Unlock tables` API.\n\n- **Full+Incremental (file-based traditional) backups** : MySQL `mysqldump`\n API. This provides the full backup of the database in backup\n format. On recovery, the restore db API recovers the database by physically\n overwriting the data area.\n\n- **MySQL log backup** : During a log backup, Backup and DR physically copies\n all the MySQL binary logs. The MySQL `purge binary logs before` API is used\n to purge the binary logs.\n\nHow it works: Backup and DR volume-based backup with Linux CBT\n--------------------------------------------------------------\n\nOnly changed blocks are tracked in the bitmap: no copy-on-writes, no I/O-intensive operations.\n\nData backup and recovery follows these steps:\n\n1. The Backup and DR agent has CBT to track changed blocks in the database data\n area.\n\n2. The agent calls the database API to freeze or pause database for data backup.\n\n3. Agent creates LVM snapshot of database data area and synthesizes a bitmap.\n\n4. Agent call to database API to unfreeze database.\n\n5. Agent copies changed blocks to backup/recovery appliance, which then deletes\n the snapshot and catalogs the backup.\n\n6. The appliance issues an internal snapshot and synthesizes a point-in-time\n virtual full backup.\n\n7. For data recovery, Backup and DR instantly mounts a rewritable staging disk\n and brings the database online.\n\nHow it works: file-based backup\n-------------------------------\n\nThe following instructions describe the process for how to perform data backup\nand recovery with file-based backup images:\n\n1. Backup and DR agent is deployed in the database server.\n\n2. Mount staging disk on the database server.\n\n3. Invoke full backup using the dump backup command, writing the backup\n to the mounted disk.\n\n4. Backup and DR takes an internal snapshot.\n Log backups are done in a similar fashion directly from the file-system at\n any schedule that you configure.\n\n5. For data recovery, Backup and DR instantly mounts the staging disk to the\n database server and initiates the database restore operation.\n Logs can be played to any point in time after the database is restored.\n\nWhat's next\n-----------\n\n[Prepare the database for Backup and DR](/backup-disaster-recovery/docs/configuration/otherdb-prep-database)\n\nOther documentation for Backup and DR for MySQL\n-----------------------------------------------\n\nThis page is one in a series of pages specific to protecting and recovering\nMySQL databases with Backup and DR.\nYou can find additional information at:\n\n- [Backup and DR for MySQL](/backup-disaster-recovery/docs/concepts/mysql-intro)\n- [Prepare the database for Backup and DR](/backup-disaster-recovery/docs/configuration/otherdb-prep-database)\n- [Add a MySQL database host and discover databases](/backup-disaster-recovery/docs/configuration/otherdb-add-host)\n- [Define policy templates and resource profiles](/backup-disaster-recovery/docs/create-plan/create-template)\n- [Set application details and settings](/backup-disaster-recovery/docs/backup/app-details-settings-otherdb)\n- [Check staging disk format and backup method](/backup-disaster-recovery/docs/backup/backup-method-staging-disk-otherdb)\n- [Protect the MySQL database and its logs](/backup-disaster-recovery/docs/backup/otherdb-protect)\n- [Mount a MySQL database](/backup-disaster-recovery/docs/access-data/otherdb-mounts)\n- [Recover MySQL Backups](/backup-disaster-recovery/docs/restore-data/otherdb-restore)\n- [Create a MySQL Backup and DR Workflow](/backup-disaster-recovery/docs/access-data/otherdb-workflow)"]]