Not the answer you need?
Register and ask your own question!

Xtrabackup 8.0.11 and MySQL 8.0.20: xtrabackup: Error: recv_find_max_checkpoint() failed.

SujitRSujitR Current User Role Contributor
I'm using Xtrabackup 8.0.11 and MySQL 8.0.20 and when I execute the following code line:
sudo xtrabackup --backup -uxxxx -p --socket=/mysqldata/mysql.sock --history --compress --slave-info --compress-threads=10 --target-dir=/xtrabackup
I am getting following Result---:
00:00:03 Using server version 8.0.20
00:00:03 xtrabackup: uses posix_fadvise().
00:00:03 xtrabackup: cd to /mysqldata
00:00:03 xtrabackup: open files limit requested 65535, set to 65535
00:00:03 xtrabackup: using the following InnoDB configuration:
00:00:03 xtrabackup:   innodb_data_home_dir = .
00:00:03 xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
00:00:03 xtrabackup:   innodb_log_group_home_dir = ./
00:00:03 xtrabackup:   innodb_log_files_in_group = 2
00:00:03 xtrabackup:   innodb_log_file_size = 2147483648
00:00:03 Number of pools: 1
00:00:03 200428 00:00:03 Connecting to MySQL server host: localhost, user: sqladmin, password: set, port: not set, socket: /mysqldata/mysql.sock
00:00:03 Unknown redo log format (4). Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/ upgrading-downgrading.html.
00:00:03 xtrabackup: Error: recv_find_max_checkpoint() failed.


As I checked in MySQL 8.0.20 release (release date 24-April-2020)
 MySql has some changes in the redo log format.
How I can resolve this now. 

Comments

  • lorraine.pocklingtonlorraine.pocklington Percona Community Manager Legacy User Role Patron
    Can I check if this is a script that you were successfully using before upgrading software? If that's the case, what have you gone from and to? I'm checking in with the team, but a few more details could help. Is it a production environment? What OS are you running, please? 
  • lorraine.pocklingtonlorraine.pocklington Percona Community Manager Legacy User Role Patron
    Hello again, I have an update. 
    The redo log format did indeed change in the latest MySQL version, and Percona XtraBackup will not be current with that until the next release. The only way to resolve the issue immediately would be to revert to 8.0.19 but that itself comes with some severe warnings, please read this blog post by my colleague Marco https://www.percona.com/blog/2020/01/10/mysql-8-minor-version-upgrades-are-one-way-only/
  • SujitRSujitR Current User Role Contributor
    edited April 28
    @lorraine
    1)Succesful backup with MySQL8.0.19(27-April-2020) and Xtrabackup 8.0.11.
    sudo xtrabackup --backup -u xxxxx -p --socket=/mysqldata/mysql.sock --history --compress --slave-info --compress-threads=10 --target-dir=/xtrabackup


    00:00:02 Using server version 8.0.19
    00:00:02 xtrabackup: uses posix_fadvise().
    00:00:02 xtrabackup: cd to /mysqldata
    00:00:02 xtrabackup: open files limit requested 65535, set to 65535
    00:00:02 xtrabackup: using the following InnoDB configuration:
    00:00:02 xtrabackup:   innodb_data_home_dir = .
    00:00:02 xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
    00:00:02 xtrabackup:   innodb_log_group_home_dir = ./
    00:00:02 xtrabackup:   innodb_log_files_in_group = 2
    00:00:02 xtrabackup:   innodb_log_file_size = 2147483648
    00:00:02 Number of pools: 1
    00:00:02 200427 00:00:02 Connecting to MySQL server host: localhost, user: sqladmin, password: set, port: not set, socket: /mysqldata/mysql.sock
    00:00:02 200427 00:00:02 >> log scanned up to (5983781423982)
    00:00:02 xtrabackup: Redo Log Archiving is not set up.
    00:00:02 xtrabackup: Generating a list of tablespaces
    00:00:02 Directories to scan '.;./;.'


    2)Is this is Production env.
    3)Os Release 
    CentOS Linux release 7.8.2003 (Core)

Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.