innobackupex fails with --remote-host when trying to create xtrabackup_binary file locally

Bug #787988 reported by Alexey Kopytov on 2011-05-25
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to
Fix Released
Alexey Kopytov
Fix Released
Stewart Smith
Fix Released
Alexey Kopytov

Bug Description

--remote-host is broken, because innobackupex tries to create the xtrabackup_binary file in the backup directory locally which, in case of --remote-host, does not exist:

innobackupex --defaults-file=./my.cnf --user=root --remote-host=mbp /tmp

110525 12:42:17 innobackupex: Connection to database server closed
xtrabackup_logfile 100% 2560 2.5KB/s 00:00
xtrabackup_checkpoints 100% 79 0.1KB/s 00:00

innobackupex: Backup created in directory '/tmp/2011-05-25_12-41-48'
innobackupex: MySQL binlog position: filename '', position
Cannot open file /tmp/2011-05-25_12-41-48/xtrabackup_binary: No such file or directory

The solution is to handle xtrabackup_binary in the same way as xtrabackup_logfile and xtrabackup_checkpoints. That is, create it in a temporary directory (with the temp. dir currently being datadir which is a separate issue), and then scp/stream it along with other files.

Related bugs:

Bug #723318 "xtrabackup_binary is not included in tar archive when streaming"
Bug #668128 "innobackupex --remote-host is broken"

Related branches

Changed in percona-xtrabackup:
status: New → Confirmed
Stewart Smith (stewart) on 2011-05-25
Changed in percona-xtrabackup:
importance: Undecided → High
status: Confirmed → Triaged
tags: added: cr i16134
Changed in percona-xtrabackup:
assignee: nobody → Alexey Kopytov (akopytov)
Changed in percona-xtrabackup:
status: Triaged → Fix Committed
milestone: none → 1.7

Percona now uses JIRA for bug reports so this bug report is migrated to:

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