percona-xtrabackup-80 does not work with mysql 8.0.20

Hello all, 

percona-xtrabackup-80 does not work with latest mysql server. 
Error is below: 

xtrabackup: recognized server arguments: --datadir=/var/lib/mysql --innodb_buffer_pool_size=240G --innodb_log_file_size=1G --server-id=67
xtrabackup: recognized client arguments: --socket=/var/run/mysqld/mysqld.sock --password=* --backup=1 --stream=xbstream --slave-info=1 --safe-slave-backup=1 --parallel=2
xtrabackup version 8.0.11 based on MySQL server 8.0.18 Linux (x86_64) (revision id: 486c270)
200428 11:23:03 version_check Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup;mysql_socket=/var/run/mysqld/mysqld.sock' (using password: YES).
200428 11:23:03 version_check Connected to MySQL server
200428 11:23:03 version_check Executing a version check against the server...
200428 11:23:03 version_check Done.
200428 11:23:03 Connecting to MySQL server host: localhost, user: not set, password: set, port: not set, socket: /var/run/mysqld/mysqld.sock
Using server version 8.0.20
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: open files limit requested 0, set to 1024
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = .
xtrabackup: innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 1073741824
Number of pools: 1
200428 11:23:03 Connecting to MySQL server host: localhost, user: not set, password: set, port: not set, socket: /var/run/mysqld/mysqld.sock
Unknown redo log format (4). Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/ upgrading-downgrading.html.
xtrabackup: Error: recv_find_max_checkpoint() failed.

Part from change notes (https://docs.oracle.com/cd/E17952_01/mysql-8.0-relnotes-en/news-8-0-20.html) that possibly is related to the issue:

InnoDB: Redo log records for modifications to undo tablespaces increased in size in MySQL 8.0 due to a change in undo tablespace ID values, which required additional bytes. The change in redo log record size caused a performance regression in workloads with heavy write I/O. To address this issue, the redo log format was modified to reduce redo log record size for modifications to undo tablespaces. (Bug #29536710)

Thanks