Affects Version/s: None
Fix Version/s: None
**Reported in Launchpad by Dan Rogart last update 24-10-2011 10:00:59
innobackupex has the following parameter defined (see innobackupex --help or perldoc innobackupex):
This option specifies which xtrabackup binary should be used. The
option accepts a string argument. IBBACKUP-BINARY should be the
command used to run XtraBackup. The option can be useful if the
xtrabackup binary is not in your search path or working directory.
However, it does not seem to work when invoked:
[drogart@some_server bin]$ ./innobackupex --ibbackup-binary=xtrabackup_51
Unknown option: ibbackup-binary
innobackupex: Bad command line arguments
I am using the 1.6 xtrabackup scripts and binaries, installed via tar.gz on a CentOS 5.2 system. FWIW, the autodetection seems to work OK, except that if your xtrabackup binaries are not in the $PATH then it will fail with a different error (already reported here by someone else: https://bugs.launchpad.net/percona-xtrabackup/+bug/806531).
I can work around this, but it's not optimal that one of the defined script parameters doesn't work at all. Maybe I'm missing something simple?