--safe-slave-backup results in incorrect binlog info

Bug #977101 reported by Aleksandr Kuzminsky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
High
Alexey Kopytov
1.6
Fix Released
High
Alexey Kopytov
2.0
Fix Released
High
Alexey Kopytov
2.1
Fix Released
High
Alexey Kopytov

Bug Description

After command "./innobackupex --safe-slave-backup --ibbackup=xtrabackup_55 /mnt/backup/mysql/"
innobackupex doesn't print bin log info correctly:

innobackupex: MySQL binlog position: filename 'Slave_IO_State:', position Waiting for master to send event

# cat /mnt/backup/mysql/2012-04-09_12-21-13/xtrabackup_binlog_info
               Slave_IO_State: Waiting for master to send event

XtraBackup version 2.0.0
MySQL version: 5.5.14-log

Related branches

Revision history for this message
Aleksandr Kuzminsky (akuzminsky) wrote :

the bug caused by --safe-slave-backup

Revision history for this message
Alexey Kopytov (akopytov) wrote :

Yet another reason to ditch innobackupex.

Changed in percona-xtrabackup:
importance: Undecided → High
status: New → Triaged
summary: - Xtrabackup doesn't save binlog info
+ --safe-slave-backup results in incorrect binlog info
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-324

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.