The MariaDB Backup API used by Google Cloud Backup and DR includes the following endpoints:
Linux CBT and LVM snapshot: MariaDB
Flush tables with read lock
File-based backups: MariaDB
mysqldumpAPI. This provides the full backup of the database in backup format. On recovery, the
restore dbAPI recovers the database by physically overwriting the data area.
MariaDB log backup: During a log backup, Backup and DR physically copies all the MariaDB binary logs. The MariaDB
Purge binary logs beforeAPI 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, there are no copy-on-writes or I/O-intensive operations.
The following steps describe the process for how to perform data backup and recovery with volume-based backup images and CBT:
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: traditional file-based backup
The following steps describe the process for how to perform data backup and recovery with traditional 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 traditional 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 desired schedule.
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: MariaDB with a traditional file-based backup
Prepare the database for Backup and DR
The Backup and DR MariaDB DBA guide
This page is one in a series of pages specific to protecting and recovering MariaDB databases with Backup and DR. You can find additional information in the following pages:
- Backup and DR for MariaDB
- Prepare the database for Backup and DR
- Add a MariaDB database host and discover databases
- Define policy templates and resource profiles
- Set application details and settings
- Check staging disk format and backup method
- Protect the MariaDB database and its logs
- Mount a MariaDB database
- Recover MariaDB Backups
- Create a MariaDB Backup and DR Workflow