xtrabackup.test.sh

root@server [/backup/mysql]# sudo -u ${XB_USER} innobackupex --user=${MYSQL_BACKUP_USER} --password=${MYSQL_BACKUP_PASS} --apply-log --use-memory 2G ${XB_BACKUP}

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

IMPORTANT: Please check that the apply-log run completes successfully.
           At the end of a successful apply-log run innobackupex
           prints "completed OK!".



140725 13:23:35  innobackupex: Starting ibbackup with command: xtrabackup_56  --defaults-file="/backup/mysql/2014-07-25_13-13-30/backup-my.cnf"  --defaults-group="my   sqld" --prepare --target-dir=/backup/mysql/2014-07-25_13-13-30 --use-memory=2G --tmpdir=/tmp

xtrabackup_56 version 2.1.7 for MySQL server 5.6.15 Linux (x86_64) (revision id: 721)
xtrabackup: cd to /backup/mysql/2014-07-25_13-13-30
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2768896, start_lsn=(265518425676)
xtrabackup: using the following InnoDB configuration for recovery:
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 = 1
xtrabackup:   innodb_log_file_size = 2768896
xtrabackup: using the following InnoDB configuration for recovery:
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 = 1
xtrabackup:   innodb_log_file_size = 2768896
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 2147483648 bytes for buffer pool (set by --use-memory parameter)
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 2.0G
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 265518425676
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages
InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 265520887037 (100%)
InnoDB: Transaction 355139135 was in the XA prepared state.
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 355139584
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48    49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 255724198, file name mysql-bin.000146
2014-07-25 13:23:40 7f9b2594f720  InnoDB: Warning: table 'ultraver_dev/dhmkc_k2_tags'
InnoDB: in InnoDB data dictionary has unknown flags 52.
2014-07-25 13:23:40 7f9b2594f720  InnoDB: Warning: table 'ultraver_dev/dhmkc_k2_items'
InnoDB: in InnoDB data dictionary has unknown flags 52.
2014-07-25 13:23:40 7f9b2594f720  InnoDB: Warning: table 'es_master/dhmkc_k2_tags'
InnoDB: in InnoDB data dictionary has unknown flags 52.
2014-07-25 13:23:40 7f9b2594f720  InnoDB: Warning: table 'es_master/dhmkc_k2_items'
InnoDB: in InnoDB data dictionary has unknown flags 52.
2014-07-25 13:23:40 7f9b2594f720  InnoDB: Warning: table 'projectx_redshark/mag_k2_items'
InnoDB: in InnoDB data dictionary has unknown flags 52.
2014-07-25 13:23:40 7f9b2594f720  InnoDB: Warning: table 'projectx_redshark/mag_k2_tags'
InnoDB: in InnoDB data dictionary has unknown flags 52.
InnoDB: 128 rollback segment(s) are active.
InnoDB: Starting in background the rollback of uncommitted transactions
2014-07-25 13:23:40 7f9a90f2c700  InnoDB: Rolling back trx with id 355139135, 1 rows to undo
InnoDB: Waiting for purge to start
InnoDB: Rollback of trx with id 355139135 completed
2014-07-25 13:23:40 7f9a90f2c700  InnoDB: Rollback of non-prepared transactions completed
2014-07-25 13:23:40 7f9a8f2b7700  InnoDB: Warning: table 'mysql/innodb_index_stats'
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-07-25 13:23:40 7f9a8f2b7700  InnoDB: Warning: table 'mysql/innodb_table_stats'
InnoDB: in InnoDB data dictionary has unknown flags 50.
InnoDB: 5.6.15 started; log sequence number 265520887037

[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 255724198, file name mysql-bin.000146

xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
2014-07-25 13:23:40 7f9b2594f720  InnoDB: Assertion failure in thread 140304327178016 in file trx0sys.cc line 1264
InnoDB: Failing assertion: total_trx >= trx_sys->n_prepared_trx
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
innobackupex: Error:
innobackupex: ibbackup failed at /usr/bin/innobackupex line 2580.
root@server [/backup/mysql]#