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

Reported by Aleksandr Kuzminsky on 2012-04-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup
High
Alexey Kopytov
1.6
High
Alexey Kopytov
2.0
High
Alexey Kopytov
2.1
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

the bug caused by --safe-slave-backup

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers