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
[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).