MySQL backups
A MySQL backup with a recovery plan.
Follow the SQL export, understand the dump check, and prepare a MySQL restore that your application can use.
Start free trial
Ask AI about CalmBackup
See what it does, who it’s for, and whether it fits your needs.
Opens with product context and a link to this page.
View or copy the prompt
01 / MySQL backups
Give the export a clear scope.
CalmBackup runs mysqldump for the database in your configuration, using single-transaction, routines and triggers. The resulting SQL is bundled with the directories you choose and encrypted before upload.
Confirm that the backup account can export the objects your application requires. Run a manual backup under the same operating-system user that will own the scheduled job, then inspect the result. This catches missing executables, permissions and connection settings before the schedule becomes routine.
02 / MySQL backups
Understand the consistency boundary.
The single-transaction option is useful for transactional tables such as InnoDB. It is not a universal consistency guarantee for every storage engine or for schema changes made during the export. Coordinate operations that can affect the dump.
Database rows and changing application files are collected through separate operations. If a transaction creates a record and an uploaded file together, decide how your application will keep that pair consistent during backup.
03 / MySQL backups
Rehearse the import before an incident.
Prepare an isolated MySQL destination with compatible settings and the credentials the application will use. The restore imports SQL into the configured target, so treat it as a write operation that can replace existing data.
After import, exercise a few meaningful application paths: load a customer record, inspect recent transactions and open an uploaded file. Keep outbound email, payments and other production integrations disabled in the rehearsal environment.
Save the backup identifier, elapsed time, import messages and application checks with the runbook. Repeat the exercise when the database version, schema or deployment process changes substantially.

A calmer place to start
Your next backup.
Your first recovery rehearsal.
Connect a source, keep your encryption key safe, and try a restore. Make the whole routine familiar before you need it.
Start your 14-day trial