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.
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.
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)
@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?
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?
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)
@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
@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