Bug #86718 MEB 4.1 failing for MySQL 5.7.11
Submitted: 15 Jun 2017 13:38 Modified: 18 Oct 2017 18:02
Reporter: Hemant Shah Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Backup Documentation Severity:S3 (Non-critical)
Version:4.1 OS:Red Hat (RHEL7)
Assigned to: CPU Architecture:Any
Tags: MEB Encrypted tables

[15 Jun 2017 13:38] Hemant Shah
Description:
I tried using MEB 4.1, for MySQL EE 5.7.11 and it failed. It seems that it
works on 5.7.12 and higher. May be due to encrypted tables (TDE) 

170511 08:13:47 MAIN    INFO: Encryption password "encrypt-password" not
specified.
170511 08:13:47 MAIN ERROR: Invalid options, MEB would not be able backup
encrypted tables.
 
mysqlbackup failed with errors!
170511 08:13:47 MAIN    INFO: Setting server system variable
'old_alter_table' back to '0'

How to repeat:
Run backup using 4.1 on MySQL 5.7.9, 5.7.10 & 5.7.11

Suggested fix:
It works fine on 5.7.12
[15 Jun 2017 23:13] Jesper wisborg Krogh
Hi,

Thank you for the bug report.

MEB will not work with encrypted InnoDB tablespaces in 5.7.11 due to a bug in MySQL Server. The bug was fixed in 5.7.12 which is why backups of 5.7.12+ works.

This limitation is also documented in http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/meb-encrypted-innodb.html :

"Limitations.  Certain limitations apply when MySQL Enterprise Backup works with encrypted InnoDB tables:

  * For MySQL 5.7.11 and earlier, backup for InnoDB tablespaces encrypted with “MySQL Enterprise Transparent Data Encryption (TDE)” is not supported by mysqlbackup. To perform a backup for those tables, upgrade the server to the latest MySQL 5.7 release, paying attention to any upgrade requirements explained in Changes Affecting Upgrades to MySQL 5.7, especially the one regarding the --early-plugin-load option, and rotate the master key on the upgraded server using the ALTER INSTANCE ROTATE INNODB MASTER KEY statement. Proceed then with the backup process."

Best regards,
Jesper Krogh
MySQL Support
[16 Jun 2017 7:14] MySQL Verification Team
As Jesper pointed out and explained in his earlier note, this is known issue and also documented limitation. For now marking this as duplicate of Bug #85231

Thanks,
Umesh
[16 Jun 2017 13:43] Hemant Shah
I suggest to add this on compatibility page at https://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/bugs.compatibility.html 

And also on- https://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/bugs.backup.html

It would reduce confusion at users end.
Thanks
[20 Jun 2017 3:23] Jesper wisborg Krogh
Hi,

Agree it makes sense to document it in those places. I will convert this to a docs bug to get the documentation updated.

Best regards,
Jesper Krogh
MySQL Support
[28 Aug 2017 18:37] Hemant Shah
Well now MEB 4.0.3 does not work, either on MySQL 5.7.11:

<><><><> [Mon Aug 28 09:07:20 PDT 2017] Starting DB Backup [DB:test_backup_db] 

MySQL Enterprise Backup version 4.0.3 Linux-2.6.18-194.el5-x86_64 [2016/08/04] 
Copyright (c) 2003, 2016, Oracle and/or its affiliates. All Rights Reserved.

 mysqlbackup: INFO: Starting with following command line ...
 //opt/app/mysql/product/backup/meb-4.0.3/bin/mysqlbackup -uroot 
        -pxxxxxxxxxx --socket=/opt/app/mysql/mysql.sock 
        --backup-dir=/opt/app/mysql/backup/2017-08-28/Backup_DB_Dir 
        --with-timestamp 
        --comments=DB Backup [test_backup_db] at Mon Aug 28 09:07:20 PDT 2017 
        --compress --include-tables=test_backup_db.* backup 

 mysqlbackup: INFO: 
 mysqlbackup: INFO: MySQL server version is '5.7.11-enterprise-commercial-advanced-log'
 mysqlbackup: INFO: MySQL server compile os version is 'linux-glibc2.5'
 mysqlbackup: INFO: Got some server configuration information from running server.

IMPORTANT: Please check that mysqlbackup run completes successfully.
           At the end of a successful 'backup' run mysqlbackup
           prints "mysqlbackup completed OK!".

170828 09:07:20 mysqlbackup: INFO: MEB logfile created at /opt/app/mysql/backup/2017-08-28/Backup_DB_Dir/2017-08-28_09-07-20/meta/MEB_2017-08-28.09-07-20_compress_backup.log

 mysqlbackup: INFO: Encryption password "encrypt-password" not specified.
 mysqlbackup: ERROR: Invalid options, MEB would not be able backup encrypted tables.

mysqlbackup failed with errors!

<><><><> [Mon Aug 28 09:07:20 PDT 2017] Recording DB Backup status. 

<><><><> [Mon Aug 28 09:07:20 PDT 2017] DB Backup Failure
[28 Aug 2017 22:41] Jesper wisborg Krogh
Posted by developer:
 
Hi Hemant,

May I recommend logging a Service Request for issues like this? That will give you quicker responses.

In MySQL 5.7.11 the keyring_file plugin is enabled by default (it was disabled again in 5.7.12). So you must either create the backup with --encrypt-password or explicitly disable the keyring_file plugin.

Please see the following Knowledge Base document for details:

MySQL Enterprise Backup (MEB) 4.0.2 And Later Backing Up MySQL Server 5.7.11 Without Using Transparent Data Encryption (TDE) Fails: "mysqlbackup: ERROR: Invalid options, MEB would not be able backup encrypted tables." (Doc ID 2168248.1)

Best regards,
Jesper Krogh
[18 Oct 2017 18:02] Daniel So
Posted by developer:
 
A note on that limitation has been added to https://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/bugs.compatibility.html. 

The change will be visible in the next build of the manual.

https://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/bugs.backup.html already has a general note on the limitations on working with encrypted InnoDB tables.