Bug #79108 Multiple MEB and MySQL Versions now allowed
Submitted: 4 Nov 2015 1:53 Modified: 4 Nov 2015 10:33
Reporter: Philip Olson Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.3.5 OS:Any
Assigned to: CPU Architecture:Any
Tags: meb

[4 Nov 2015 1:53] Philip Olson
My system has the following:

MySQL Server 5.5.56
MySQL Server 5.6.27
MySQL Server 5.7.9

MySQL Enterprise Backup 3.12.1
MySQL Enterprise Backup 4.0.0

MySQL Workbench 6.3.5

I am unable to use "Online Backup" with MySQL 5.7 because all I see is this:

"MySQL server versions 5.7 and later are not supported by mysqlbackup
version installed on your system (your mysqlbackup version = 3.12.1)"

But, as stated above, I do have 4.0.0 installed as well, but it's not seeing it nor allowing me to find it.

How to repeat:
1. Install MySQL Server 5.6 and 5.7 commercial
2. Install latest MEB 3 and 4 (in my case, 3.12.1 and 4.0.0)
3. Load Workbench
4. Attempt to use "Online Backup" with your 5.6 connection
5. Attempt to use "Online Backup" with your 5.7 connection

Suggested fix:
Not certain, but I did expect the ability to assign one MEB binary to one connection, and another MEB binary to a different connection.
[4 Nov 2015 10:33] Pawel Mroszczyk
Thank you for reporting this bug.  However, I'm closing it as a duplicate because it's already in our internal bug-tracking system, which unfortunately, I cannot make a reference to from this bug system.

But let me assure you, that the issue is being worked on.

BTW, the inability to select the MEB version for a particular database instance is actually not the bug, but a side effect of another underlying problem: when versions don't match, the user is locked out of the MEB configuration screen.  Workbench does actually let you pick mysqlbackup binary per database instance.

As a workaround in the meantime, if you are not uncomfortable with editing configuration files manually, you can assign the path to the proper mysqlbackup binary, by editing Workbench MEB config file.  On Linux, you would typically find it in your MySQL directory.  Here's one on my dev machine (/etc/mysql/mebmanager.cnf):

# Server wide settings for MySQL Workbench, Enterprise Backup

mysql_instance_1 = /var/lib/mysql/
mysql_instance_2 = /home/benny/sandboxes/msb_5_7_9/data/

command = /usr/bin/mysqlbackup3 <======== this is what you need to change
home = /var/lib/mysqlbackuphome
user = mysqlbackup
password =
host = i7
port = 3306
protocol = SOCKET
socket = /var/run/mysqld/mysqld.sock
datadir = /var/lib/mysql/
innodb_data_home_dir =
mysql_version = 5.6.24
datadir_owner = mysql

command = /usr/bin/mysqlbackup4 <======== this is what you need to change
home = /var/lib/mysqlbackuphome-5.7.9
user = mysqlbackup
password =
host = i7
port = 5709
protocol = SOCKET
socket = /tmp/mysql_sandbox5709.sock
datadir = /home/benny/sandboxes/msb_5_7_9/data/
innodb_data_home_dir =
mysql_version = 5.7.9-enterprise-commercial-advanced
datadir_owner = benny

On Windows, look for it in your MySQL configuration path.  C:\ProgramData\MySQL\..... somewhere in there, or C:\Program Files\MySQL\..... , depending on how your system is configured.

I hope this helps.