InnoDB: Unsupported redo log format.

I’m trying to use xtrabackup-v2 in a galera cluster, this is what innobackup.backup.log gives me when a peer tries to join. The host is just an new mariaDB server with only an extra user to give xtrabackup access:

180206 20:26:40 innobackupex: Starting the backup operation

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

180206 20:26:40 Connecting to MySQL server host: localhost, user: xtrabackup, password: set, port: not set, socket: /var/lib/mysql/mysql.sock
Using server version 10.3.4-MariaDB
innobackupex version 2.4.9 based on MySQL server 5.7.13 Linux (x86_64) (revision id: a467167cdd4)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql/
xtrabackup: open files limit requested 0, set to 16364
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 = 209715200
InnoDB: Number of pools: 1
InnoDB: Unsupported redo log format. The redo log was created with MariaDB 10.3.4. Please follow the instructions at http://dev.mysql.com/doc/refman/5.7/en/upgrading-downgrading.html

Since everything is a clean install, I have no clue what is going on, the mariadb server on the joiner doesn’t start, I almost started thinking that the packages I use are too new?

Hi MrMoronIV ,

Have you tried using MariaDB Backup instead of PXB for your MDB 10.3 Galera cluster? It appears that the redo log format of 10.3 may have sufficiently diverged from upstream MySQL to no longer be compatible.
https://mariadb.com/kb/en/library/mariadb-backup-overview/