explain that xtrabackup_binlog_pos_innodb is created on prepare stage
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Low
|
Hrvoje Matijakovic | ||
2.1 |
Invalid
|
Low
|
Unassigned | ||
2.2 |
Fix Released
|
Low
|
Hrvoje Matijakovic | ||
2.3 |
Fix Released
|
Low
|
Hrvoje Matijakovic |
Bug Description
With these versions:
vagrant@node2 ~]$ rpm -qa|grep mysql-community
mysql-community
[vagrant@node2 ~]$ uname -a
Linux node2.local 2.6.32-
[vagrant@node2 ~]$ cat /etc/centos-release
CentOS release 6.5 (Final)
[vagrant@node2 ~]$ rpm -qa|grep percona-xtrabackup
percona-
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://
141002 14:17:54 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:
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/
141002 14:17:54 innobackupex: Starting ibbackup with command: xtrabackup --defaults-
innobackupex: Waiting for ibbackup (pid=6863) to suspend
innobackupex: Suspend file '/backups/
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_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
>> log scanned up to (1626027)
[01] Copying ./ibdata1 to /backups/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
>> log scanned up to (1626027)
xtrabackup: Creating suspend file '/backups/
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/
>> log scanned up to (1626027)
innobackupex: Backing up files '/var/lib/
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/
xtrabackup: Transaction log of lsn (1626027) to (1626027) was copied.
141002 14:17:57 innobackupex: All tables unlocked
innobackupex: Backup created in directory '/backups/
innobackupex: MySQL binlog position: filename 'mysql-bin.000006', position 279, GTID of the last change 'f7028b4a-
141002 14:17:57 innobackupex: Connection to database server closed
141002 14:17:57 innobackupex: completed OK!
I don't get a xtrabackup_
[vagrant@node2 ~]$ ls -lah /backups/
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_
-rw-r----- 1 root root 89 Oct 2 14:17 xtrabackup_
-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://
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-
That the server does have binary logging enabled, and xtrabackup_
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.