Dear community,

The release 0.8 of the opensource backup tool for InnoDB and XtraDB is available for download.

Key features:

tar4ibd is made to be sure that read of InnoDB page is consistent. Before we had some complains what in stream mode some pages are getting corrupted, and we suspect tar can do read of pages in time when they changed. So we patches libtar to make read consistent.

Export is added to support moving .ibd tablespaces between servers.

The list of other features in the release includes:

  • Support of ARCHIVE tables
  • Addded incremental option to innobackupex-1.5.1 script
  • Rollback XA PREPAREd transaction automatically at –prepare
  • To extend tablespace size, if needed after –prepare
  • Data page corruption check is added to local backup mode
  • innobackupex can pass –export option
  • Bug #389360: innobackupex-1.5.1 accepts scp options

Fixed bugs:

  • Bug #388062: Update to innobackupex to include incremental
  • fix error handling of tar stream

The binary packages for RHEL4,5, Debian, FreeBSD as well as source code of the XtraBackup is available on https://www.percona.com/mysql/xtrabackup/0.8/.

The project lives on Launchpad : https://launchpad.net/percona-xtrabackup and you can report bug to Launchpad bug system:
https://launchpad.net/percona-xtrabackup/+filebug. The documentation is available on our Wiki.

For general questions use our Pecona-discussions group, and for development question Percona-dev group.

For support, commercial and sponsorship inquiries contact Percona.

Share this post

Comments (8)

  • http://krow.livejournal.com/


    Awesome on supporting Archive files!

    Are you doing this in the manner that archive_reader does, aka as an online backup?


    July 1, 2009 at 10:30 am
  • Vadim


    No, we are doing it like regular MyISAM files, under LOCK TABLES.

    July 1, 2009 at 3:16 pm
  • Davy


    I saw a post a couple days ago talking about possible downfalls of innobackupex and I noticed one of the items says that xtrabackup writes to the ibdata* files. Could you clear up what/why/if this happens as this has worried me a little bit about the possibility of corrupting Innodb?

    July 1, 2009 at 6:45 pm
  • Vadim


    Please see my comment to that post, I think it was misleading.

    xtrabackup does not change any files on original server and can’t cause any corruption on working server.

    xtrabackup does change already copied ( destination files), but that is exactly how ibbackup works also.

    Sure as any software xtrabackup may have bugs and writes “possible” may get destination files “corrupted”, but again it is similar to ibbackup.

    But in comparison with ibbackup we have open all source code and you can check how our backup solution works.

    So far we faced corruption only in case with streaming via tar, and that’s why we implemented tar4ibd stream.

    July 1, 2009 at 10:08 pm
  • Oren

    Hi Vadim,

    Thanks for these updates. A couple of questions:

    1. I see there are no RHEL 32-bit packages. Are you planning to release any?

    2. What’s the probability of old backups made with stream=tar are corrupt? Are old backups unusable?


    July 1, 2009 at 11:16 pm
  • Vadim


    1. We do not plan to produce 32bit binaries, only by special requests.

    2. I would say we observed corruption with stream=tar once per month doing daily backups. Corruption is noticed on –prepare stage. So if you see –prepare was OK, you should be safe.

    July 1, 2009 at 11:53 pm
  • evg


    I guess you forgot to update version of the xtrabackup. It still reports “xtrabackup Ver rc-0.7 for 5.0.83 pc-linux-gnu (x86_64)”.


    July 6, 2009 at 2:22 am
  • Ranjan

    I have installed the xtrabackup in linux CentOS 5 – 32-BIT. But I am getting this error when I run backup command. Any one let me know xtrabackup not supporting 32-BIT CentOS 5

    Getting error
    -bash: ./xtrabackup: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory

    January 14, 2010 at 6:30 pm

Comments are closed.

Use Percona's Technical Forum to ask any follow-up questions on this blog topic.