To back up database data using the INNOBACKUPEX command error message The log file size is inconsistent with the settings in the configuration file workaround

Problem Description:

The following error is prompted when backing up the MARIADB database using the Xtrabackup tool:

InnoDB:Error:log file./ib_logfile0 is of different size 5242880 Bytesinnodb:than specified in the. cnf file 50331648 b Ytes!innobackupex:error:the Xtrabackup child process had died At/usr/bin/innobackupex line 2672.

The database is installed in a common binary format, and the configuration file is the my-large.cnf file in the replicated Support-files directory.

The default innodb_log_file_size size in this profile is 64M, and other types of profiles are different, while there are two ib_logfile in the database data directory, IB_LOGFILE0 and Ib_logfile1, The size of the two file is 5M:

[Email protected] data]# LS-LH ib_logfile0 IB_LOGFILE1-RW-RW----1 Nobody nobody 5.0M Sep 9 00:29 IB_LOGFILE0-RW-RW---- 1 Nobody nobody 5.0M Sep 9 00:29 ib_logfile1

Workaround:

The log file can be rebuilt by backing up the log and removing the log in the data directory, but in order to avoid the hassle of recovering data later, instead of deleting the files in the data directory, the Innodb_log_file_size parameter is set to 5 m in the configuration file, which is not enabled by default. Although not enabled, there is a default value, but the default value is inconsistent with the actual ib_logfile numeric size, causing the Innobackupex command to check for inconsistencies in the setting of these parameters during execution and to abort the backup process. After modifying the configuration file after the parameter is 5M, then perform the backup operation will be smooth.

To back up database data using the INNOBACKUPEX command error message The log file size is inconsistent with the settings in the configuration file workaround