OurMySQL BackupSevere System ProblemsBug
Originated fromOpen SourceSoftware XtrabackupA bug
Https://bugs.launchpad.net/percona-xtrabackup/+bug/722638
We have not encountered this problem before large-scale deployment.
After converting the counter to MySQL, we deployed the backup system, which often failed to be backed up, so we decided to completely solve this problem,
After a series of tests, it is found that the data warehouse receiving operations across counters cannot be performed during the backup process,
Backup System Error:
[Code]
[01] copying./cnt_it/cnt_referrer_channel_2011.ibd
To/usr/local/MySQL/crontab/cnt_it/backup/InnoDB/full/2011-06-10_18-18-25/cnt_it/cnt_referrer_channel_2011.ibd
[01]... Done
[01] copying./cnt_it/cnt_goals_abandon_201109.ibd
To/usr/local/MySQL/crontab/cnt_it/backup/InnoDB/full/2011-06-10_18-18-25/cnt_it/cnt_goals_abandon_201109.ibd
[01]... Done
[01] copying./cnt_it/cnt_referrer_search_keyword_201107.ibd InnoDB: Error: tablespace ID is 43167 inDataDictionary
InnoDB: But in file./cnt_it/cnt_referrer_summary_work.ibd it is 43178!
110610
18:37:57 InnoDB: assertion failure in thread 1201920320 in file
/Home/buildbot/slaves/percona-server-51-12/tgz_centos_5_x86_64/work/xtrabackup-1.6/Percona-Server-5.5/storage/Innobase/FIL/fil0fil. c
Line 780
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: Snapshot uption In the InnoDB tablespace. Please refer
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
To/usr/local/MySQL/crontab/cnt_it/backup/InnoDB/full/2011-06-10_18-18-25/cnt_it/cnt_referrer_search_keyword_201107.ibd
[01]... Done
[01] copying./cnt_it/cnt_goals_referrer_201205.ibd
To/usr/local/MySQL/crontab/cnt_it/backup/InnoDB/full/2011-06-10_18-18-25/cnt_it/cnt_goals_referrer_201205.ibd
[01]... Done
./Backup. sh: line 109: 24002 backup failed xtrabackup
-- Defaults-file = $ CNF -- backup -- target-Dir = $ backup/$ engine/full/$ day
-- Datadir = $ datadir
+ Return 1
+ Critical
+ DF-H
[/Code]
What is the problem above?
That is to say, during the backup process,DatabaseThe table cannot be rebuilt, such as truncate table, drop table, and re-create a table.
The error message indicates that xtrabackup has taken this issue into consideration, but it was not handled at the time. Therefore, an assertion is added to the relevant code.
If an error occurs in the code, exit.
This bug exists in versions 1.5, 1.5.1, and 1.6. It cannot be repaired until version 1.7.
Wait!
Currently, the backup slave database is used as an alternative.