Bug #64905 mysqlbackup references ibbackup in MySQL error log
Submitted: 8 Apr 2012 2:28 Modified: 24 Aug 2014 6:28
Reporter: Ronald Bradford Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.6.15 OS:Linux (Ubuntu 11.10 64bit)
Assigned to: CPU Architecture:Any
Tags: copy-back, error log, mysqlbackup

[8 Apr 2012 2:28] Ronald Bradford 
Description:
The MySQL error log reports ibbackup, when the mysqlbackup command was used to perform a restore with copy-back.

120408  2:12:04  InnoDB: Initializing buffer pool, size = 4.9G
120408  2:12:05  InnoDB: Completed initialization of buffer pool
InnoDB: The log file was created by ibbackup --apply-log at
InnoDB: ibbackup 120407 21:29:50
...

How to repeat:
$ time /opt/meb/bin/mysqlbackup --defaults-file=/etc/mysql/my.cnf --backup-dir=/mysql/backup/meb/first --innodb-log-files-in-group=2 copy-back
$ sudo service mysql start
$ tail -50 /var/log/mysql/error.log

Suggested fix:
Update messaging to use mysqlbackup instead of ibbackup
[8 Apr 2012 8:06] Valeriy Kravchuk 
Thank you for the problem report. I think that all referenced to ibbackup in both MEB and InnoDB source code should be updated to mention mysqlbackup.
[28 Feb 2013 15:58] Sanjay Manwani 
Assigned to InnoDB team
[28 Feb 2013 16:00] Sanjay Manwani 
Fix needed in InnoDB
[13 Feb 2014 10:50] Daniël van Eeden 
Still present in 3.9.0/5.6.15
[3 Jun 2014 21:56] Daniel So 
Added the following entry to the MySQL Enterprise Backup 3.10.2 changelog:

"After a backup was restored using the copy-back subcommand, the MySQL server's error log referred to “ibbackup” instead of “mysqlbackup” as the performer of the task."
[24 Jun 2014 16:43] Daniel So 
Actually, this bug has not been fixed yet and needs to be reassigned. The above-mentioned changelog entry has been removed.
[19 Aug 2014 15:55] Daniel So 
Posted by developer:
 
Reassigning this to be a server bug.
[24 Aug 2014 6:31] Erlend Dahl 
The server bug has been fixed as of 5.6.20.