# Crash on prepare partitial backup **URL:** \ **Category:** Percona XtraBackup\ **Created:** [June 23, 2014, 2:27am UTC](https://forums.percona.com/t/crash-on-prepare-partitial-backup/3563 "2014-06-23T02:27:03Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![salos](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@salos](https://forums.percona.com/u/salos)\ **Post date:** [June 23, 2014, 2:27am UTC](https://forums.percona.com/t/crash-on-prepare-partitial-backup/3563/1 "2014-06-23T02:27:03Z")
I’m trying to prepare my backup to restore on another server and I have InnoDB: End of page dump 2014-06-23 06:36:45 7f40e17c3700 InnoDB: uncompressed page, stored checksum in field1 3735928559, calculated checksums for field1: crc32 177807968, innodb 3475755373, none 3735928559, stored checksum in field2 3735928559, calculated checksums for field2: crc32 177807968, innodb 1624572976, none 3735928559, page LSN 0 0, low 4 bytes of LSN at page end 0, page number (if stored to page already) 0, space id (if created with \>= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be a freshly allocated page 2014-06-23 06:36:45 7f40e17c3700 InnoDB: Assertion failure in thread 139916637648640 in file rem0rec.cc line 577 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: [http://dev.mysql.com/doc/refman/5.6/](http://dev.mysql.com/doc/refman/5.6/)…-recovery.html InnoDB: about forcing recovery. Aborted innobackupex: Error: innobackupex: ibbackup failed at /usr/bin/innobackupex line 2610. If I try to restore it by table it also error Internal error: Cannot reset LSNs in table ‘“hero\_db”.“map\_save”’ : Data structure corruption \*/ It seems that is because there are no exp file. command for prepare innobackupex --apply-log --export /var/mysql-backup/2014-06-20\_10-00-01 command for create backup innobackupex --user= --password= --compact --databases=“hero\_db” /var/mysql-backup Probably it is because we use COMPRESSED tables