Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0.34
Description
The mariabackup tool currently reads the [xtrabackup] option group from configuration files. It inherited this behavior from Percona XtraBackup, and it probably makes sense to keep it. However, wouldn't it also make sense for mariabackup to read the [mariabackup] option group? It doesn't currently seem to do so.
e.g. if someone wants to set a user name and password, they can currently do the following:
[xtrabackup]
|
user=sstuser
|
password=password
|
But maybe it would make sense to also support the following?:
[mariabackup]
|
user=sstuser
|
password=password
|
Attachments
Issue Links
- relates to
-
MDEV-18347 mariabackup doesn't read all server option groups from configuration files
- Closed
-
MDEV-18405 Add Mariabackup option to set gtid_slave_pos to original server's gtid_current_pos during prepare
- Stalled
-
MDEV-18917 Don't create xtrabackup_binlog_pos_innodb with Mariabackup
- Closed
-
MDEV-18931 Rename Mariabackup's xtrabackup_* files to mariadb_backup_*
- Closed
-
MDEV-18985 Remove support for XtraDB's changed page bitmap from Mariabackup in 10.2+
- Closed
-
MDEV-19246 Change database and table used for Mariabackup's history
- Closed
-
MDEV-19264 Better support MariaDB GTID for Mariabackup's --slave-info option
- Closed
-
MDEV-20552 Remove innobackupex mode from Mariabackup
- Stalled
-
MDEV-20556 Remove references to "xtrabackup" and "innobackupex" executables in mariabackup option descriptions
- Closed
-
MDEV-21298 mariabackup doesn't read from the [mariadbd] and [mariadbd-X.Y] server option groups from configuration files
- Closed
-
MDEV-21301 mariabackup doesn't read [mariadb-backup] option group in configuration file
- Closed
- links to