explain that xtrabackup_binlog_pos_innodb is created on prepare stage

[Fernando Ipar]

With these versions:

vagrant@node2 ~]$ rpm -qa|grep mysql-community-server
mysql-community-server-5.6.21-2.el6.x86_64
[vagrant@node2 ~]$ uname -a
Linux node2.local 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[vagrant@node2 ~]$ cat /etc/centos-release
CentOS release 6.5 (Final)
[vagrant@node2 ~]$ rpm -qa|grep percona-xtrabackup
percona-xtrabackup-2.2.4-5004.el6.x86_64

If I make a backup like this:

[vagrant@node2 ~]$ sudo innobackupex /backups
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
 LANGUAGE = (unset),
 LC_ALL = (unset),
 LC_CTYPE = "UTF-8",
 LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.

This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

Get the latest version of Percona XtraBackup, documentation, and help resources:
http://www.percona.com/xb/p

141002 14:17:54 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup' (using password: NO).
141002 14:17:54 innobackupex: Connected to MySQL server
141002 14:17:54 innobackupex: Executing a version check against the server...
141002 14:17:54 innobackupex: Done.
IMPORTANT: Please check that the backup run completes successfully.
           At the end of a successful backup run innobackupex
           prints "completed OK!".

innobackupex: Using mysql server version 5.6.21-log

innobackupex: Created backup directory /backups/2014-10-02_14-17-54

141002 14:17:54 innobackupex: Starting ibbackup with command: xtrabackup --defaults-group="mysqld" --backup --suspend-at-end --target-dir=/backups/2014-10-02_14-17-54 --tmpdir=/tmp --extra-lsndir='/tmp'
innobackupex: Waiting for ibbackup (pid=6863) to suspend
innobackupex: Suspend file '/backups/2014-10-02_14-17-54/xtrabackup_suspended_2'

xtrabackup version 2.2.4 based on MySQL server 5.6.17 Linux (x86_64) (revision id: )
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: open files limit requested 0, set to 1024
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 50331648
>> log scanned up to (1626027)
[01] Copying ./ibdata1 to /backups/2014-10-02_14-17-54/ibdata1
[01] ...done
[01] Copying ./mysql/innodb_index_stats.ibd to /backups/2014-10-02_14-17-54/mysql/innodb_index_stats.ibd
[01] ...done
[01] Copying ./mysql/slave_worker_info.ibd to /backups/2014-10-02_14-17-54/mysql/slave_worker_info.ibd
[01] ...done
[01] Copying ./mysql/innodb_table_stats.ibd to /backups/2014-10-02_14-17-54/mysql/innodb_table_stats.ibd
[01] ...done
[01] Copying ./mysql/slave_master_info.ibd to /backups/2014-10-02_14-17-54/mysql/slave_master_info.ibd
[01] ...done
[01] Copying ./mysql/slave_relay_log_info.ibd to /backups/2014-10-02_14-17-54/mysql/slave_relay_log_info.ibd
[01] ...done
>> log scanned up to (1626027)
xtrabackup: Creating suspend file '/backups/2014-10-02_14-17-54/xtrabackup_suspended_2' with pid '6863'

141002 14:17:56 innobackupex: Continuing after ibbackup has suspended
141002 14:17:56 innobackupex: Executing FLUSH TABLES WITH READ LOCK...
141002 14:17:56 innobackupex: All tables locked and flushed to disk

141002 14:17:56 innobackupex: Starting to backup non-InnoDB tables and files
innobackupex: in subdirectories of '/var/lib/mysql'
innobackupex: Backing up files '/var/lib/mysql/mysql/*.{frm,isl,MYD,MYI,MAD,MAI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (74 files)
>> log scanned up to (1626027)
innobackupex: Backing up files '/var/lib/mysql/performance_schema/*.{frm,isl,MYD,MYI,MAD,MAI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (53 files)
141002 14:17:56 innobackupex: Finished backing up non-InnoDB tables and files

141002 14:17:56 innobackupex: Executing FLUSH ENGINE LOGS...
141002 14:17:56 innobackupex: Waiting for log copying to finish

xtrabackup: The latest check point (for incremental): '1626027'
xtrabackup: Stopping log copying thread.
.>> log scanned up to (1626027)

xtrabackup: Creating suspend file '/backups/2014-10-02_14-17-54/xtrabackup_log_copied' with pid '6863'
xtrabackup: Transaction log of lsn (1626027) to (1626027) was copied.
141002 14:17:57 innobackupex: All tables unlocked

innobackupex: Backup created in directory '/backups/2014-10-02_14-17-54'
innobackupex: MySQL binlog position: filename 'mysql-bin.000006', position 279, GTID of the last change 'f7028b4a-47e8-11e4-9d1b-0800274fb806:1'
141002 14:17:57 innobackupex: Connection to database server closed
141002 14:17:57 innobackupex: completed OK!

I don't get a xtrabackup_binlog_pos_innodb file:

[vagrant@node2 ~]$ ls -lah /backups/2014-10-02_14-17-54
total 13M
drwxr-xr-x 4 root root 4.0K Oct 2 14:17 .
drwxr-xr-x 4 root root 4.0K Oct 2 14:17 ..
-rw-r--r-- 1 root root 357 Oct 2 14:17 backup-my.cnf
-rw-r----- 1 root root 12M Oct 2 14:17 ibdata1
drwx------ 2 root root 4.0K Oct 2 14:17 mysql
drwxr-xr-x 2 root root 4.0K Oct 2 14:17 performance_schema
-rw-r--r-- 1 root root 61 Oct 2 14:17 xtrabackup_binlog_info
-rw-r----- 1 root root 89 Oct 2 14:17 xtrabackup_checkpoints
-rw-r--r-- 1 root root 590 Oct 2 14:17 xtrabackup_info
-rw-r----- 1 root root 2.5K Oct 2 14:17 xtrabackup_logfile

Yet the docs say it should be there:

http://www.percona.com/doc/percona-xtrabackup/2.2/xtrabackup_bin/working_with_binary_logs.html

Are the docs wrong or is this a problem with my software combination?

Notice from:

innobackupex: MySQL binlog position: filename 'mysql-bin.000006', position 279, GTID of the last change 'f7028b4a-47e8-11e4-9d1b-0800274fb806:1'

That the server does have binary logging enabled, and xtrabackup_binlog_info is created.

[Alexey Kopytov (akopytov)]

xtrabackup_binlog_pos_innodb is created on prepare. There's apparently some attempt in the manual to explain this, but it could use better wording:

"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."

Let's keep it as a doc request to improve the manual, i.e. make it clear the xtrabackup_binlog_pos_innodb is created as a result of the prepare process, not the backup one.

[Hrvoje Matijakovic (hrvojem)]

Fixed here: https://github.com/percona/percona-xtrabackup/pull/94 and https://github.com/percona/percona-xtrabackup/pull/95

[Shahriyar Rzayev (rzayev-sehriyar)]

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