Not the answer you need?
Register and ask your own question!

xb-mgr is failing to verify the backup after mysql upgrade

farhanafarhana EntrantInactive User Role Beginner
Hi Team,
We are using xtrabackup manager tool to take the backup of databases remotely. Recently, we had a minor upgrade of Mysql 5.5.23 to mysql 5.6.10 later i noticed xtrabackup is failing repeatedly. Backup is failing with the below error (Seems like backup is Ok but the verification is failing)

shine01.log
[ERROR] MySQL daemon failed to start or exited, check /root/shine01/prepare/mysqld_verify.log for details.

I could see the below information under verify.log
mysqld_verify.log

InnoDB: Page may be a transaction system page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 5.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
160307 4:45:36 InnoDB: Assertion failure in thread 140153916659648 in file buf0buf.c line 4004
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
04:45:36 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/



I also ran the xtrabackup in localhost, there its working fine.Could anyone please suggest me a way to take my database backup remotely.

Thanks
Farhana Mohammed

Comments

  • mirfanmirfan Database Administrator Inactive User Role Beginner
    What exact xtrabackup version you used ? Can you show us the exact commands used for backup.
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.