backups not working with archive logging enabled

Bug #1227240 reported by Hrvoje Matijakovic on 2013-09-18
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Fix Released
Medium
Vlad Lesin
2.1
Fix Released
Medium
Vlad Lesin
2.2
Fix Released
Medium
Vlad Lesin

Bug Description

When trying to take a backup from PS-5.6.13-60.5 with Log archiving enabled I keep getting the error:

root@ps56:~# innobackupex /home/vagrant/

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.

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

130918 16:26:35 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup' (using password: NO).
130918 16:26:35 innobackupex: Connected to MySQL server
IMPORTANT: Please check that the backup run completes successfully.
           At the end of a successful backup run innobackupex
           prints "completed OK!".

innobackupex: Using mysql server version 5.6.13-rc60.5

innobackupex: Created backup directory /home/vagrant/2013-09-18_16-26-35

130918 16:26:35 innobackupex: Starting ibbackup with command: xtrabackup_56 --defaults-group="mysqld" --backup --suspend-at-end --target-dir=/home/vagrant/2013-09-18_16-26-35 --tmpdir=/tmp
innobackupex: Waiting for ibbackup (pid=4296) to suspend
innobackupex: Suspend file '/home/vagrant/2013-09-18_16-26-35/xtrabackup_suspended_2'

xtrabackup_56 version 2.1.3 for MySQL server 5.6.11 Linux (x86_64) (revision id: undefined)
xtrabackup: error: --archived-logs-dir and --to-archived-lsn can be used only with --prepare
innobackupex: Error: The xtrabackup child process has died at /usr/local/bin/innobackupex line 2579.

Tested with current trunk build and the version available from daily XtraBackup repos

Related branches

Changed in percona-xtrabackup:
assignee: nobody → Vlad Lesin (vlad-lesin)
Vlad Lesin (vlad-lesin) wrote :

Hrvoje, I can not repeat it with the parameters you gave.

I tried to repeat in with the following xtrabackup options:
./xtrabackup_56 --backup --target-dir=/tmp
/1/backup --datadir=/tmp/1/percona-current/data --suspend-at-end --defaults-group="mysql" --tmp-dir=/tmp --inn
odb_log_file_size=2M

on PS-5.6.13 with the following options:
bin/mysqld --no-defaults --gdb --basedir=/tmp/1/percona-current --datadir=/tmp/1/percona-current/data --innodb_log_archi
ve=ON --innodb_log_arch_dir=/tmp/1/percona-current/data --innodb-file-per-table --innodb_log_file_size=2M --in
nodb_log_files_in_group=5

and it works ok.

So I need some additional data:
1) How do you build xtrabackup and PS?
2) Your my.cnf file.

Alexey Kopytov (akopytov) wrote :

Vlad,

Hrvoje was using innobackupex rather than the xtrabackup binary.

Vlad Lesin (vlad-lesin) wrote :

Alexey,

Yes, but innobackupex invokes xtrabackup binary with the same options as I did. xtrabackup checks those options and outputs that diagnostic message independent of the way it was started.

So my assumption that configuration file contains additional options(--archived-logs-dir for example).

How to reproduce:

[mysqld]
datadir=/var/lib/mysql
innodb_log_archive=1
innodb_log_arch_dir=/archived_logs

and then just run:

# innobackupex /backups/

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.

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

131013 13:16:05 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup' (using password: NO).
131013 13:16:05 innobackupex: Connected to MySQL server
IMPORTANT: Please check that the backup run completes successfully.
           At the end of a successful backup run innobackupex
           prints "completed OK!".

innobackupex: Using mysql server version 5.6.13-rc61.0

innobackupex: Created backup directory /backups/2013-10-13_13-16-05

131013 13:16:05 innobackupex: Starting ibbackup with command: xtrabackup_56 --defaults-group="mysqld" --backup --suspend-at-end --target-dir=/backups/2013-10-13_13-16-05 --tmpdir=/tmp
innobackupex: Waiting for ibbackup (pid=25978) to suspend
innobackupex: Suspend file '/backups/2013-10-13_13-16-05/xtrabackup_suspended_2'

xtrabackup_56 version 2.1.5 for MySQL server 5.6.11 Linux (x86_64) (revision id: undefined)
xtrabackup: error: --archived-logs-dir and --to-archived-lsn can be used only with --prepare
innobackupex: Error: The xtrabackup child process has died at /usr/bin/innobackupex line 2579.

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-665

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

Other bug subscribers