Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.3.20
-
None
-
Ubuntu 18.04
dpkg -l | grep maria
ii libmariadb3:amd64 1:10.3.20+maria~bionic amd64 MariaDB database client library
ii mariadb-backup 1:10.3.20+maria~bionic amd64 Backup tool for MariaDB server
ii mariadb-client-10.3 1:10.3.20+maria~bionic amd64 MariaDB database client binaries
ii mariadb-client-core-10.3 1:10.3.20+maria~bionic amd64 MariaDB database core client binaries
ii mariadb-common 1:10.3.20+maria~bionic all MariaDB database common files (e.g. /etc/mysql/conf.d/mariadb.cnf)
ii mariadb-server-10.3 1:10.3.20+maria~bionic amd64 MariaDB database server binaries
ii mariadb-server-core-10.3 1:10.3.20+maria~bionic amd64 MariaDB database core server files
ii mysql-common 1:10.3.20+maria~bionic all MariaDB database common files (e.g. /etc/mysql/my.cnf)
Ubuntu 18.04 dpkg -l | grep maria ii libmariadb3:amd64 1:10.3.20+maria~bionic amd64 MariaDB database client library ii mariadb-backup 1:10.3.20+maria~bionic amd64 Backup tool for MariaDB server ii mariadb-client-10.3 1:10.3.20+maria~bionic amd64 MariaDB database client binaries ii mariadb-client-core-10.3 1:10.3.20+maria~bionic amd64 MariaDB database core client binaries ii mariadb-common 1:10.3.20+maria~bionic all MariaDB database common files (e.g. /etc/mysql/conf.d/mariadb.cnf) ii mariadb-server-10.3 1:10.3.20+maria~bionic amd64 MariaDB database server binaries ii mariadb-server-core-10.3 1:10.3.20+maria~bionic amd64 MariaDB database core server files ii mysql-common 1:10.3.20+maria~bionic all MariaDB database common files (e.g. /etc/mysql/my.cnf)
Description
I am running multi-source slave and trying to backup database with mariabackup.
mariabackup --compress --open-files-limit=9046 --slave-info --safe-slave-backup --safe-slave-backup-timeout=500 --backup --target-dir /backup/mysqld1/2019-11-12
But mariabackup does not detect multi-source slave configuration ( i don't have default_master_connection configured, only named connections)
[00] 2019-11-12 12:02:48 Failed to get master binlog coordinates from SHOW SLAVE STATUS.This means that the server is not a replication slave. Ignoring the --slave-info option
[00] 2019-11-12 12:02:48 Compressing xtrabackup_binlog_info
[00] 2019-11-12 12:02:48 ...done
[00] 2019-11-12 12:02:48 Executing FLUSH NO_WRITE_TO_BINLOG ENGINE LOGS...
[00] 2019-11-12 12:02:48 mariabackup: The latest check point (for incremental): '587720589969'
mariabackup: Stopping log copying thread.[00] 2019-11-12 12:02:48 >> log scanned up to (587723317367)
[00] 2019-11-12 12:02:48 >> log scanned up to (587723317367)
[00] 2019-11-12 12:02:48 Executing UNLOCK TABLES
[00] 2019-11-12 12:02:48 All tables unlocked
Attachments
Issue Links
- relates to
-
MDEV-30666 Different GTID for the same binlog File + Position (xtrabackup_binlog_info vs binlog_gtid_pos)
- Closed