Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

A brief Analysis of the methods to solve the failure of xtrabackup backup in MySQL

2025-04-08 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)06/01 Report--

This article mainly introduces the methods to solve the failure of MySQL backup using xtrabackup. The content of the article is carefully selected and edited by the author. It has a certain pertinence and is of great significance to everyone. Let's learn about the next topic with the author.

After receiving the alarm, a port backup failed. Check the backup log below to show the backup interruption caused by the DDL operation. View the binary log at that time, and execute a sql statement to add fields. 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 repair of bug:

Running DDL statements on Percona Server 5.7 during the backup process could in some cases lead to failure while preparing the backup. Bug fixed # 1555626.

MySQL 5.7 can sometimes skip redo logging when creating an index. If such ALTER TABLE is being issued during the backup, the backup would be inconsistent. Xtrabackup will now abort with error message if such ALTER TABLEhas been done during the backup. Bug fixed # 1582345.

Therefore, this situation is normal, and we should try our best to avoid performing these sql during backup.

Back up the log:

InnoDB: Last flushed lsn: 340748764928 load_index lsn 34074890477A DDL operation has been performed (no redo log has been recorded). The affected line may not have landed, and PXB cannot guarantee the consistency of the backup. Please try [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 failed 2017-06-01 08:43:19 0x7f396ee27700 InnoDB: Assertion failure in thread 139884650198784 in file ut0ut.cc line 9 deliberately generated a memory trap to interrupt 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

After reading the above brief analysis of the methods to solve the failure of MySQL using xtrabackup backup, many readers must have some understanding. If you need to get more industry knowledge and information, you can continue to follow our industry information column.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 206

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report