innobackupex copy-back doesn't work without ibbackup

Reported by Paul Graessle on 2011-07-27
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Low
Alexey Kopytov
1.5
Undecided
Alexey Kopytov
1.6
Low
Alexey Kopytov
2.0
Low
Alexey Kopytov
Trunk
Undecided
Alexey Kopytov

Bug Description

According to the online documentation, you should be able to restore the backup by specifying the following:
  innobackupex --copy-back <location_of_backup>

When I attempt to restore this way, I receive the following:
  InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
  and Percona Inc 2009-2011. All Rights Reserved.

  This software is published under
  the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

  IMPORTANT: Please check that the copy-back run completes successfully.
             At the end of a successful copy-back run innobackupex
             prints "completed OK!".

  Can't exec "autodetect": No such file or directory at /usr/bin/innobackupex line 1972.
  innobackupex: fatal error: no 'mysqld' group in MySQL options
  innobackupex: fatal error: OR no 'datadir' option in group 'mysqld' in MySQL options

I tried to specify the ibbackup-binary option, then I read in another bug to use ibbackup instead of ibbackup-binary. I was then able to successfully restore the backup.

I am currently using 64-bit version of CentOS 5.6 with xtrabackup 1.6.2 (1.6.2-274.rhel5). The xtrabackup binaries are listed in my PATH.

Charl (charlretief) wrote :

I have the same problem after upgrading to Xtrabackup 1.6.2
I am currently running MySql Server 5.5.15 on Ubuntu Server 10.04 (64-bit).

The above mentioned workaround does work:

innobackupex --ibbackup=xtrabackup_55 --copy-back <<backup_location>>

Alexey Kopytov (akopytov) wrote :

This bug is a regression introduced in 1.6.2 by the fix for bug #729497.

Changed in percona-xtrabackup:
status: New → Confirmed
assignee: nobody → Alexey Kopytov (akopytov)
Changed in percona-xtrabackup:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers