MariaDB backup issue

Hi All,

MariaDB 10.3 doesn’t work with percona-xtrabackup24

]# /usr/local/share/urbackup/scripts/mariadbxtrabackup > /dev/null
2019-09-11 19:17:00 0 [Note] Plugin ‘FEEDBACK’ is disabled.
Starting binary backup of MariaDB at Wed Sep 11 19:17:00 MSK 2019…
xtrabackup: recognized server arguments:
xtrabackup: recognized client arguments: --backup=1 --stream=tar --extra-lsndir=/var/lib/mariadbbackup/last.new --user=root --password=*
190911 19:17:01 version_check Connecting to MySQL server with DSN ‘dbi:mysql:;mysql_read_default_group=xtrabackup’ as ‘root’ (using password: YES).
190911 19:17:01 version_check Connected to MySQL server
190911 19:17:01 version_check Executing a version check against the server…
190911 19:17:01 version_check Done.
190911 19:17:01 Connecting to MySQL server host: localhost, user: root, password: set, port: not set, socket: not set
Using server version 10.3.15-MariaDB
xtrabackup version 2.4.15 based on MySQL server 5.7.19 Linux (x86_64) (revision id: 544842a)
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.15. Please follow the instructions at http://dev.mysql.com/doc/refman/5.7/en/upgrading-downgrading.html

Can I use mariabackup instead?
Edit line of
/usr/local/share/urbackup/scripts/mariadbxtrabackup
to

mariabackup --backup --stream=xbstream --extra-lsndir="$MARIADB_TEMP_INCRDIR/last.new" --user="$MARIADB_USER" --password="$MARIADB_PASSWORD" $COMPACT

As far as I understand I should edit also file:
/usr/local/share/urbackup/scripts/restore-mariadbbackup

All, What you think about it?

So, the problem could be that UrBackup actually reads the tar output, then stores the streamed backup as files.

The xbstream format seems somewhat similar to tar, but is obviously not compatible. I also couldn’t find any documentation about that format.

Thank you for reply, the main problem that mariabackup doesn’t support tar format.
I’ve looked on percona-xtrabackup-80, it seems that it support only xbstream format too and doesn’t support tar format too.
A couple years ago, I read that MariaDB 10.3 have some compatibility issues with percona-xtrabackup-24. It was the reason to migrate to mariabackup. As far as I understand, mariabackup is fork of percona-xtrabackup

May be this link will be helpful:
https://www.percona.com/doc/percona-xtrabackup/2.3/xbstream/xbstream.html

As far as I understand tar support stream was removed about one year ago from mariabackup, and it seems that percona-xtrabackup will do tha same (or done already like pecrona-xtrabackup-80)

https://www.percona.com/doc/percona-xtrabackup/8.0/xtrabackup_bin/xbk_option_reference.html says it is supported.

It seems, they have no time to upgrade manual and this is very strange:

/usr/local/share/urbackup/scripts/mariadbxtrabackup > /dev/null
2019-09-15 17:41:54 0 [Note] Plugin ‘FEEDBACK’ is disabled.
Starting binary backup of MariaDB at Sun Sep 15 17:41:54 MSK 2019…
Invalid --stream argument: tar

mysql -V
mysql Ver 15.1 Distrib 10.3.15-MariaDB, for Linux (x86_64) using readline 5.1

yum list installed | grep percona
percona-release.noarch 1.0-13 installed
percona-xtrabackup-80.x86_64 8.0.6-1.el7 @percona-release-x86_64

which xtrabackup
/usr/bin/xtrabackup

line from the script:
xtrabackup --backup --stream=tar --extra-lsndir="$MARIADB_TEMP_INCRDIR/last.new" --user="$MARIADB_USER" --password="$MARIADB_PASSWORD" $COMPACT

Finally found:
https://jira.percona.com/browse/PXB-1707?focusedCommentId=231555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-231555

So, I think we need to play around mariabackup+xbstream in the nearest future:

https://jira.percona.com/browse/PXB-1550

Could you retry the mysql tar backup with this version http://beta.urbackup.org/tmp/UrBackupUpdateLinux(15).sh and send me the client log file if the backup still doesn’t work?

Let me try right now

System confiuration:

  • Client CentOS release 6.8 (Final)
  • urbackup verson fro link:
    http://beta.urbackup.org/tmp/UrBackupUpdateLinux(15).sh
  • mysql Ver 15.1 Distrib 10.1.16-MariaDB, for Linux (x86_64) using readline 5.1
  • percona-xtrabackup-24.x86_64 2.4.15-1.el6
  • mariadbxtrabackup enabled
  • trying incr backup (Internet mode)
  • Urbackup server: 2.3.7.0.r1 (NAS Asustor 1002t)

Installaton log:

Verifying archive integrity... All good.
Uncompressing UrBackup Client Installer for Linux  100%
Installation of UrBackup Client 2.4.7 beta to /usr/local ... Proceed ? [Y/n]
Y
Uncompressing install data...
Assuming RedHat (derivative) system
Detected architecture x86_64-linux-glibc
(Glibc not installed or too old. Falling back to Android NDK build...)
Installing System V init script...
Restarting UrBackup Client service...
Restarting UrBackup Client Daemon urbackupclientbackendShut[  OK  ]n UrBackup client:
Starting UrBackup client:                                  [  OK  ]
Successfully started client service. Installation complete.

Unfortunately, backup failed. Will send fresh logs to the email.

Shortly, a couple errors around:

Client calculated hash of … differs from server calculated hash. This may be caused by a bug or by random bit flips on the client or server hard disk. Failing backup

Sorry, still haven’t found the cause. I added more debug info to http://beta.urbackup.org/tmp/UrBackupUpdateLinux(16).sh , so if possible retry with that and send the logs… thanks!

Hi,

No problems, already in the progress. Will send you logs.