通过xtrabackup2.3.9恢复mysql5.6.48出现的报错现象

系统环境：

centos7.7
mysql5.6.48
xtrabackup2.3.9

恢复过程

[root@lineqi ~]# innobackupex --user=root --port=13306 --password=234 --apply-log --redo-only /data/xtrabackup/2020-05-27/
200528 22:19:11 innobackupex: Starting the apply-log operation

IMPORTANT: Please check that the apply-log run completes successfully.
At the end of a successful apply-log run innobackupex
prints “completed OK!”.

innobackupex version 2.3.9 based on MySQL server 5.6.24 Linux (x86_64) (revision id: fde0e3e)
xtrabackup: cd to /data/xtrabackup/2020-05-27/
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(1657770)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:200M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:200M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Memory barrier is not used
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: The log sequence numbers 1626007 and 1626007 in ibdata files do not match the log sequence number 1657770 in the ib_logfiles!
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files…
InnoDB: Restoring possible half-written data pages
InnoDB: from the doublewrite buffer…
xtrabackup: Last MySQL binlog file position 1544, file name mysql-bin.000005

xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: Starting shutdown…
InnoDB: Shutdown completed; log sequence number 1657770
200528 22:19:13 completed OK!

[root@lineqi ~]# innobackupex --defaults-file=/etc/my13306.cnf --copy-back /data/mysqlbackup/xtrabackup/2020-05-27
200528 22:29:01 innobackupex: Starting the copy-back operation

IMPORTANT: Please check that the copy-back run completes successfully.
At the end of a successful copy-back run innobackupex
prints “completed OK!”.

innobackupex version 2.3.9 based on MySQL server 5.6.24 Linux (x86_64) (revision id: fde0e3e)
200528 22:29:01 [01] Copying ibdata1 to /data/mysql_13306/data/ibdata1
200528 22:29:07 [01] …done
200528 22:29:07 [01] Copying ./backup.log to /data/mysql_13306/data/backup.log
200528 22:29:07 [01] …done
200528 22:29:07 [01] Copying ./mysql/innodb_table_stats.ibd to /data/mysql_13306/data/mysql/innodb_table_stats.ibd
…………………………
200528 22:29:09 [01] …done
200528 22:29:09 [01] Copying ./xtrabackup_info to /data/mysql_13306/data/xtrabackup_info
200528 22:29:09 [01] …done
200528 22:29:09 completed OK!

[root@lineqi ~]# mkdir /data/mysql_13306/{logs,tmp}
[root@lineqi ~]# chown -R mysql:mysql /data/mysql_13306
启动成功，但数据库后台日志有错误信息
InnoDB:
http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2020-05-28 22:54:57 7fa72adbc700 InnoDB: Error: page 3 log sequence number 1655896
InnoDB: is in the future! Current system log sequence number 1626144.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2020-05-28 22:54:57 7fa72adbc700 InnoDB: Error: page 308 log sequence number 1649493
InnoDB: is in the future! Current system log sequence number 1626144.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2020-05-28 22:54:57 7fa72adbc700 InnoDB: Error: page 307 log sequence number 1649445
InnoDB: is in the future! Current system log sequence number 1626144.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2020-05-28 22:54:57 7fa7dbcc8780 InnoDB: Error: page 0 log sequence number 1656770
InnoDB: is in the future! Current system log sequence number 1626144.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2020-05-28 22:54:57 3569 [Note] InnoDB: 5.6.48 started; log sequence number 1626134
2020-05-28 22:54:57 3569 [Note] RSA private key file not found: /data/mysql_13306/data//private_key.pem. Some authentication plugins will not work.
2020-05-28 22:54:57 3569 [Note] RSA public key file not found: /data/mysql_13306/data//public_key.pem. Some authentication plugins will not work.
2020-05-28 22:54:57 3569 [Note] Server hostname (bind-address): ‘*’; port: 13306
2020-05-28 22:54:57 3569 [Note] IPv6 is available.
2020-05-28 22:54:57 3569 [Note] - ‘::’ resolves to ‘::’;
2020-05-28 22:54:57 3569 [Note] Server socket created on IP: ‘::’.
2020-05-28 22:54:57 3569 [Warning] ‘user’ entry ‘root@lineqi’ ignored in --skip-name-resolve mode.
2020-05-28 22:54:57 3569 [Warning] ‘user’ entry ‘@lineqi’ ignored in --skip-name-resolve mode.
2020-05-28 22:54:57 3569 [Warning] ‘proxies_priv’ entry ‘@ root@lineqi’ ignored in --skip-name-resolve mode.
2020-05-28 22:54:57 3569 [Note] Event Scheduler: Loaded 0 events
2020-05-28 22:54:57 3569 [Note] mysqld: ready for connections.
Version: ‘5.6.48-log’ socket: ‘/data/mysql_13306/mysql.sock’ port: 13306 MySQL Community Server (GPL)