September 18, 2014

Percona XtraBackup 1.6

Percona XtraBackup 1.6 is now available for download and is the current stable release version of XtraBackup.

Options Added

  • Added option --extra-lsndir to innobackupex. When specified for the backup phase, the option is passed to xtrabackup, and lsn information is stored with the file in the specified directory. This is needed so that lsn information is preserved during stream backup. (Vadim Tkachenko)
  • Added option --incremental-lsn to innobackupex. If specified, this option is passed directly to the xtrabackup script and --incremental-basedir is ignored. (Vadim Tkachenko)
  • Added option --incremental-dir to innobackupex. This option is passed directly to the xtrabackup binary. (Vadim Tkachenko)
  • Added option --safe-slave-backupto innobackupex. (Daniel Nichter)
  • Added option --safe-slave-backup-timeout to innobackupex. (Daniel Nichter)

Other Changes

  • Eliminated some compiler warnings. (Stewart Smith)
  • Ported XtraBackup to MySQL 5.1.55, MySQL 5.5.9, Percona Server 5.1.55-12.6, and Percona Server 5.5.9-20.1 code bases. The xtrabackup_55 binary is now based on Percona Server 5.5, rather than MySQL 5.5. Support for building against InnoDB plugin in MySQL 5.1 has been removed. (Alexey Kopytov)
  • Updates were made to made to the built-in innobackupex usage docs. (Baron Schwartz, Fred Linhoss)
  • Added a manual page for XtraBackup. (Aleksandr Kuzminsky)
  • Disabled auto-creating ib_logfile* when innobackupex is called with --redo-only or with --incremental-dir. If neccessary ib_logfile* can be created later with xtrabackup --prepare call. (Vadim Tkachenko)
  • Fixed xtrabackup exit code to improve portability: EXIT_SUCCESS on success and EXIT_FAILURE on a failure. (Aleksandr Kuzminsky)
  • For portability, the XtraBackup build script now tries to link with libaio only on Linux. (Aleksandr Kuzminsky)

Bugs Fixed

  • Bug #368945 – When option --prepare was specified, an error message was requesting that datadir be set, even though it’s not a required option. (Vadim Tkachenko)
  • Bug #420181 – The innobackupex script now backs up CSV tables. (Valentine Gostev)
  • Bug #597384 – The innobackup --include option now handles non-InnoDB tables. (Vadim Tkachenko)
  • Bug #606981 – Streaming InnoDB files with tar4ibd could lead to filesystem hangs when InnoDB was configured to access data files with the O_DIRECT flag. The reason was that tar4ibd did not have support for O_DIRECT and simultaneous O_DIRECT + non-O_DIRECT access to a file on Linux is disallowed. Fixed innobackupex and tar4ibd to use O_DIRECT on input InnoDB files if the value of innodb_flush_method is O_DIRECT in the InnoDB configuration. (Alexey Kopytov)
  • Bug #646647 – Removed the bogus warning about invalid data in the Perl version string in innobackupex. (Baron Schwartz)
  • Bug #672384 – When no log files can be found in the backup directory while executing xtrabackup --stats, a descriptive error message is printed instead of crashing. (Alexey Kopytov)
  • Bug #688211 – Using the --password option with innobackupex to specify MySQL passwords containing special shell characters (such as “&”) did not work, even when the option value was properly quoted.
  • Bug #688417 – It’s now possible to do incremental backups for compressed InnoDB tables.
  • Bug #701767 – The script innobackupex-1.5.1 was renamed to innobackupex. Symbolic link innobackupex-1.5.1 was created for backupward compatibility. (Vadim Tkachenko)
  • Bug #703070xtrabackup_55 crashed with an assertion failure on non-Linux platforms. (Alexey Kopytov)
  • Bug #703077 – Building xtrabackup could fail on some platforms due to an incorrect argument to CMake. Fixed by changing the -DWITH_ZLIB argument to lowercase, because that’s what the CMake scripts actually expect. (Alexey Kopytov)
  • Bug #713799 – Dropping a table during a backup process could result in assertion failure in xtrabackup. Now it continues with a warning message about the dropped table. (Alexey Kopytov)
  • Bug #717784 – Performing parallel backups with the --parallel option could cause xtrabackup to fail with the “cannot mkdir” error. (Alexey Kopytov)

For more information, please see the following links:

About Fred Linhoss

Fred is a former Percona employee.
Fred has a long history in software development and has held positions in both programming and technical management. He holds a degree in Computer Science from Virginia Tech.

Comments

  1. Alexey Kopytov says:

    Marcus,

    Unfortunately, some bugs including https://bugs.launchpad.net/bugs/690661 have slipped through the cracks and not made it into 1.6. So the release notes are currently more accurate than bug reports on Launchpad. We are working on fixing that right now.

    Speaking of quicklz compression, that feature is scheduled for the next major XtraBackup release.

  2. Alexey Kopytov says:

    George,

    No, https://bugs.launchpad.net/bugs/733665 wasn’t scheduled for 1.6. I think it will be fixed in the next release.

  3. Marcus Bointon says:

    Prior to the reelase I saw various comments on here about integration of quicklz for integrated compression of tar streams. I don’t see any reference to that in these release notes or the man pages – did it not make it in after all? There seem to be a fair number of bugs marked as fixed for 1.6 in launchpad that are not mentioned here – did you only list highlights?

  4. Marcus Bointon says:
  5. George says:

    Sweet, has the bug been fixed where innobackupex won’t recognise MariaDB version string http://blogs.skysql.com/2011/03/using-xtrabackup-and-incremental.html ?

    Thanks

  6. George says:

    Sweet, has the bug been fixed where innobackupex won’t recognise MariaDB version string http://blogs.skysql.com/2011/03/using-xtrabackup-and-incremental.html ?

    Thanks

  7. Prior to the reelase I saw various comments on here about integration of quicklz for integrated compression of tar streams. I don’t see any reference to that in these release notes or the man pages – did it not make it in after all? There seem to be a fair number of bugs marked as fixed for 1.6 in launchpad that are not mentioned here – did you only list highlights?

  8. Alexey Kopytov says:

    George,

    No, https://bugs.launchpad.net/bugs/733665 wasn’t scheduled for 1.6. I think it will be fixed in the next release.

  9. Alexey Kopytov says:

    Marcus,

    Unfortunately, some bugs including https://bugs.launchpad.net/bugs/690661 have slipped through the cracks and not made it into 1.6. So the release notes are currently more accurate than bug reports on Launchpad. We are working on fixing that right now.

    Speaking of quicklz compression, that feature is scheduled for the next major XtraBackup release.

  10. nouri says:

    hello,
    i can`t find and download extrabackup 1.6 ?
    what can i do?

  11. Mauricio Stekl says:

    Hi Nouri, we have just released Xtrabackup 1.6.2.
    You can find more info and download links on the following post: http://www.mysqlperformanceblog.com/2011/07/25/percona-xtrabackup-1-6-2-released/

  12. abdollah says:

    Hi mauricio ,I need windows version, i cant find it all of the internet.
    i download source but i don how can i use ?
    (I don speak english well so excuse me).

  13. honeybee says:

    Does innobackupex has the option to customize ‘s backup name instead of the default format such as “2011-09-06_12-28-21″?

  14. Alexey Kopytov says:

    honeybee,

    No, there’s currently no option to customize backup directory name. Though I think it would be a reasonable feature request, feel free to file a bug.

Speak Your Mind

*