# xtrabackup 2.0 GA not working on 5.1 installs?

**URL:** https://forums.percona.com/t/xtrabackup-2-0-ga-not-working-on-5-1-installs/2230
**Category:** Percona XtraBackup
**Created:** [April 6, 2012, 3:46pm UTC](https://forums.percona.com/t/xtrabackup-2-0-ga-not-working-on-5-1-installs/2230 "2012-04-06T15:46:14Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![perconafireitupnet](https://avatars.discourse-cdn.com/v4/letter/p/e99b99/32.png) [@perconafireitupnet](https://forums.percona.com/u/perconafireitupnet)
#### Post date: [April 6, 2012, 3:46pm UTC](https://forums.percona.com/t/xtrabackup-2-0-ga-not-working-on-5-1-installs/2230/1 "2012-04-06T15:46:14Z")

</div>

I recently decided to try upgrading to xtrabackup 2.0 on one of my servers. However, it doesn’t appear that --stream=tar appears to work properly, anymore. Here is my command line:

innobackupex-1.5.1 --user --password --stream=tar ./ \> backup.test2.tar

The output that this gives out is:

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

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

120406 16:05:34 innobackupex-1.5.1: Starting mysql with options: --password=xxxxxxxx --user=‘backup’ --unbuffered –  
120406 16:05:34 innobackupex-1.5.1: Connected to database with mysql child process (pid=29516)  
120406 16:05:40 innobackupex-1.5.1: Connection to database server closed  
IMPORTANT: Please check that the backup run completes successfully.  
At the end of a successful backup run innobackupex-1.5.1  
prints “completed OK!”.

innobackupex-1.5.1: Using mysql Ver 14.14 Distrib 5.1.53, for unknown-linux-gnu (x86\_64) using readline 5.1  
innobackupex-1.5.1: Using mysql server version Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.

innobackupex-1.5.1: Created backup directory /root/dbbackup\_xtra  
120406 16:05:40 innobackupex-1.5.1: Starting mysql with options: --password=xxxxxxxx --user=‘backup’ --unbuffered –  
120406 16:05:40 innobackupex-1.5.1: Connected to database with mysql child process (pid=29541)  
120406 16:05:42 innobackupex-1.5.1: Connection to database server closed

120406 16:05:42 innobackupex-1.5.1: Starting ibbackup with command: xtrabackup --backup --suspend-at-end --target-dir=/tmp --stream=tar  
innobackupex-1.5.1: Waiting for ibbackup (pid=29547) to suspend  
innobackupex-1.5.1: Suspend file ‘/tmp/xtrabackup\_suspended’

xtrabackup version 2.0.0 for Percona Server 5.1.59 unknown-linux-gnu (x86\_64) (revision id: 417)  
xtrabackup: uses posix\_fadvise().  
xtrabackup: cd to /var/lib/mysql  
xtrabackup: Target instance is assumed as followings.  
xtrabackup: innodb\_data\_home\_dir = ./  
xtrabackup: innodb\_data\_file\_path = ibdata1:10M:autoextend  
xtrabackup: innodb\_log\_group\_home\_dir = ./  
xtrabackup: innodb\_log\_files\_in\_group = 2  
xtrabackup: innodb\_log\_file\_size = 2097152000  
xtrabackup: using O\_DIRECT  
120406 16:05:42 InnoDB: Warning: allocated tablespace 96, old maximum was 9

> > log scanned up to (1733864492822)  
> > archive\_write\_header() failed.  
> > [01] xtrabackup: error: cannot open the destination stream for ibdata1  
> > [01] xtrabackup: Error: xtrabackup\_copy\_datafile() failed.  
> > [01] xtrabackup: Error: failed to copy datafile.  
> > innobackupex-1.5.1: Error: ibbackup child process has died at /usr/bin/innobackupex-1.5.1 line 371.

If I remove the --stream=tar option, then everything works fine.  
Everything did work fine under previous versions of xtrabackup, and I was able to downgrade to xtrabackup 1.6.6 and have everything work properly.

---

<div class="post-metadata">

### Author: ![xaprb](https://avatars.discourse-cdn.com/v4/letter/x/49beb7/32.png) [@xaprb](https://forums.percona.com/u/xaprb)
#### Post date: [April 8, 2012, 9:42am UTC](https://forums.percona.com/t/xtrabackup-2-0-ga-not-working-on-5-1-installs/2230/2 "2012-04-08T09:42:26Z")

</div>

Please read the documentation for the updated version; there are large and important changes.

---

<div class="post-metadata">

### Author: ![perconafireitupnet](https://avatars.discourse-cdn.com/v4/letter/p/e99b99/32.png) [@perconafireitupnet](https://forums.percona.com/u/perconafireitupnet)
#### Post date: [April 10, 2012, 1:30pm UTC](https://forums.percona.com/t/xtrabackup-2-0-ga-not-working-on-5-1-installs/2230/3 "2012-04-10T13:30:24Z")

</div>

Ok, then I’m missing something obvious here. Looking at the --help page for innobackupex, I see:

–stream=[tar|. . .]  
This option specifies the format in which to do the streamed backup.  
The option accepts a string argument. The backup will be done to  
STDOUT in the specified format. Currently, the only supported  
formats are tar and xbstream. This option is passed directly to  
xtrabackup’s --stream option.

Same type of thing located at:  
[http://www.percona.com/doc/percona-xtrabackup/innobackupex/s](http://www.percona.com/doc/percona-xtrabackup/innobackupex/s) treaming\_backups\_innobackupex.html

I don’t otherwise see any docs that are specific for xtrabackup 2.0.0. What am I missing here?
