Comment 0 for bug 910206

Using:

Percona-Server-client-51-5.1.60-rel13.1.413.rhel5
Percona-Server-shared-51-5.1.60-rel13.1.413.rhel5
Percona-Server-server-51-5.1.60-rel13.1.413.rhel5
xtrabackup-1.6.4-314.rhel5

In sub set_xtrabackup_version, MySQL is asked for the running version and innodb_version variables. A set of regexes then compare the expected version numbers to select an extrabackup binary to run.

When using the RPMs listed, the MySQL version is "5.1.60-rel13.1-log" and the InnoDB version is "1.0.17-rel13.1".

For 5.1, there are three possible regexes:

$var_innodb_version =~ m//
$var_innodb_version =~ m/1\.0\.\d+$/
$var_innodb_version =~ m/1\.0\.\d+-\d/

"1.0.17-rel13.1" does not match the later two, but I'm not entirely sure why it's failing the first, which should match anything.

I corrected my local copy by simply setting $ibbackup_binary to 'xtrabackup', which will work correctly for my specific installation. This may be the safest bet, in addition to adding a check before returning to ensure that *something* was selected, along with an appropriate error if not.

Irritatingly, this problem manifested itself with a misleading error message:

innobackupex: fatal error: no 'mysqld' group in MySQL options
innobackupex: fatal error: OR no 'datadir' option in group 'mysqld' in MySQL options