Merge lp:~rodrigo-gadea-percona/percona-xtrabackup/docbug-836907 into lp:percona-xtrabackup/2.0

Proposed by Rodrigo Gadea on 2011-08-29
Status: Merged
Approved by: Stewart Smith on 2011-09-14
Approved revision: 302
Merged at revision: 308
Proposed branch: lp:~rodrigo-gadea-percona/percona-xtrabackup/docbug-836907
Merge into: lp:percona-xtrabackup/2.0
Diff against target: 39 lines (+8/-4)
1 file modified
doc/source/xtrabackup_bin/working_with_binary_logs.rst (+8/-4)
To merge this branch: bzr merge lp:~rodrigo-gadea-percona/percona-xtrabackup/docbug-836907
Reviewer Review Type Date Requested Status
Stewart Smith (community) 2011-08-29 Approve on 2011-09-14
Review via email: mp+73310@code.launchpad.net

Description of the change

Fix for DocBug #836907
======================

- Updated how to retrieve the binlog position in xtrabackup_bin/working_with_binary_logs
- It was OK on "PIT with innobackupex": innobackupex/pit_recovery_ibk

To post a comment you must log in.
Stewart Smith (stewart) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/source/xtrabackup_bin/working_with_binary_logs.rst'
2--- doc/source/xtrabackup_bin/working_with_binary_logs.rst 2011-07-07 05:32:50 +0000
3+++ doc/source/xtrabackup_bin/working_with_binary_logs.rst 2011-08-29 22:39:23 +0000
4@@ -6,7 +6,7 @@
5 Finding the Binary Log Position
6 -------------------------------
7
8-You can find the binary log position corresponding to a backup performing the ``--prepare`` process. If your backup is from a server with binary logging enabled, ``xtrabackup`` will create a file named ``xtrabackup_binlog_pos_innodb`` in the target directory. This file contains the binary log file name and position of the exact point in the binary log to which the prepared backup corresponds.
9+You can find the binary log position corresponding to a backup performing the ``--prepare`` process. If your backup is from a server with binary logging enabled, ``xtrabackup`` will create a file named ``xtrabackup_binlog_info`` in the target directory. This file contains the binary log file name and position of the exact point in the binary log to which the prepared backup corresponds.
10
11 You will also see output similar to the following during the prepare stage: ::
12
13@@ -17,12 +17,16 @@
14 the binary log position seems to be:
15 InnoDB: Last MySQL binlog file position 0 3252710, file name ./mysql-bin.000001
16
17-The output should contain the same file name and position as the ``xtrabackup_binlog_pos_innodb`` file. The message about hacking group commit refers to an early implementation of emulated group commit in |Percona Server|.
18+This output can also be found in the :file:`xtrabackup_binlog_pos_innodb` file, but **it is only correct** when no other than |XtraDB| or |InnoDB| are used as storage engines.
19+
20+If other storage engines are used (i.e. |MyISAM|), you should use the :file:`xtrabackup_binlog_info` file to retrieve the position.
21+
22+The message about hacking group commit refers to an early implementation of emulated group commit in |Percona Server|.
23
24 Point-In-Time Recovery
25 ----------------------
26
27-To perform a point-in-time recovery from an ``xtrabackup`` backup, you should prepare and restore the backup, and then replay binary logs from the point shown in the ``xtrabackup_binlog_pos_innodb`` file.
28+To perform a point-in-time recovery from an ``xtrabackup`` backup, you should prepare and restore the backup, and then replay binary logs from the point shown in the :file:`xtrabackup_binlog_info` file.
29
30 A more detailed procedure is found :doc:`here <../innobackupex/pit_recovery_ibk>` (with |innobackupex|).
31
32@@ -30,6 +34,6 @@
33 Setting Up a New Replication Slave
34 ----------------------------------
35
36-To set up a new replica, you should prepare the backup, and restore it to the data directory of your new replication slave. Then in your ``CHANGE MASTER TO`` command, use the binary log filename and position shown in the ``xtrabackup_binlog_pos_innodb`` file to start replication.
37+To set up a new replica, you should prepare the backup, and restore it to the data directory of your new replication slave. Then in your ``CHANGE MASTER TO`` command, use the binary log filename and position shown in the ``xtrabackup_binlog_info`` file to start replication.
38
39 A more detailed procedure is found in :doc:`../howtos/setting_up_replication`.

Subscribers

People subscribed via source and target branches