Bug #75899 meb fails to apply log intermittently
Submitted: 13 Feb 2015 18:55 Modified: 26 Feb 2015 20:37
Reporter: Adelina Welch Email Updates:
Status: Won't fix Impact on me:
Category:MySQL Enterprise Backup Severity:S1 (Critical)
Version:3.10.1 OS:Linux
Assigned to: CPU Architecture:Any

[13 Feb 2015 18:55] Adelina Welch
I have been using the backup-and-apply-log operation of mysqlbackup and the 'apply-log' step fails sometimes.  For example, database server A will have a successful backup, database server B will fail to backup, and database server C will have successfully backed up last week, but not this week.  Each database server has the same database schemas. Each schema has a mix of MyISAM and InnoDB tables.  Each database have different amounts of data; the backups of the larger size databases are failing.

The mysqlbackup command is this:

mysqlbackup --defaults-file=/opt/zends/etc/zends.cnf

The database servers are all MySQL advanced enterprise 5.5.37.

I am aware of bug 71515, which identified that mysqlbackup does not work with compressed row tables in MySQL versions less the 5.6.11, so all the compressed row format tables have been migrated to the 'compact' row format (just one table in one schema).

How to repeat:
1. Install MySQL server 5.5.37
2. Install MEB 3.10.1
3. Create a database containing a compressed row format table.
4. Add data to that table.
5. alter that table, changing the row format to compact.
6. Use mysqlbackup as in the description.
[13 Feb 2015 18:57] Adelina Welch
gdb output of a mysqlbackup failure

Attachment: gdblsmrg326a-1.txt (text/plain), 27.91 KiB.

[13 Feb 2015 18:58] Adelina Welch
I'm in the process of having MEB 3.11.1 installed and will retest that version.
[17 Feb 2015 14:26] Adelina Welch
backup failure with MEB 3.11.1

Attachment: mysqlbackupv3-11gdb.txt (text/plain), 27.92 KiB.

[17 Feb 2015 14:28] Adelina Welch
MEB 3.10 and 3.11 have differing opinions on how to report the format of the database files.  3.10 is reporting the files as Barracuda and 3.11 claims the format is Antelope.  However, it's the same database server and databases.
[26 Feb 2015 20:37] Sveta Smirnova
Thank you for the report.

This is known issue. Please read at http://dev.mysql.com/doc/mysql-enterprise-backup/3.11/en/bugs.backup.html:

Compressed InnoDB tables from MySQL server 5.6.10 and earlier cannot be restored with MySQL Enterprise Backup 3.9.0 or later, due to a bug with the InnoDB storage engine (see Bug# 72851 on the MySQL Bug System).