# Impossible to install on Debian buster with its MariaDB version 10.3

**URL:** <https://forums.percona.com/t/impossible-to-install-on-debian-buster-with-its-mariadb-version-10-3/10641>\
**Category:** Percona XtraBackup\
**Created:** [May 31, 2021, 11:27am UTC](https://forums.percona.com/t/impossible-to-install-on-debian-buster-with-its-mariadb-version-10-3/10641 "2021-05-31T11:27:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![szepeviktor](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/szepeviktor/32/3631_2.png) [@szepeviktor](https://forums.percona.com/u/szepeviktor)\
**Post date:** [May 31, 2021, 11:27am UTC](https://forums.percona.com/t/impossible-to-install-on-debian-buster-with-its-mariadb-version-10-3/10641/1 "2021-05-31T11:27:33Z")

</div>

Hello! Thank you for the backup tools!

Debian buster comes with MariaDB 10.3. Percona XtraBackup for buster are versions 2.4 and 8.0.  
**None** of them are compatible with MariaDB 10.3.

Please advise. I’m a Debian user.

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [May 31, 2021, 2:28pm UTC](https://forums.percona.com/t/impossible-to-install-on-debian-buster-with-its-mariadb-version-10-3/10641/2 "2021-05-31T14:28:34Z")

</div>

What happens when you try PXB on your Maria setup? Errors? What are they?

---

<div class="post-metadata">

**Author:** ![szepeviktor](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/szepeviktor/32/3631_2.png) [@szepeviktor](https://forums.percona.com/u/szepeviktor)\
**Post date:** [May 31, 2021, 2:55pm UTC](https://forums.percona.com/t/impossible-to-install-on-debian-buster-with-its-mariadb-version-10-3/10641/3 "2021-05-31T14:55:46Z")

</div>

Thank you very much for your response.

> InnoDB: Unsupported redo log format. The redo log was created with MariaDB 10.3.27.

```auto
# xtrabackup --backup --throttle=100 --target-dir=/media/server-backup.s3ql/innodb
xtrabackup: recognized server arguments: --datadir=/var/lib/mysql --tmpdir=/tmp
xtrabackup: recognized client arguments: --socket=/var/run/mysqld/mysqld.sock --backup=1 --throttle=100 --target-dir=/media/server-backup.s3ql/innodb
210531 14:53:59 version_check Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup;mysql_socket=/var/run/mysqld/mysqld.sock' (using password: NO).
210531 14:53:59 version_check Connected to MySQL server
210531 14:53:59 version_check Executing a version check against the server...
210531 14:53:59 version_check Done.
210531 14:53:59 Connecting to MySQL server host: localhost, user: not set, password: not set, port: not set, socket: /var/run/mysqld/mysqld.sock
Using server version 10.3.27-MariaDB-0+deb10u1
xtrabackup version 2.4.22 based on MySQL server 5.7.32 Linux (x86_64) (revision id: c99a781)
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 = 50331648
InnoDB: Number of pools: 1
InnoDB: Unsupported redo log format. The redo log was created with MariaDB 10.3.27. Please follow the instructions at http://dev.mysql.com/doc/refman/5.7/en/upgrading-downgrading.html

```

Found that log format diverged from MySQL: [InnoDB: Unsupported redo log format. - #2 by Michael\_Coburn](https://forums.percona.com/t/innodb-unsupported-redo-log-format/6176/2)

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [May 31, 2021, 3:48pm UTC](https://forums.percona.com/t/impossible-to-install-on-debian-buster-with-its-mariadb-version-10-3/10641/4 "2021-05-31T15:48:52Z")

</div>

Ah yes. I initially thought it was a MariaDB issue but didn’t want to jump to that conclusion. Yes, MariaDB is a fork of MySQL and they have their own ways of doing things that are not 100% compatible with Community/Percona.

---

<div class="post-metadata">

**Author:** ![szepeviktor](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/szepeviktor/32/3631_2.png) [@szepeviktor](https://forums.percona.com/u/szepeviktor)\
**Post date:** [May 31, 2021, 4:48pm UTC](https://forums.percona.com/t/impossible-to-install-on-debian-buster-with-its-mariadb-version-10-3/10641/5 "2021-05-31T16:48:57Z")

</div>

It turns out MariaDB forked Percona XtraBackup!

> **[Mariabackup Overview](https://mariadb.com/kb/en/mariabackup-overview/)**
>
> The Mariabackup utility performs physical backups and supports Data-at-Rest Encryption and InnoDB Page Compression.

In my case it needed 2 extra switches.

```bash
mariabackup --socket=/var/run/mysqld/mysqld.sock --user=root

```