[doc] add info how to use binary logs with innobackupex

Bug #836907 reported by Valentine Gostev on 2011-08-29
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Rodrigo Gadea

Bug Description


In section setting up new slave it is advised to use last binlog position from xtrabackup_binlog_pos_innodb. But it is correct when we use only InnoDB/XtraDB as storage engine.

If we use other storage engines (MyISAM) the last binlog position of entire server may differ from last position when InnoDB changed last, so when we utilize multiple storage engines it is more reliable to use xtrabackup_binlog_info file to retrieve last position.

Related branches

tags: added: cr doc i18240
Changed in percona-xtrabackup:
status: New → Confirmed
assignee: nobody → Rodrigo Gadea (rodrigo-gadea-percona)
milestone: none → 1.6.3
Stewart Smith (stewart) on 2011-09-14
Changed in percona-xtrabackup:
status: Confirmed → Fix Committed
Stewart Smith (stewart) on 2011-09-16
Changed in percona-xtrabackup:
importance: Undecided → Low
importance: Low → Medium
Stewart Smith (stewart) on 2011-09-20
Changed in percona-xtrabackup:
status: Fix Committed → Fix Released

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

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

Other bug subscribers