can we use xtrabackup 2.4.20 to backup community edition of MYSQL 5.16 ?

MySQL & MariaDB Percona XtraBackup
1

can we use xtrabackup 2.4.20 to backup community edition of MYSQL 5.16 ?

during prepare phase getting error InnoDB: 5.7.26 started; log sequence number 16976204771688
InnoDB: Cannot add field `a_str_131` in table `DB123`.`task` because after adding it, the row size is 8166 which is greater than maximum allowed size (8126) for a record on index leaf page.

2

Do you mean MySQL version 5.7.16? In any case, Xtrabackup 2.4.20 should work with MySQL Community edition 5.7. If I understand correctly, this happens during prepare (restore). Please check and compare the configuration between source and destination instances (eg innodb_page_size, default character set, etc).Please provide full output of the table structure for DB123.task table.

3

Thanks for prompt response . We are using My SQL Server version: 5.6.16-log MySQL Community Server. Can we use Xtrabackup 2.4.20 to backup and restore MySQL 5.6.16?

While decompress we are getting

xtrabackup version 2.4.20 based on MySQL server 5.7.26 Linux (x86_64) (revision id: c8b4056)

200831 22:34:12 [01] decompressing ./xtrabackup_logfile.qp

200831 22:34:12 [02] decompressing ./mysql/innodb_index_stats.ibd.qp

200831 22:34:12 [03] decompressing ./mysql/slave_relay_log_info.ibd.qp

sh: qpress: command not found

4

You are missing the qpress package. If you are using CentOS/RHEL 7 you can download it here:

https://repo.percona.com/yum/release/centos/7/RPMS/x86_64/qpress-11-1.el7.x86_64.rpm

5

@jrivera Thanks for your response on decompressing

We are using My SQL Server version: 5.6.16 MySQL Community Server. Can we use Xtrabackup 2.4.20 to backup and restore MySQL 5.6.16? or do we need to install any older version of xtrabackup?

6

@jrivera Can we use Xtrabackup 2.4.20 to backup and restore MySQL 5.6.16  Thanks


7

Xtrabackup 2.4.20 should work, however, due to the version of MySQL being too old. It may be good to use Xtrabackup 2.3 instead. Are you backing up and restoring to the same MySQL version?

8

Thanks . We are backing up and restoring to same version of MySQL 5.6.16 . Which version of xtrabackup you 2.3 we need to down load ?

9

We generally recommend using the latest version available for PXB 2.3 series.

10

Can you please provide the link . Not able to find down load link for redhat 6.x

11

@jrivera can you please provide link to down load PXB2.3 fro backing up MySQL 5.6

12

@kduvvuri note that PXB 2.3 has already reached EOL. Can you try using Percona Xtrabackup 2.4 first and let us know if you encounter any issues?

13

@jrivera backup using version 2.4.20 worked  , backup detected MYSQL Using server version 5.6.16-log 

The prepare command was also success full , and got message InnoDB: 5.7.26 started; log sequence number 17226588601877

Are we good to use xtrabackup 2.4.20 for MySQL 5.6 ?

As per extra backup page

https://www.percona.com/doc/percona-xtrabackup/2.4/index.html here it says It can back up data from InnoDB, XtraDB, and MyISAM tables on MySQL 5.1 [1], 5.5, 5.6 and 5.7 servers, as well as Percona Server for MySQL with XtraDB

xtrabackup --defaults-extra-file=/glide/backup/xtrabkp/xbk.cnf --parallel=4 --backup --target-dir=/glide/backup/xtrabkp/bkp
200908 17:15:18  version_check Connecting to MySQL server with DSN'dbi:mysql:;mysql_read_default_group=xtrabackup;host=localhost;port=3306;mysql_socket=/tmp/mysql.sock' as 'root'  (using password: YES).
200908 17:15:18  version_check Connected to MySQL server
200908 17:15:18  version_check Executing a version check against the server...
200908 17:15:18  version_check Done.
200908 17:15:18 Connecting to MySQL server host: localhost, user: root, password: set, port: 3306, socket: /tmp/mysql.sock
Using server version 5.6.16-log
xtrabackup version 2.4.20 based on MySQL server 5.7.26 Linux (x86_64) (revision id: c8b4056)

Prepare command xtrabackup --defaults-extra-file=/glide/backup/xtrabkp/xbk.cnf --parallel=4 --prepare --target-dir=/glide/backup/xtrabkp/bkp

InnoDB: 5.7.26 started; log sequence number 17226588601877
InnoDB: page_cleaner: 1000ms intended loop took 7890ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 17226588601896
200908 17:28:25 completed OK!


14

@jrivera can you please advice if we are good to use percona xtrabackup .Backup worked fine on 5.6.16 . During prepare phase we got InnoDB: 5.7.26 started; log sequence number 17226588601877 for mysql5.6.16

15

@kduvvuri Percona XtraBackup 2.4.20 should be fine then. Did you try and start up the prepared backup on a test v5.6.16 instance or not?

16

@jrivera I will test and update this forum

17

@jrivera I was able to backup MySQL V5.6.16 on RHEL 6.x using xtra backup 2.4.20 , restore the database on rhel7.x . After restore on target server innodb_version | 5.6.16 . Looks like we can use xtra backup 2.4.20 to backup and restore older version MySQL 5.6.16

Thanks for your prompt response