# Xtrabackup broken with MariaDB Galera Cluster

**URL:** <https://forums.percona.com/t/xtrabackup-broken-with-mariadb-galera-cluster/4567>\
**Category:** Percona XtraBackup\
**Created:** [December 4, 2015, 7:06am UTC](https://forums.percona.com/t/xtrabackup-broken-with-mariadb-galera-cluster/4567 "2015-12-04T07:06:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chstehl](https://avatars.discourse-cdn.com/v4/letter/c/ba9def/32.png) [@chstehl](https://forums.percona.com/u/chstehl)\
**Post date:** [December 4, 2015, 7:06am UTC](https://forums.percona.com/t/xtrabackup-broken-with-mariadb-galera-cluster/4567/1 "2015-12-04T07:06:46Z")

</div>

Hi there,

with the update to XtraBackup 2.3, the SST-Method xtrabackup-v2 is not working anymore with our MariaDB Galera Cluster 10.  
Also Innobackupex is terminating with errors. After rollback to xtrabackup 2.2 everything runs fine again.  
Is there a solution for this available?  
MariaDB Galera Server 10.0.21 on centos7, WSREP Provider 25.3.9(r3387)

Christian

---

<div class="post-metadata">

**Author:** ![Denis](https://avatars.discourse-cdn.com/v4/letter/d/5e9695/32.png) [@Denis](https://forums.percona.com/u/Denis)\
**Post date:** [December 16, 2015, 10:53am UTC](https://forums.percona.com/t/xtrabackup-broken-with-mariadb-galera-cluster/4567/2 "2015-12-16T10:53:08Z")

</div>

## I also failed to use xtrabackup (2.3.2 ) to join a new node to a galera cluster( Server version: 10.0.21-MariaDB-wsrep-log MariaDB Server, wsrep\_25.10.r4144) with xtrabackup-v2 method. after I switch to the 2.2.13 version, no problem. When i check the donor log:

## 151216 6:33:58 [Note] WSREP: Running: 'wsrep\_sst\_xtrabackup-v2 --role ‘donor’ --address ‘10.74.3.195:4444/xtrabackup\_sst’ --auth ‘sst\_user: xxxx’ --socket ‘/home/mysql/db02/admin/mysql.sock’ --datadir ‘/home/mysql/db02/data/’ --defaults-file ‘/home/mysql/galera-10.0.21/my.cnf ’ --defaults-group-suffix ‘’ --binlog ‘/home/mysql/db02/binlogs/mysql\_db02-bin’ --gtid ‘5d57dce4-a28c-11e5-b74c-9a364e95fd0d:9’’ 151216 6:33:58 [Note] WSREP: sst\_donor\_thread signaled with 0 WSREP\_SST: [INFO] Streaming with xbstream (20151216 06:33:59.093) WSREP\_SST: [INFO] Using socat as streamer (20151216 06:33:59.095) WSREP\_SST: [INFO] Using /tmp/tmp.tXBdi22845 as innobackupex temporary directory (20151216 06:33:59.105) WSREP\_SST: [INFO] Streaming GTID file before SST (20151216 06:33:59.108) WSREP\_SST: [INFO] Streaming the backup to joiner at 10.74.3.195 4444 (20151216 06:34:09.119) WSREP\_SST: [INFO] Evaluating innobackupex --defaults-file=/home/mysql/galera-10.0.21/my.cnf --defaults-group=mysqld --no-version-check $tmp opts $INNOEXTRA --galera-info --stream=$sfmt $itmpdir 2\>${DATA}/innobackup.backup.log | socat -u stdio TCP:10.74.3.195:4444; RC=( ${PIPESTAT US[@]} ) (20151216 06:34:09.121) 151216 6:34:11 [Note] WSREP: Provider paused at 5d57dce4-a28c-11e5-b74c-9a364e95fd0d:9 (15) 151216 6:34:11 [Note] WSREP: resuming provider at 15 151216 6:34:11 [Note] WSREP: Provider resumed. WSREP\_SST: [ERROR] innobackupex finished with error: 1. Check /home/mysql/db02/data//innobackup.backup.log (20151216 06:34:11.522) WSREP\_SST: [ERROR] Cleanup after exit with status:22 (20151216 06:34:11.524)

when i check /home/mysql/db02/data//innobackup.backup.log, it has:

[00] error: cannot open file /home/mysql/db02/data//mysql\_db02-bin.000003

While the file mysql\_db02-bin.000003 is actually at /home/mysql/db02/binlogs/ . It looks to me in the 2.3 version , the default location of binlog used, even with --binlog '/home/mysql/db02/binlogs/mysql\_db02-bin used in wsrep\_sst\_xtrabackup-v2

Denis