przemyslaw.malkowski@bm-support01:~/sandboxes/ps5.7.10$ percona-xtrabackup-2.4.1-Linux-x86_64/bin/innobackupex --apply-log backups/2016-03-10_06-21-34
160310 06:22:41 innobackupex: Starting the apply-log operation

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

percona-xtrabackup-2.4.1-Linux-x86_64/bin/innobackupex version 2.4.1 based on MySQL server 5.7.10 Linux (x86_64) (revision id: a2dc9d4)
xtrabackup: cd to /home/przemyslaw.malkowski/sandboxes/ps5.7.10/backups/2016-03-10_06-21-34
xtrabackup: This target seems to be not prepared yet.
InnoDB: Number of pools: 1
xtrabackup: xtrabackup_logfile detected: size=192086016, start_lsn=(1275383262)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = .
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = .
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 192086016
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = .
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = .
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 192086016
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: PUNCH HOLE support not available
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Uses event mutexes
InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Number of pools: 1
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, total size = 100M, instances = 1, chunk size = 100M
InnoDB: Completed initialization of buffer pool
InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
InnoDB: Highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 1275383262
InnoDB: Ignoring data file './db1/#sql-ib123-1282040285.ibd' with space ID 112. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/sb1.ibd' with space ID 112, since the redo log references ./db1/sb1.ibd with space ID 111.
InnoDB: Ignoring data file './db1/#sql-ib123-1282040285.ibd' with space ID 112. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/#sql-ib123-1282040285.ibd' with space ID 112. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Doing recovery: scanned up to log sequence number 1280625664 (3%)
InnoDB: Doing recovery: scanned up to log sequence number 1285868544 (6%)
InnoDB: Doing recovery: scanned up to log sequence number 1291111424 (9%)
InnoDB: Ignoring data file './db1/#sql-ib123-1282040285.ibd' with space ID 112. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/#sql-ib123-1282040285.ibd' with space ID 112. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/#sql-ib123-1282040285.ibd' with space ID 112. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/#sql-ib123-1282040285.ibd' with space ID 112. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/#sql-ib123-1282040285.ibd' with space ID 112. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/#sql-ib123-1282040285.ibd' with space ID 112. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/#sql-ib123-1282040285.ibd' with space ID 112. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Doing recovery: scanned up to log sequence number 1279052800 (2%)
InnoDB: Doing recovery: scanned up to log sequence number 1284295680 (5%)
InnoDB: Doing recovery: scanned up to log sequence number 1289538560 (8%)
InnoDB: Doing recovery: scanned up to log sequence number 1294781440 (11%)
InnoDB: Doing recovery: scanned up to log sequence number 1300024320 (14%)
InnoDB: Doing recovery: scanned up to log sequence number 1305267200 (17%)
InnoDB: Ignoring data file './db2/#sql-ib126-1282040288.ibd' with space ID 113. Another data file called ./db2/sb1.ibd exists with the same space ID.
InnoDB: Ignoring data file './db2/sb1.ibd' with space ID 114. Another data file called ./db2/#sql-ib125-1282040287.ibd exists with the same space ID.
InnoDB: Ignoring data file './db2/sb1.ibd' with space ID 113. Another data file called ./db2/#sql-ib126-1282040288.ibd exists with the same space ID.
InnoDB: Ignoring data file './db2/#sql-ib125-1282040287.ibd' with space ID 114. Another data file called ./db2/sb1.ibd exists with the same space ID.
InnoDB: Doing recovery: scanned up to log sequence number 1310510080 (20%)
InnoDB: Doing recovery: scanned up to log sequence number 1315752960 (23%)
InnoDB: Doing recovery: scanned up to log sequence number 1320995840 (26%)
InnoDB: Doing recovery: scanned up to log sequence number 1326238720 (29%)
InnoDB: Doing recovery: scanned up to log sequence number 1331481600 (32%)
InnoDB: Ignoring data file './db1/#sql-ib128-1282040290.ibd' with space ID 115. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/sb1.ibd' with space ID 116. Another data file called ./db1/#sql-ib127-1282040289.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/sb1.ibd' with space ID 115. Another data file called ./db1/#sql-ib128-1282040290.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/#sql-ib127-1282040289.ibd' with space ID 116. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Doing recovery: scanned up to log sequence number 1336724480 (35%)
InnoDB: Doing recovery: scanned up to log sequence number 1341967360 (38%)
InnoDB: Doing recovery: scanned up to log sequence number 1347210240 (42%)
InnoDB: Doing recovery: scanned up to log sequence number 1352453120 (45%)
InnoDB: Doing recovery: scanned up to log sequence number 1357696000 (48%)
InnoDB: Ignoring data file './db2/#sql-ib130-1282040292.ibd' with space ID 117. Another data file called ./db2/sb1.ibd exists with the same space ID.
InnoDB: Ignoring data file './db2/sb1.ibd' with space ID 118. Another data file called ./db2/#sql-ib129-1282040291.ibd exists with the same space ID.
InnoDB: Ignoring data file './db2/sb1.ibd' with space ID 117. Another data file called ./db2/#sql-ib130-1282040292.ibd exists with the same space ID.
InnoDB: Ignoring data file './db2/#sql-ib129-1282040291.ibd' with space ID 118. Another data file called ./db2/sb1.ibd exists with the same space ID.
InnoDB: Doing recovery: scanned up to log sequence number 1362938880 (51%)
InnoDB: Doing recovery: scanned up to log sequence number 1368181760 (54%)
InnoDB: Doing recovery: scanned up to log sequence number 1373424640 (57%)
InnoDB: Doing recovery: scanned up to log sequence number 1378667520 (60%)
InnoDB: Doing recovery: scanned up to log sequence number 1383910400 (63%)
InnoDB: Doing recovery: scanned up to log sequence number 1389153280 (66%)
InnoDB: Ignoring data file './db1/#sql-ib132-1282040294.ibd' with space ID 119. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/sb1.ibd' with space ID 120. Another data file called ./db1/#sql-ib131-1282040293.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/sb1.ibd' with space ID 119. Another data file called ./db1/#sql-ib132-1282040294.ibd exists with the same space ID.
InnoDB: Ignoring data file './db1/#sql-ib131-1282040293.ibd' with space ID 120. Another data file called ./db1/sb1.ibd exists with the same space ID.
InnoDB: Doing recovery: scanned up to log sequence number 1394396160 (69%)
InnoDB: Doing recovery: scanned up to log sequence number 1399639040 (72%)
InnoDB: Doing recovery: scanned up to log sequence number 1404881920 (75%)
InnoDB: Doing recovery: scanned up to log sequence number 1410124800 (78%)
InnoDB: Doing recovery: scanned up to log sequence number 1415367680 (81%)
InnoDB: Ignoring data file './db2/#sql-ib134-1282040296.ibd' with space ID 121. Another data file called ./db2/sb1.ibd exists with the same space ID.
InnoDB: Ignoring data file './db2/sb1.ibd' with space ID 122. Another data file called ./db2/#sql-ib133-1282040295.ibd exists with the same space ID.
InnoDB: Ignoring data file './db2/sb1.ibd' with space ID 121. Another data file called ./db2/#sql-ib134-1282040296.ibd exists with the same space ID.
InnoDB: Ignoring data file './db2/#sql-ib133-1282040295.ibd' with space ID 122. Another data file called ./db2/sb1.ibd exists with the same space ID.
InnoDB: Doing recovery: scanned up to log sequence number 1420610560 (85%)
InnoDB: Doing recovery: scanned up to log sequence number 1425853440 (88%)
InnoDB: Doing recovery: scanned up to log sequence number 1431096320 (91%)
InnoDB: Doing recovery: scanned up to log sequence number 1436339200 (94%)
InnoDB: Doing recovery: scanned up to log sequence number 1441582080 (97%)
InnoDB: Doing recovery: scanned up to log sequence number 1446139626 (100%)
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Doing recovery: scanned up to log sequence number 1276038144 (0%)
InnoDB: Ignoring data file './db1/sb1.ibd' with space ID 112. Another data file called ./db1/#sql-ib123-1282040285.ibd exists with the same space ID.
InnoDB: Cannot rename './db1/#sql-ib123-1282040285.ibd' to './db1/sb1.ibd' for space ID 112 because the target file exists. Remove the target file and try again.
InnoDB:  Cannot replay file rename. Remove either file and try again.
InnoDB: Plugin initialization aborted with error Generic error
xtrabackup: innodb_init(): Error occured.