Not the answer you need?
Register and ask your own question!

xtrabackup 8.0 do not work with 8.0.19 cluster

SfinxSfinx Current User Role Novice
edited July 15 in Percona XtraBackup
Greetings,
Trying to evaluate the PXC for my project but afraid that all the things are still not mature. Created simple 3-node cluster + ProxySQL setup as stated in LATEST docs, played with sysbench all is ok. Next trying to backup it using xtrabackup and it fails. If I'm trying to connect to cluster over ProxySQL it fails to connect as seems like password is not propagated (!!!) :
[email protected]:~$ xtrabackup --backup --target-dir=./backups --login-path=pxc
xtrabackup: recognized server arguments: --datadir=/var/lib/mysql --tmpdir=/tmp 
xtrabackup: recognized client arguments: --user=proxyuser --password=* --host=127.0.0.1 --backup=1 --target-dir=./backups 
xtrabackup version 8.0.13 based on MySQL server 8.0.20 Linux (x86_64) (revision id: fdf0f4c)
200715 08:35:03  version_check Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup;host=127.0.0.1' as 'proxyuser'  (using password: YES).
200715 08:35:03  version_check Connected to MySQL server
200715 08:35:03  version_check Executing a version check against the server...
200715 08:35:03  version_check Done.
200715 08:35:03 Connecting to MySQL server host: 127.0.0.1, user: proxyuser, password: set, port: not set, socket: not set
Failed to connect to MySQL server: ProxySQL Error: Access denied for user 'proxyuser'@'172.29.0.1' (using password: NO).
If I'm trying to connect directly to any node the error is different:
[email protected]:~$ sudo xtrabackup --backup --target-dir=./backups -u root -pPaSw0rd -H 172.29.0.2 
xtrabackup: recognized server arguments: --datadir=/var/lib/mysql --tmpdir=/tmp 
xtrabackup: recognized client arguments: --user=proxyuser --password=* --host=127.0.0.1 --backup=1 --target-dir=./backups --user=root --password=* --host=172.29.0.2 
xtrabackup version 8.0.13 based on MySQL server 8.0.20 Linux (x86_64) (revision id: fdf0f4c)
200715 08:36:04  version_check Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup;host=172.29.0.2' as 'root'  (using password: YES).
200715 08:36:04  version_check Connected to MySQL server
200715 08:36:04  version_check Executing a version check against the server...
200715 08:36:04  version_check Done.
200715 08:36:04 Connecting to MySQL server host: 172.29.0.2, user: root, password: set, port: not set, socket: not set
Using server version 8.0.19-10
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: open files limit requested 0, set to 65536
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
Number of pools: 1
200715 08:36:04 Connecting to MySQL server host: 172.29.0.2, user: root, password: set, port: not set, socket: not set
Redo log format is v1. The redo log was created before MySQL 8.0.3.
Redo log format is v1. The redo log was created before MySQL 8.0.3.
200715 08:36:04 >> log scanned up to (2884065)
xtrabackup: Redo Log Archiving is not set up.
xtrabackup: Generating a list of tablespaces
xtrabackup: Generating a list of tablespaces
Scanning './'
Completed space ID check of 0 files.
Allocated tablespace ID 13 for mysql/innodb_table_stats, old maximum was 0
Will create 2 new undo tablespaces.
Cannot create undo tablespaces since innodb_read_only has been set. Using 0 existing undo tablespaces.
Cannot continue InnoDB startup in read_only mode because there are no existing undo tablespaces found.
xtrabackup: error: xb_load_tablespaces() failed with error code 11
What are the problems with xtrabackup here ? The most confusing is that it can't even connect over ProxySQL

Answers

  • jriverajrivera Percona Support Engineer Percona Staff Role
    Hi, Thanks for testing PXC, Xtrabackup and Proxysql. The issue here is that Xtrabackup is not supposed to connect to the MySQL instance through ProxySQL since it is going to take a physical backup and does not work like mysqldump. We recommend you install xtrabackup on the node itself and take the backup from inside the node since xtrabackup will need direct access to the physical files.
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.