MySQL Enterprise Backup 4.1 User's Guide  /  Appendixes  /  Backup History Table Update

Appendix D Backup History Table Update

The mysql.backup_history table has been updated with the release of MySQL Enterprise Backup 4.1.2 in the following ways:

  • Changed the storage engine from CSV to InnoDB

  • Added a new column for server UUIDs

When MySQL Enterprise Backup 4.1.2 tries to perform its first full backup on a database, it attempts to perform a format update on the table automatically with the following steps:

  • Create in the new format a table named mysql.backup_history_new and copy into it data from the original mysql.backup_history table.

  • Rename the original mysql.backup_history table to mysql.backup_history_old, and the mysql.backup_history_new table to mysql.backup_history.

For the migration to the new table format to succeed, before performing the first backup task with MySQL Enterprise Backup 4.1.2 , grant the required privileges to the mysqlbackup user on the server by issuing these statements at the mysql client: :

GRANT CREATE, INSERT, DROP ON mysql.backup_history_old TO 'mysqlbackup'@'localhost';
GRANT CREATE, INSERT, DROP, ALTER ON mysql.backup_history_new TO 'mysqlbackup'@'localhost';

If these privileges are not granted, the first full backup on the upgraded server will fail with an error message similar to the following:

180612 08:40:45 MAIN ERROR: MySQL query 'DROP TABLE IF EXISTS mysql.backup_history_old': 1142, DROP command denied to user 'mysqlbackup'@'localhost' for table 'backup_history_old'
mysqlbackup failed with errors!

These privileges are no longer needed after the first full backup has been performed by MySQL Enterprise Backup 4.1.2 , by which point they can be revoked.


If you are working with a multiprimary Group Replication setting, make sure these privileges are granted on all primary nodes; see also Chapter 8, Using MySQL Enterprise Backup with Group Replication.