# innobackupex apply-log error for fullbackup **URL:** \ **Category:** Percona XtraBackup\ **Created:** [December 31, 2013, 12:18am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168 "2013-12-31T00:18:40Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![Pankaj\_Joshi](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@Pankaj\_Joshi](https://forums.percona.com/u/Pankaj_Joshi)\ **Post date:** [December 31, 2013, 12:18am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/1 "2013-12-31T00:18:40Z")
I am taking a fullbackup using My Data directory are on local directory and I am taking backup on NFS mount point. innobackupex --slave-info --safe-slave-backup /gwire\_dw/extradbbackuptest/ please note : /gwire\_dw/ is a netapp mount point backup is successful. next when I go to prepare the fullbackup using innobackupex --defaults-file=/etc/my.cnf --apply-log --use-memory=8G /gwire\_dw/extradbbackuptest/2013-12-30\_16-39-55 it fails here is the prepare log 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. IMPORTANT: Please check that the apply-log run completes successfully. At the end of a successful apply-log run innobackupex prints “completed OK!”. 131230 21:16:10 innobackupex: Starting ibbackup with command: xtrabackup\_55 --defaults-file=“/etc/my.cnf” --defaults-group=“mysqld” --prepare --target-dir=/gwire\_dw/extradbbackuptest/2013-12-30\_16-39-55 --use-memory=8G --tmpdir=/tmp xtrabackup\_55 version 2.1.5 for Percona Server 5.5.31 Linux (x86\_64) (revision id: 680) xtrabackup: cd to /gwire\_dw/extradbbackuptest/2013-12-30\_16-39-55 xtrabackup: This target seems to be not prepared yet. xtrabackup: xtrabackup\_logfile detected: size=3633463296, start\_lsn=(1417494366104) 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 = 3633463296 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 = 3633463296 xtrabackup: Starting InnoDB instance for recovery. xtrabackup: Using 8589934592 bytes for buffer pool (set by --use-memory parameter) 131230 21:16:17 InnoDB: The InnoDB memory heap is disabled 131230 21:16:17 InnoDB: Mutexes and rw\_locks use GCC atomic builtins 131230 21:16:17 InnoDB: Compressed tables use zlib 1.2.3 131230 21:16:17 InnoDB: Initializing buffer pool, size = 8.0G 131230 21:16:17 InnoDB: Completed initialization of buffer pool 131230 21:16:17 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 1417494366104 131230 21:16:17 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files… InnoDB: Doing recovery: scanned up to log sequence number 1417499608576 (0 %) … InnoDB: Doing recovery: scanned up to log sequence number 1420723979776 (99 %) InnoDB: Doing recovery: scanned up to log sequence number 1420724108086 (99 %) 131230 21:17:30 InnoDB: Starting an apply batch of log records to the database… InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 131230 21:18:55 InnoDB: Assertion failure in thread 140345562953472 in file rem0rec.c line 569 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to [http://bugs.mysql.com](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: [url][http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html[/url]](http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html%5B/url%5D) InnoDB: about forcing recovery. innobackupex: Error: innobackupex: ibbackup failed at /usr/bin/innobackupex line 2517. I checked these 2 lines from the log xtrabackup: cd to /gwire\_dw/extradbbackuptest/2013-12-30\_16-39-55 xtrabackup: This target seems to be not prepared yet. but this directory exists. Please help I am trying this for last 2-3 days and its not working . ---
**Author:** ![Pankaj\_Joshi](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@Pankaj\_Joshi](https://forums.percona.com/u/Pankaj_Joshi)\ **Post date:** [December 31, 2013, 12:28am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/2 "2013-12-31T00:28:10Z")
My.cnf looks like this [mysqld] log-bin = /var/lib/mysqllogs/bin.log log-bin-index = /var/lib/mysqllogs/log-bin.index performance\_schema datadir=/var/lib/mysql relay-log=/var/lib/mysqllogs/relay.log relay-log-index=/var/lib/mysqllogs/relay-log user=mysql symbolic-links=0 max\_connections=500 skip-slave-start max\_allowed\_packet=100M innodb\_file\_format=Barracuda innodb\_flush\_log\_at\_trx\_commit = 2 innodb-log-buffer-size=16M innodb\_buffer\_pool\_size=10G innodb\_log\_file\_size=64M innodb\_file\_per\_table innodb\_flush\_method=O\_DIRECT table\_cache = 3000 skip-name-resolve thread\_cache\_size =150 innodb\_buffer\_pool\_instances=10 ---
**Author:** ![mirfan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mirfan/32/16890_2.png) [@mirfan](https://forums.percona.com/u/mirfan)\ **Post date:** [December 31, 2013, 2:58pm UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/3 "2013-12-31T14:58:44Z")
Can you please try to prepare backup without --defaults-file=/etc/my.cnf option and check if it works. For further details check highlighted “Note” section in documentation here [url][Preparing the backup](http://www.percona.com/doc/percona-xtrabackup/2.1/xtrabackup_bin/preparing_the_backup.html?id=percona-xtrabackup%3axtrabackup%3aprepare%5B/url%5D) ---
**Author:** ![Pankaj\_Joshi](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@Pankaj\_Joshi](https://forums.percona.com/u/Pankaj_Joshi)\ **Post date:** [January 1, 2014, 12:30am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/4 "2014-01-01T00:30:52Z")
I tried running prepare without --defaults-file=/etc/my.cnf and its same error Assertion failure in thread 140336965527296 in file rem0rec.c line 569 ---
**Author:** ![mirfan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mirfan/32/16890_2.png) [@mirfan](https://forums.percona.com/u/mirfan)\ **Post date:** [January 2, 2014, 1:49am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/5 "2014-01-02T01:49:54Z")
Please share source MySQL version from where you took the backup and version of xtrabackup you are trying with. Also, try with latest xtrabackup version and post full backup log in case if error persists. ---
**Author:** ![Pankaj\_Joshi](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@Pankaj\_Joshi](https://forums.percona.com/u/Pankaj_Joshi)\ **Post date:** [January 3, 2014, 5:28am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/6 "2014-01-03T05:28:14Z")
so it failed again though this time with another error extrabacup version percona-xtrabackup-2.1.6-702.rhel6.x86\_64 MySQL version 5.5.34-log Data Directory Size 409 GB Tables are compressed . Backup taken by running this command innobackupex --slave-info --safe-slave-backup /gwire\_dw/extradbbackuptest/ 2\>&1 | tee /tmp/backup3rdjan2004.txt backup log 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](http://www.percona.com/xb/p) 140102 20:40:55 innobackupex: Connecting to MySQL server with DSN ‘dbi:mysql:;mysql\_read\_default\_group=xtrabackup’ as ‘bkpuser’ (using password: YES). 140102 20:40:55 innobackupex: Connected to MySQL server 140102 20:40:55 innobackupex: Executing a version check against the server… # A software update is available: # \* The current version for MySQL Community Server (GPL) is 5.5.35. 140102 20:40:56 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.5.34-log innobackupex: Created backup directory /gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57 140102 20:40:57 innobackupex: Starting ibbackup with command: xtrabackup\_55 --defaults-group=“mysqld” --backup --suspend-at-end --target-dir=/gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57 --tmpdir=/tmp innobackupex: Waiting for ibbackup (pid=7231) to suspend innobackupex: Suspend file ‘/gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57/xtrabackup\_suspended\_2’ xtrabackup\_55 version 2.1.6 for Percona Server 5.5.31 Linux (x86\_64) (revision id: 702) xtrabackup: uses posix\_fadvise(). xtrabackup: cd to /gwire\_dw/mysql\_app278/mysql 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 = 67108864 xtrabackup: using O\_DIRECT > > log scanned up to (1464649810058) > > 140102 20:41:01 InnoDB: Warning: allocated tablespace 44, old maximum was 9 > > [01] Copying ./ibdata1 to /gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57/ibdata1 > > [01] xtrabackup: Page 64 is a doublewrite buffer page, skipping. > > … > > [01] xtrabackup: Page 188 is a doublewrite buffer page, skipping. > > log scanned up to (1464649973184) > > log scanned up to (1464661518012) > > [01] …done > > [01] Copying ./test/pankaj.ibd to /gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57/test/pankaj.ibd > > [01] …done > > [01] Copying ./hydra/url\_count.ibd to /gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57/hydra/url\_count.ibd > > [01] …done > > [01] Copying ./hydra/hydra\_es\_index.ibd to /gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57/hydra/hydra\_es\_index.ibd > > [01] …done > > [01] ./hydra/hydra\_content.ibd is compressed with page size = 8192 bytes > > [01] Copying ./hydra/hydra\_content.ibd to /gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57/hydra/hydra\_content.ibd > > log scanned up to (1464661839410) > > … > > log scanned up to (1467316471704) > > [01] …done > > [01] Copying ./monitoring/heartbeat.ibd to /gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57/monitoring/heartbeat.ibd > > [01] …done > > log scanned up to (1467316474619) > > xtrabackup: Creating suspend file ‘/gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57/xtrabackup\_suspended\_2’ with pid ‘7231’ > > log scanned up to (1467316475067) 140103 02:01:21 innobackupex: Continuing after ibbackup has suspended innobackupex:: Slave open temp tables: 0 140103 02:01:21 innobackupex: Starting to lock all tables… 140103 02:01:21 innobackupex: All tables locked and flushed to disk 140103 02:01:21 innobackupex: Starting to backup non-InnoDB tables and files innobackupex: in subdirectories of ‘/gwire\_dw/mysql\_app278/mysql’ innobackupex: Backing up file ‘/gwire\_dw/mysql\_app278/mysql/test/pankaj.frm’ innobackupex: Backing up file ‘/gwire\_dw/mysql\_app278/mysql/hydra/hydra\_content.frm’ innobackupex: Backing up file ‘/gwire\_dw/mysql\_app278/mysql/hydra/hydra\_es\_index.frm’ innobackupex: Backing up file ‘/gwire\_dw/mysql\_app278/mysql/hydra/url\_count.frm’ innobackupex: Backing up file ‘/gwire\_dw/mysql\_app278/mysql/hydra/hydra\_hash.frm’ innobackupex: Backing up file ‘/gwire\_dw/mysql\_app278/mysql/hydra/db.opt’ innobackupex: Backing up files ‘/gwire\_dw/mysql\_app278/mysql/mysql/\*.{frm,isl,MYD,MYI,MAD,MAI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}’ (75 files) > > log scanned up to (1467316475720) > > log scanned up to (1467316476598) > > log scanned up to (1467316476598) > > innobackupex: Backing up file ‘/gwire\_dw/mysql\_app278/mysql/monitoring/heartbeat.frm’ > > innobackupex: Backing up file ‘/gwire\_dw/mysql\_app278/mysql/monitoring/db.opt’ > > innobackupex: Backing up files ‘/gwire\_dw/mysql\_app278/mysql/performance\_schema/\*.{frm,isl,MYD,MYI,MAD,MAI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}’ (18 files) > > log scanned up to (1467316479669) > > 140103 02:01:26 innobackupex: Finished backing up non-InnoDB tables and files 140103 02:01:26 innobackupex: Waiting for log copying to finish xtrabackup: The latest check point (for incremental): ‘1467297323880’ xtrabackup: Stopping log copying thread. .\>\> log scanned up to (1467316479669) xtrabackup: Creating suspend file ‘/gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57/xtrabackup\_log\_copied’ with pid ‘7231’ xtrabackup: Transaction log of lsn (1464554168682) to (1467316479669) was copied. 140103 02:01:27 innobackupex: All tables unlocked innobackupex:: Starting slave SQL thread innobackupex: Backup created in directory ‘/gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57’ innobackupex: MySQL binlog position: filename ‘bin.000006’, position 107 innobackupex: MySQL slave binlog position: master host ‘10.0.7.79’, filename ‘bin.000186’, position 117927779 140103 02:01:27 innobackupex: Connection to database server closed 140103 02:01:27 innobackupex: completed OK! so backup was successful prepare log is … ---
**Author:** ![Pankaj\_Joshi](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@Pankaj\_Joshi](https://forums.percona.com/u/Pankaj_Joshi)\ **Post date:** [January 3, 2014, 5:30am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/7 "2014-01-03T05:30:11Z")
now Preparing backup command innobackupex --apply-log --use-memory=8G /gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57 2\>&1 | tee /tmp/prepare3rdjan2004.txt 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: [url][Percona XtraBackup - MySQL Database Backup Software](http://www.percona.com/xb/p%5B/url%5D) IMPORTANT: Please check that the apply-log run completes successfully. At the end of a successful apply-log run innobackupex prints “completed OK!”. 140103 02:33:56 innobackupex: Starting ibbackup with command: xtrabackup\_55 --defaults-file=“/gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57/backup-my.cnf” --defaults-group=“mysqld” --prepare --target-dir=/gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57 --use-memory=8G --tmpdir=/tmp xtrabackup\_55 version 2.1.6 for Percona Server 5.5.31 Linux (x86\_64) (revision id: 702) xtrabackup: cd to /gwire\_dw/extradbbackuptest/2014-01-02\_20-40-57 xtrabackup: This target seems to be not prepared yet. 140103 2:33:56 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. xtrabackup: Warning: cannot open ./xtrabackup\_logfile. will try to find. xtrabackup: ‘ib\_logfile0’ seems to be ‘xtrabackup\_logfile’. will retry. xtrabackup: xtrabackup\_logfile detected: size=3933044736, start\_lsn=(1464554168682) 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 = 3933044736 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 = 3933044736 xtrabackup: Starting InnoDB instance for recovery. xtrabackup: Using 8589934592 bytes for buffer pool (set by --use-memory parameter) 140103 2:34:03 InnoDB: The InnoDB memory heap is disabled 140103 2:34:03 InnoDB: Mutexes and rw\_locks use GCC atomic builtins 140103 2:34:03 InnoDB: Compressed tables use zlib 1.2.3 140103 2:34:03 InnoDB: Initializing buffer pool, size = 8.0G 140103 2:34:03 InnoDB: Completed initialization of buffer pool 140103 2:34:03 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 1464554168682 140103 2:34:04 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files… InnoDB: Doing recovery: scanned up to log sequence number 1464559411200 (0 %) InnoDB: Doing recovery: scanned up to log sequence number 1464564654080 (0 %) InnoDB: Doing recovery: scanned up to log sequence number 1464569896960 (0 %) InnoDB: Doing recovery: scanned up to log sequence number 1464575139840 (0 %) InnoDB: Doing recovery: scanned up to log sequence number 1464580382720 (0 %) InnoDB: Doing recovery: scanned up to log sequence number 1464585625600 (0 %) InnoDB: Doing recovery: scanned up to log sequence number 1464590868480 (1 %) InnoDB: Doing recovery: scanned up to log sequence number 1467316479669 (79 %) 140103 2:35:07 InnoDB: Starting an apply batch of log records to the database… InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 InnoDB: Probable data corruption on page 50419077 InnoDB: Original record (compact record) InnoDB: on that page. InnoDB: Cannot find the dir slot for record (compact record) InnoDB: on that page! 140103 2:35:40 InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex 0000000003012373338303263653600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000700063000001553c72e293; asc U U U\= MySQL-4.1.1 and stored already) 25 InnoDB: Page may be an update undo log page InnoDB: Page may be an index page where index id is 55 140103 2:35:40 InnoDB: Assertion failure in thread 139802270525184 in file page0page.c line 153 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to [http://bugs.mysql.com](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: [url][http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html[/url]](http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html%5B/url%5D) InnoDB: about forcing recovery. innobackupex: Error: innobackupex: ibbackup failed at /usr/bin/innobackupex line 2569. I am not sure what’s happening here , my.cnf is same what was mentioned earlier . please help. ---
**Author:** ![mixa](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mixa/32/16881_2.png) [@mixa](https://forums.percona.com/u/mixa)\ **Post date:** [January 7, 2014, 10:05am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/8 "2014-01-07T10:05:48Z")
Hi Pankaj Joshi The root cause of problem could be data corruption. Let me help you to check if it’s so. - create file “ibd\_checksum.sh” with source code: #!/bin/bash for i in $(ls /var/lib/mysql/_/_.ibd) do innochecksum -v $i done - set permissions: chmod +x ibd\_checksum.sh - run it and save it’s log: sudo ./ibdscript.sh \> idb\_checksum.log And attach here idb\_checksum.log or send us the output of “sudo ./ibdscript.sh” command I would also ask you to run this command in mysql: select i.index\_id, i.name, t.table\_id, t.schema, t.name from innodb\_sys\_indexes i left join innodb\_sys\_tables t on i.table\_id = t.table\_id where index\_id=55 * * * If you’ll find that you have a corrupted table then you can try innodb\_force\_recovery. [http://dev.mysql.com/doc/refman/5.5/](http://dev.mysql.com/doc/refman/5.5/)…-recovery.html Add this: innodb\_force\_recovery = 1 (you can start from 1 and change it to 6 if needed; this is well described in the URL below) To your MySQL config (my.cnf) and restart MySQL. Check MySQL error log for details. If the culprit is data corruption then after you’ll solve it you should be able to backup your data. Please check and let us to know. ---
**Author:** ![Pankaj\_Joshi](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@Pankaj\_Joshi](https://forums.percona.com/u/Pankaj_Joshi)\ **Post date:** [January 9, 2014, 6:32am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/9 "2014-01-09T06:32:55Z")
Hello Mixa thanks for looking into this, I am running the script now and will share the findings . I am using MySQL version 5.5.34-log so the query which you mentioned is not able to run . select i.index\_id, i.name, t.table\_id, t.schema, t.name from innodb\_sys\_indexes i left join innodb\_sys\_tables t on i.table\_id = t.table\_id where index\_id=55 any alternate query which could get the expected results from above mentioned query. ---
**Author:** ![mixa](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mixa/32/16881_2.png) [@mixa](https://forums.percona.com/u/mixa)\ **Post date:** [January 9, 2014, 8:31am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/10 "2014-01-09T08:31:59Z")
Can you please try this one? My mistake I didn’t add database name here… Or run “use mysql;” command before running te previous one. The point here - it gets data from tables from database with name “mysql” select i.index\_id, i.name, t.table\_id, t.schema, t.name from mysql.innodb\_sys\_indexes i left join mysql.innodb\_sys\_tables t on i.table\_id = t.table\_id where index\_id=55 ---
**Author:** ![Pankaj\_Joshi](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@Pankaj\_Joshi](https://forums.percona.com/u/Pankaj_Joshi)\ **Post date:** [January 9, 2014, 9:45am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/11 "2014-01-09T09:45:06Z")
select i.index\_id, i.name, t.table\_id, t.schema, t.name from mysql.innodb\_sys\_indexes i left join mysql.innodb\_sys\_tables t on i.table\_id = t.table\_id where index\_id=55 it gives me this error Table ‘mysql.innodb\_sys\_indexes’ doesn’t exist . Please note I am using MySQL version 5.5.34-log I also ran the script which you sent . this is the final output ./ibd\_checksum.sh \> idb\_checksum.log page 0 invalid (fails log sequence number check) please note we are using compression for tables . I am attaching the complete log as well. [idb\_checksum\_test.txt](https://forums.percona.com/uploads/short-url/yr0sHFFyj70vLEuzl00sfauFAJ5.txt) (12.1 KB) ---
**Author:** ![Pankaj\_Joshi](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@Pankaj\_Joshi](https://forums.percona.com/u/Pankaj_Joshi)\ **Post date:** [January 12, 2014, 10:50pm UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/12 "2014-01-12T22:50:53Z")
Hello mixa/mirfan can you please look into this and let me know if I can provide any information to be able to fix this issue . thanks in advance. ---
**Author:** ![Pankaj\_Joshi](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@Pankaj\_Joshi](https://forums.percona.com/u/Pankaj_Joshi)\ **Post date:** [January 15, 2014, 9:50am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/13 "2014-01-15T09:50:46Z")
Hello Percona Team. I upgraded MySQL 5.5.34 to 5.6.11 and was able to take the backup and prepare it successfully with xtrabackup\_56 version 2.1.5 . Thank you for all your support really appreciate it. ---
**Author:** ![mixa](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mixa/32/16881_2.png) [@mixa](https://forums.percona.com/u/mixa)\ **Post date:** [January 18, 2014, 3:11am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/14 "2014-01-18T03:11:36Z")
Hi Pankaj, Glad that it worked for you. Can you please try to restore backup on some test environment? Just to be sure that it works and not corrupted or something… ---
**Author:** ![Pankaj\_Joshi](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@Pankaj\_Joshi](https://forums.percona.com/u/Pankaj_Joshi)\ **Post date:** [February 13, 2014, 6:22am UTC](https://forums.percona.com/t/innobackupex-apply-log-error-for-fullbackup/3168/15 "2014-02-13T06:22:59Z")
Hello Mixa, Aplogies for delayed response , I restored backup on a server by manually copying the backup directory to another server and it worked. infact I set a new slave by taking backup of existing slave . Thanks Pankaj