xtrabackup behaviour is inconsistent when called directly instead of via the innnobackupex symbolic link
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.3 |
Fix Released
|
High
|
Hrvoje Matijakovic | |||
2.4 |
Fix Released
|
High
|
Hrvoje Matijakovic |
Bug Description
Using percona-xtrabackup 2.3.2-1.trusty (from the percona repositories):
/usr/bin/
The command:
/usr/bin/
Performs a backup and streams it to /dev/null
The command:
/usr/bin/xtrabackup --user=root --socket=
Responds:
xtrabackup: Error: unknown argument: '/tmp'
Renaming the xtrabackup binary to innobackupex and running with the same command line causes a backup to be performed and streamed to /dev/null
In the documentation ( https:/
innobackupex --stream=tar /tmp
Also in the documentation ( https:/
xtrabackup does support all the features, but the syntax remains the same as it used to be
correct syntax for xtrabackup is:
xtrabackup --user=root --socket= /var/run/ mysqld/ mysqld. sock --compress --stream=xbstream --backup target-dir=/tmp
We are working to update documentation