MySQL xtrabackup Backup failed record

Received an alarm, a port backup failed, view the backup log as follows, showing the backup interrupt caused by the DDL operation, view the binary log at that time, then executed a SQL statement to add a field. Currently, you can only re-perform the backup and modify the backup time to avoid a similar situation.

mysql:5.7.11

xtrabackup:2.4.5

Find the official fix bug situation:

Running DDL Statements on Percona Server 5.7 During the backup process could in some cases leads to failure while preparing the backup. Fixed #1555626 Bug.

MySQL5.7 can sometimes skip redo logging when creating an index. If suchALTER TABLEis being issued during the backup, the backup would be inconsistent.XtrabackupWould now abort with error message if suchALTER TABLEHave been done during the backup. Bug fixed#1582345.

So it's normal to try to avoid executing these SQL at backup time

BACKUP LOG:

innodb: last flushed lsn: 340748764928 load_index lsn 340748904772#  A DDL operation has been performed (redo logs are not logged). The affected rows may not have landed, PXB cannot ensure the consistency of the backup, please retry [fatal] innodb: an optimized (without redo logging)   Ddloperation has been performed. all modified pages may not have  been flushed to the disk yet.    pxb will not  be able take a consistent backup. Retry the backup  operation    #  Assertion Failure 2017-06-01 08:43:19 0x7f396ee27700  innodb:  Assertion failure in thread 139884650198784 in file ut0ut.cc  line 916#  intentionally generates a memory trap that interrupts the backup 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, eveninnodb:  Immediately after the mysqld startup, there may beinnodb: corruption  in the innodb tablespace. please refer toinnodb: http://dev.mysql.com /doc/refman/5.7/en/forcing-innodb-recovery.htmlinnodb: about forcing recovery.00:43:19 utc  - xtrabackup got signal 6 ; this could be because you hit a bug or data is  Corrupted. This error can also be caused by malfunctioning hardware. attempting to collect some information that could help diagnose  The problem. As this is a crash and something is definitely wrong, the  informationcollection process might fail. thread pointer: 0x0attempting backtrace. you can use the following  information to find outwhere mysqld died. if you see no  messages after this, something wentterribly wrong...stack_bottom = 0  Thread_stack 0x10000/usr/local/xtrabackup/bin/innobackupex (my_print_stacktrace+0x35) [0xd55c45]/usr/local/ Xtrabackup/bin/innobackupex (handle_fatal_signal+0x273) [0xb0d5a3]/lib64/libpthread.so.0[0x36ac20f710]/lib64/ Libc.so.6 (gsignal+0x35) [0x36abe32625]/lib64/libc.so.6 (abort+0x175) [0x36abe33e05]/usr/local/xtrabackup/bin/ Innobackupex[0x7bfbe5]/usr/local/xtrabackup/bin/innobackupex (_ZN2IB5FATALD1EV+0XB3) [0x837743]/usr/local/ Xtrabackup/bin/innobackupex[0x8af4a1]/usr/local/xtrabackup/bin/innobackupex (_Z19recv_parse_log_recsm7store_tb+ 0X4DF) [0x8b20ef]/usr/local/xtrabackup/bin/innobackupex[0x763b60]/usr/local/xtrabackup/bin/innobackupex[ 0x764176]/usr/local/xtrabackup/bin/innobAckupex[0x764523]/lib64/libpthread.so.0[0x36ac2079d1]/lib64/libc.so.6 (clone+0x6d) [0x36abee88fd]Please  Report a bug at https://bugs.launchpad.net/percona-xtrabackup

This article is from the "Amnesiasun" blog, make sure to keep this source http://amnesiasun.blog.51cto.com/10965283/1931479

MySQL xtrabackup Backup failed record