# Xtrabackup failing on 5.6

**URL:** <https://forums.percona.com/t/xtrabackup-failing-on-5-6/3768>\
**Category:** Percona XtraBackup\
**Created:** [September 24, 2014, 1:30pm UTC](https://forums.percona.com/t/xtrabackup-failing-on-5-6/3768 "2014-09-24T13:30:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![shadow](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@shadow](https://forums.percona.com/u/shadow)\
**Post date:** [September 24, 2014, 1:30pm UTC](https://forums.percona.com/t/xtrabackup-failing-on-5-6/3768/1 "2014-09-24T13:30:46Z")

</div>

Using the latest xtrabackup 2.2.4 on mysql 5.6.16, trying to prepare the backup consistently crashes out with:

xtrabackup: export metadata of table ‘vbulletin/threadviews’ to file `./vbulletin/threadviews.exp` (2 indexes)  
xtrabackup: name=GEN\_CLUST\_INDEX, id.low=7773, page=3  
xtrabackup: name=threadid, id.low=7774, page=4  
xtrabackup: export metadata of table ‘vbulletin/attachmentviews’ to file `./vbulletin/attachmentviews.exp` (2 indexes)  
xtrabackup: name=GEN\_CLUST\_INDEX, id.low=7581, page=3  
xtrabackup: name=postid, id.low=7582, page=4  
xtrabackup: export metadata of table ‘vbulletin/postindex’ to file `./vbulletin/postindex.exp` (1 indexes)  
xtrabackup: name=wordid, id.low=7725, page=3

[notice (again)]  
If you use binary log and don’t use any hack of group commit,  
the binary log position seems to be:  
InnoDB: Last MySQL binlog file position 0 1058288605, file name db2.000080

xtrabackup: starting shutdown with innodb\_fast\_shutdown = 0  
innobackupex: Error:  
innobackupex: ibbackup failed line 2617.

Dumping out $cmdline at 2617 shows it’s running: xtrabackup --defaults-file=“/mnt/backup/my.cnf” --defaults-group=“mysqld” --prepare --target-dir=/mnt/backup/2014-09-23 --export --tmpdir=/mnt/mysql/tmp

Syntax I’m calling it with is pretty standard:

innobackupex --defaults-file=/mnt/backup/my.cnf --socket=/tmp/mysql.sock --no-timestamp --slave-info /mnt/backup/2014-09-23 --host=localhost  
innobackupex --export --defaults-file=/mnt/backup/my.cnf --socket=/tmp/mysql.sock --apply-log /mnt/backup/2014-09-23 --host=localhost

/mnt/backup/my.cnf is:

[mysqld]  
server-id = 13  
relay-log = db3-relay-bin  
log-bin = db3

skip-slave-start  
skip-name-resolve  
skip-external-locking  
log-warnings

max\_connections = 2048  
open\_files\_limit = 8192  
key\_buffer = 256M  
max\_connect\_errors = 64

read\_buffer\_size = 1M  
read\_rnd\_buffer\_size = 4M  
sort\_buffer\_size = 1M  
tmp\_table\_size = 128M  
max\_heap\_table\_size = 128M  
myisam\_sort\_buffer\_size = 256M

table\_open\_cache = 16384  
thread\_cache\_size = 256

wait\_timeout = 300  
connect\_timeout = 10

max\_allowed\_packet = 16M  
bulk\_insert\_buffer\_size = 16M

query\_cache\_limit = 2M  
query\_cache\_size = 0

# query\_prealloc\_size = 16384

# query\_alloc\_block\_size = 16384

query\_cache\_type = 0

tmpdir = /mnt/mysql/tmp

slow\_query\_log = 1  
long\_query\_time = 2  
slow\_query\_log\_file = /var/lib/mysql/slow.log

innodb\_file\_per\_table  
innodb\_buffer\_pool\_size = 5G  
innodb\_additional\_mem\_pool\_size = 20M  
innodb\_log\_buffer\_size = 8M  
innodb\_data\_file\_path = ibdata1:100M:autoextend  
innodb\_flush\_log\_at\_trx\_commit = 2  
innodb\_thread\_concurrency = 24

innodb\_io\_capacity = 300  
innodb\_read\_io\_threads = 6  
innodb\_write\_io\_threads = 6  
innodb\_adaptive\_flushing = 1

innodb\_log\_file\_size=256M  
innodb\_log\_files\_in\_group=2

[mysql]  
default-character-set = utf8

[client]  
user=root  
password=XXXXXXXXXXX

[xtrabackup]  
datadir = /mnt/mysql/mysql  
target\_dir = /mnt/backup/

This was working fine when we were on 5.5, pretty sure it broke around the time we moved to 5.6. Originally ran into this on 2.2.3 so upgraded to 2.2.4 but no improvement. Any suggestions on how to troubleshoot further?