--safe-slave-backup results in incorrect binlog info
Bug #977101 reported by
Aleksandr Kuzminsky
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=
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/
XtraBackup version 2.0.0
MySQL version: 5.5.14-log
Related branches
lp:~akopytov/percona-xtrabackup/bug977101-1.6
- Stewart Smith (community): Approve
-
Diff: 108 lines (+40/-23)2 files modifiedinnobackupex (+9/-23)
test/t/bug977101.sh (+31/-0)
lp:~akopytov/percona-xtrabackup/bug977101-2.0
- Stewart Smith (community): Approve
-
Diff: 108 lines (+40/-23)2 files modifiedinnobackupex (+9/-23)
test/t/bug977101.sh (+31/-0)
lp:~akopytov/percona-xtrabackup/bug977101-2.1
- Stewart Smith (community): Approve
-
Diff: 102 lines (+40/-23)2 files modifiedinnobackupex (+9/-23)
test/t/bug977101.sh (+31/-0)
summary: |
- Xtrabackup doesn't save binlog info + --safe-slave-backup results in incorrect binlog info |
To post a comment you must log in.
the bug caused by --safe-slave-backup