--safe-slave-backup results in incorrect binlog info
Reported by
Aleksandr Kuzminsky
on 2012-04-09
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=
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 on 2012-06-12
- Diff: 108 lines (+40/-23) 2 files modified
lp:~akopytov/percona-xtrabackup/bug977101-2.0
- Stewart Smith (community): Approve on 2012-06-12
- Diff: 108 lines (+40/-23) 2 files modified
lp:~akopytov/percona-xtrabackup/bug977101-2.1
- Stewart Smith (community): Approve on 2012-06-12
- Diff: 102 lines (+40/-23) 2 files modified
| Aleksandr Kuzminsky (akuzminsky) wrote : | #1 |
| Alexey Kopytov (akopytov) wrote : | #2 |
Yet another reason to ditch innobackupex.
Alexey Kopytov (akopytov)
on 2012-06-04
| 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