percona-xtrabackup 2.1 + 5.1 w/ innodb plugin

Reported by Andrew Garner on 2013-05-16
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Critical
Alexey Kopytov
2.1
Critical
Alexey Kopytov

Bug Description

As I understand percona-xtrabackup 2.1 still supports MySQL 5.1 as long as the innodb-plugin is being used. However, attempting to do so fails:

# mysql -se 'SELECT @@version, @@innodb_version'
@@version @@innodb_version
5.1.67-log 1.0.17

# mysql -e 'SHOW PLUGINS' | grep InnoDB
InnoDB ACTIVE STORAGE ENGINE ha_innodb_plugin.so GPL

# innobackupex $HOME/backup
innobackupex: Error: Support for MySQL 5.1 with builtin InnoDB (not the plugin) was removed in Percona XtraBackup 2.1. The last version to support MySQL 5.1 with builtin InnoDB was Percona XtraBackup 2.0. at /usr/bin/innobackupex line 387.

This is due to the check here:

    if($var_version =~ m/5\.1\.\d/ && $var_innodb_version =~ m/.*/) {
    Die "Support for MySQL 5.1 with builtin InnoDB (not the plugin) was removed in Percona XtraBackup 2.1. The last version to support MySQL 5.1 with builtin InnoDB was Percona XtraBackup 2.0.";
    }

I suppose this check intends to look for an empty/missing innodb_version instead.

James Dooley (james-v) wrote :

This is also blocking backups on Percona-Server 5.1.

MarcODell (marc-odell) wrote :

Verified. This bug is stopping backups on Percona Server 5.1.66 with the following error:

innobackupex: Error: Support for MySQL 5.1 with builtin InnoDB (not the plugin) was removed in Percona XtraBackup 2.1. The last version to support MySQL 5.1 with builtin InnoDB was Percona XtraBackup 2.0. at /usr/bin/innobackupex line 387.

Downgrading to 2.0.7 allowed me to use Xxtrabackup.

Cheers!
Marc O'Dell
Percona Remote DBA Team

Changed in percona-xtrabackup:
status: New → Confirmed
Alexey Kopytov (akopytov) wrote :

Verified. The workaround is to set the xtrabackup binary explicitly with

innobackupex --ibbackup=xtrabackup ...

James Dooley (james-v) wrote :

Did a quick test of the specific portion of the patch related to this bug, everything seems to be working properly now.

Hi James,

Thanks so much! That was the quickest bug fix I have ever seen.

Cheers!
Marc

On May 17, 2013, at 7:04 AM, James Dooley <email address hidden> wrote:

> Did a quick test of the specific portion of the patch related to this
> bug, everything seems to be working properly now.
>
> --
> You received this bug notification because you are subscribed to Percona
> XtraBackup.
> Matching subscriptions: xtrabackup21
> https://bugs.launchpad.net/bugs/1180905
>
> Title:
> percona-xtrabackup 2.1 + 5.1 w/ innodb plugin
>
> Status in Percona XtraBackup:
> Fix Committed
> Status in Percona XtraBackup 2.1 series:
> Fix Committed
>
> Bug description:
> As I understand percona-xtrabackup 2.1 still supports MySQL 5.1 as
> long as the innodb-plugin is being used. However, attempting to do so
> fails:
>
> # mysql -se 'SELECT @@version, @@innodb_version'
> @@version @@innodb_version
> 5.1.67-log 1.0.17
>
> # mysql -e 'SHOW PLUGINS' | grep InnoDB
> InnoDB ACTIVE STORAGE ENGINE ha_innodb_plugin.so GPL
>
> # innobackupex $HOME/backup
> innobackupex: Error: Support for MySQL 5.1 with builtin InnoDB (not the plugin) was removed in Percona XtraBackup 2.1. The last version to support MySQL 5.1 with builtin InnoDB was Percona XtraBackup 2.0. at /usr/bin/innobackupex line 387.
>
> This is due to the check here:
>
> if($var_version =~ m/5\.1\.\d/ && $var_innodb_version =~ m/.*/) {
> Die "Support for MySQL 5.1 with builtin InnoDB (not the plugin) was removed in Percona XtraBackup 2.1. The last version to support MySQL 5.1 with builtin InnoDB was Percona XtraBackup 2.0.";
> }
>
> I suppose this check intends to look for an empty/missing
> innodb_version instead.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/percona-xtrabackup/+bug/1180905/+subscriptions

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers