Aborting Backups

Backups of MySQL databases can take a long time. The size of backup window for a backup set depends on various factors such as:

• Size of databases/tables in the backup set
• Storage engine used by the databases/tables in the backup set
• Network bandwidth in case of remote backups
• Backup method used
• Backup compression and encryption

ZRM for MySQL provides an option to abort the backup runs. This might be required because the backup windows is too long and overlaps with the application load peak time or errors such as lack of space for backup images. Aborted backup runs cannot be restarted and the partial backup images are not removed.

Example:

mysql-zrm --action abort-backup --backup-set <backup set>

The currently running backup run for the backup set are aborted.

---

Other languages: [[::Aborting Backups|English]] {{#ifexist: {{#if: | | {{#if: | :}}Aborting Backups}}/Fr |  • {{#if: |français| [[::Aborting Backups/Fr|français]]}}|}}

{{#ifexist: {{#if: | | {{#if: | :}}Aborting Backups}}/Zh-cn |  • {{#if: |中文（中国大陆）| [[::Aborting Backups/Zh-cn|中文（中国大陆）]]}}|}}