Percona XtraBackup 2.1.3 for MySQL available for download

Percona XtraBackup 2.1.3 for MySQL available for download


Percona XtraBackup for MySQL Percona is glad to announce the release of Percona XtraBackup 2.1.3 for MySQL on May 22, 2013. Downloads are available from our download site here and Percona Software Repositories.

This release fixes a high priority bug. It’s advised to upgrade your latest 2.1 version to 2.1.3 if you’re using the Percona XtraBackup with Percona XtraDB Cluster. This release is the latest stable release in the 2.1 series.

Bug Fixed:

Release notes with all the bugfixes for Percona XtraBackup 2.1.3 are available in our online documentation. Bugs can be reported on the launchpad bug tracker.

* * *

Percona XtraBackup is the world’s only open-source, free MySQL hot backup software that performs non-blocking backups for InnoDB and XtraDB databases. With Percona XtraBackup, you can achieve the following benefits:

  • Backups that complete quickly and reliably
  • Uninterrupted transaction processing during backups
  • Savings on disk space and network bandwidth
  • Automatic backup verification
  • Higher uptime due to faster restore time

XtraBackup makes MySQL hot backups for all versions of Percona Server, MySQL, MariaDB, and Drizzle. It performs streaming, compressed, and incremental MySQL backups.

Percona’s enterprise-grade commercial MySQL Support contracts include support for XtraBackup. We recommend support for critical production deployments.


Share this post

Comments (4)

  • Azigui Reply

    since I upgrade percona xtrabackup to 2.1.3.
    My node is crashed and I have this error in my log :

    07:53:55 UTC – mysqld got signal 11 ;
    This could be because you hit a bug. It is also possible that this binary
    or one of the libraries it was linked against is corrupt, improperly built,
    or misconfigured. This error can also be caused by malfunctioning hardware.
    We will try our best to scrape up some info that will hopefully help
    diagnose the problem, but since we have already crashed,
    something is definitely wrong and this may fail.
    Please help us make Percona Server better by reporting any
    bugs at

    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4432877 K bytes of memory
    Hope that’s ok; if not, decrease some variables in the equation.

    Thread pointer: 0x7f9234000990
    Attempting backtrace. You can use the following information to find out
    where mysqld died. If you see no messages after this, something went
    terribly wrong…
    stack_bottom = 7f9244a8fdb8 thread_stack 0x40000

    Trying to get some variables.
    Some pointers may be invalid and cause the dump to abort.
    Query (0): is an invalid pointer
    Connection ID (thread ID): 3
    Status: NOT_KILLED

    You may download the Percona Server operations manual by visiting You may find information
    in the manual which will help you identify the cause of the crash.
    130528 09:53:56 mysqld_safe Number of processes running now: 0
    130528 09:53:56 mysqld_safe WSREP: not restarting wsrep node automatically
    130528 09:53:56 mysqld_safe mysqld from pid file /var/lib/mysql/ ended

    in an another environment I have three nodes on VM with percona-xtrabackup-2.0.7-552.rhel6.x86_64 and it’s working perfectly.

    Best regards,


    May 30, 2013 at 3:49 am
  • Hrvoje Matijakovic Reply

    Hi Azigui,

    Can you please report this as a bug on Launchpad ( This way it would be easier to track and provide more information.

    Thank you,

    May 30, 2013 at 3:58 am
  • Fernando Mattera Reply

    Does this version of xtrabackup backup of used pages only?
    We use xtrabackup_55 version 2.1.3 and basically copies entire database to another folder, and us later we run tar+gzip to save space.

    May 30, 2013 at 1:28 pm
  • Paul Reply

    Is there any change of this supporting the hotbackup interface for when you are using the percona-tokudb engine?

    July 1, 2013 at 7:39 pm

Leave a Reply