Details
-
New Feature
-
Status: Stalled (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
Mariabackup has an --innobackupex option, which can be used to enable innobackupex mode.
https://mariadb.com/kb/en/library/mariabackup-options/#-innobackupex
This is a compatibility option:
The primary purpose of innobackupex mode is to allow scripts and tools to more easily migrate to Mariabackup if they were originally designed to use the innobackupex utility that is included with Percona XtraBackup. It is not recommended to use this mode in new scripts, since it is not guaranteed to be supported forever.
This mode is not very different from the normal mode. The listed differences are:
- To prepare a backup, the --apply-log option is used instead of the --prepare option.
- To create an incremental backup, the --incremental option is supported.
- The --no-timestamp option is supported.
- To create a partial backup, the --include option is used instead of the --tables option.
- To create a partial backup, the --databases option can still be used, but it's behavior changes slightly.
- The --target-dir option is not used to specify the backup directory. The backup directory should instead be specified as a standalone argument.
These differences are not very significant, and having this extra mode is a bit confusing.
Maybe some of the behavioral differences in innobackupex mode should be merged into Mariabackup's normal mode, and then we should remove innobackupex mode?
UPDATE 14 Aug 2023
This task needs to be about:
- verifying/ensuring that all innobackupex functionality is available in the normal mode (list to be updated)
- add "timestamp" option
- deprecation message for innobackupex (
MDEV-31505)
Attachments
Issue Links
- is blocked by
-
MDEV-31505 Deprecate mariabackup --innobackupex mode
- Closed
- relates to
-
MDEV-14746 mariabackup doesn't read [mariabackup] option group in configuration file
- Closed
-
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-23695 remove unused xtrabackup code
- Open
-
MDEV-32253 impossible to use --no-timestamp option
- Open
-
MDEV-13524 Document --innobackupex option for MariaDB Backup
- Closed
-
MDEV-18215 mariabackup does not report unknown command line options
- Closed
-
MDEV-20556 Remove references to "xtrabackup" and "innobackupex" executables in mariabackup option descriptions
- Closed
ralf.gebhardt asked me, what options do we loose and what is the alternative options.
1. --innobackupex --apply-log is the same as --prepare;
2. --innobackupex --incremental is the same as --incremental-dir, example:
mariabackup --innobackupex --defaults-file=$MYSQLTEST_VARDIR/my.cnf --incremental --no-timestamp --incremental-basedir=$targetdir/full $targetdir/inc;
mariabackup --innobackupex --defaults-file=$MYSQLTEST_VARDIR/my.cnf --apply-log $targetdir/full;
mariabackup --innobackupex --defaults-file=$MYSQLTEST_VARDIR/my.cnf --apply-log --incremental-dir=$targetdir/inc $targetdir/full;
can be exchanged with:
mariabackup --defaults-file=$MYSQLTEST_VARDIR/my.cnf --backup --incremental-basedir=$targetdir/full --target-dir=$targetdir/inc;
mariabackup --defaults-file=$MYSQLTEST_VARDIR/my.cnf --prepare --target-dir=$targetdir/full;
mariabackup --defaults-file=$MYSQLTEST_VARDIR/my.cnf --prepare --incremental-dir=$targetdir/inc --target-dir=$targetdir/full;
3. --no-timestamp is the default mode for mariabackup, see the above example;
4. --include and --tables are the same
5. --databases - according to the code in ibx_init():
xtrabackup_databases_file = opt_ibx_databases;
xtrabackup_databases = opt_ibx_databases;
}
}
--innobackupex --databases can contain both the list of databases/tables and a file name which contains the list of databases/tables, while just --databases can contain only the list of databases/tables, while for the file there is another option --databases_file.
6. --target_dir is omitted in innobackupex mode, just target directory path is required, what is the same as --target_dir in mariabackup, see the example above.
I would say we don't loose any functionality, all innobackupex options have alternative mariabackup options.