Comment 3 for bug 369913

On Fri, Jun 5, 2009 at 8:56 AM, Vadim Tkachenko<email address hidden> wrote:
> Todd,
>
> But it does write
>
> 090605 11:55:04  innobackupex: Starting mysql with options: --unbuffered
> ....
> 090605 01:06:05  innobackupex: innobackup completed OK!

My apologies, I omitted the important information that I was
specifically asking for this in the copy-back operation. This is how
the output looks for --copy-back:

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy.
All Rights Reserved.

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

innobackupex: Starting to copy MyISAM tables, indexes,
innobackupex: .MRG, .TRG, .TRN, .opt, and .frm files
innobackupex: in '/mysqlBackups/mysqlBackup1/2009-05-30_16-32-10'
innobackupex: back to original data directory '/var/lib/mysql'
innobackupex: Copying directory
'/mysqlBackups/mysqlBackup1/2009-05-30_16-32-10/magento_ws_58455'
innobackupex: Copying directory
'/mysqlBackups/mysqlBackup1/2009-05-30_16-32-10/magento_ws_27421'
<snip>

Here's how I called it:

innobackupex-1.5.1 --copy-back
/mysqlBackups/mysqlBackup1/2009-05-30_16-32-10/ 2>&1 | tee
/tmp/innobackup.out

Thank you for pointing that out :-)

--
Regards... Todd