Merge lp:~hrvojem/percona-xtrabackup/rn-2.0.7-2.0 into lp:percona-xtrabackup/2.0

[Hrvoje Matijakovic]

[Alexey Kopytov (akopytov)]

Approved with one minor comment:

> On the destination server running |Percona Server| with |XtraDB| or |MySQL| 5.6, with :term:`innodb_expand_import` enabled

This sounds like innodb_expand_import must be enabled on MySQL 5.6 as well. Needs to be rephrased to make clear only XtraDB requires that option.

review: Approve

=== modified file 'doc/source/conf.py'
--- doc/source/conf.py	2013-03-20 06:09:32 +0000
+++ doc/source/conf.py	2013-05-06 13:57:23 +0000
@@ -51,9 +51,9 @@
 # built documents.
 #
 # The short X.Y version.
-version = '2.0.6'
+version = '2.0.7'
 # The full version, including alpha/beta/rc tags.
-release = '2.0.6'
+release = '2.0.7'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
@@ -108,6 +108,8 @@
 
 .. |XtraBackup|  replace:: *XtraBackup*
 
+.. |Percona XtraBackup|  replace:: *Percona XtraBackup*
+
 .. |Percona Server|  replace:: *Percona Server*
 
 .. |Percona|  replace:: *Percona*
 
=== modified file 'doc/source/installation/apt_repo.rst'
--- doc/source/installation/apt_repo.rst	2013-04-30 07:33:04 +0000
+++ doc/source/installation/apt_repo.rst	2013-05-06 13:57:23 +0000
@@ -28,6 +28,7 @@
 ------
 
  * 6.0 (squeeze)
+ * 7.0 (wheezy)
 
 Ubuntu
 ------
@@ -35,6 +36,7 @@
  * 10.04LTS (lucid)
  * 12.04LTS (precise) 
  * 12.10 (quantal)
+ * 13.04 (raring)
 
 Experimental Repository
 =======================
 
=== added file 'doc/source/release-notes/2.0/2.0.7.rst'
--- doc/source/release-notes/2.0/2.0.7.rst	1970-01-01 00:00:00 +0000
+++ doc/source/release-notes/2.0/2.0.7.rst	2013-05-06 13:57:23 +0000
@@ -0,0 +1,63 @@
+============================
+|Percona| |XtraBackup| 2.0.7
+============================
+
+Percona is glad to announce the release of Percona XtraBackup 2.0.7 on May 6, 2013. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-2.0.7/>`_ and :doc:`Percona Software Repositories </installation>`.
+
+This release is the current GA (Generally Available) stable release in the 2.0 series. 
+
+New Features
+=============
+
+ This version of |Percona XtraBackup| has implemented full support for new |MySQL| 5.6 features (``GTID``, remote/transportable tablespaces, separate undo tablespace, 5.6-style buffer pool dump files).
+
+ |Percona XtraBackup| has implemented support for the `InnoDB Buffer Pool Preloading <http://dev.mysql.com/doc/refman/5.6/en/innodb-performance.html#innodb-preload-buffer-pool>`_ introduced in |MySQL| 5.6. Starting with |MySQL| 5.6 buffer pool dumps can be produced and loaded for faster server warmup after the start. This feature is similar to the `Dump/Restore of the Buffer Pool <http://www.percona.com/doc/percona-server/5.5/management/innodb_lru_dump_restore.html>`_ in |Percona Server|. |MySQL| 5.6 buffer pool dump is copied into backup directory during the backup stage. During the copy back stage (restore) it is copied back to data directory. After the backup is restored buffer pool dump can be loaded by the server either automatically on startup or on demand.
+
+ Time interval between checks done by log copying thread is now configurable by :option:`innobackupex --log-copy-interval`. Making the interval configurable allows to reduce the time between checks which can prevent |XtraBackup| failures that are caused by the log records in the transactional log being overwritten before they are copied by the log copying thread.
+ 
+ |Percona XtraBackup| now stores the ``GTID`` value in the :file:`xtrabackup_binlog_info` when doing the backup of |MySQL| and |Percona Server| 5.6 with the :option:`innobackupex --slave-info`. Example of how this information can be used to create/restore a slave can be found in `this blogpost <http://www.mysqlperformanceblog.com/2013/02/08/how-to-createrestore-a-slave-using-gtid-replication-in-mysql-5-6/>`_.
+
+ |Percona XtraBackup| option :option:`xtrabackup --export` now supports transportable tablespaces introduced in |MySQL| 5.6. This option can be used to produce 5.6-style metadata files, that can be imported by ``ALTER TABLE IMPORT TABLESPACE`` on |MySQL| and |Percona Server| 5.6 as described in :ref:`export_import_tables` guide.
+
+Bugs Fixed
+==========
+
+ ``xtrabackup_56`` binary was present in ``rpm`` and ``deb`` packages, but it was missing from the source ``.tar.gz`` package. Fixed by adding the missing binary to ``.tar.gz`` as well. Bug fixed :bug:`1158948`.
+
+ |innobackupex| could crash when taking the 5.6 backup due to linking the wrong ``SSL`` library. Bug fixed :bug:`1168540`.
+
+ |Percona XtraBackup| would crash when preparing the 5.6 backup with partitioned tables. Bug fixed :bug:`1169169`.
+
+ Tables that were dropped between taking a full backup and an incremental one were present in the full backup directory, and were not removed when incremental backups has been merged. Fixed by removing files corresponding to tables that are missing in the incremental backup directory. Bug fixed :bug:`856400`.
+
+ |Percona XtraBackup| would leave stale ``xtrabackup_tmp*`` files in the :term:`datadir` after applying incremental backups. Bug fixed :bug:`1079135`.
+
+ Fixed couple of warnings found in |innobackupex| when all warnings have been made ``FATAL``. Bug fixed :bug:`1116177`.
+
+ If there are thousands of tables and slow IO then |Xtrabackup| can spend a lot of time opening all the tablespaces. Optimization has been implemented and |XtraBackup| now avoids loading non-relevant tablespaces when partial backup is being taken which speeds up the backup process. Bug fixed :bug:`1130145`.
+
+ |Percona XtraBackup| didn't initialize per-thread data in the log copying thread which could cause |XtraBackup| to crash. Bug fixed :bug:`1166888`.
+
+ Package dependency has been changed from abstract ``mysql`` to real ``/usr/bin/mysql`` file, because ``rpm`` packages from *Oracle* no longer satisfied ``mysql`` dependency which is required by the |XtraBackup| ``rpms``. Bug fixed :bug:`1095972`.
+
+ |Percona XtraBackup| would fail when preparing the |MySQL| 5.6 backup if the log files were bigger than 4G on the source server. Bug fixed :bug:`1164979`.
+
+ Due to different implementation in |MySQL| 5.6 error messages were not printed to ``stderr`` directly. Because of that all InnoDB error or diagnostic messages are never printed by xtrabackup_56. Bug fixed :bug:`1169971`.
+
+ |innobackupex| would still run with ``FLUSH TABLES WITH READ LOCK`` even if |xtrabackup| would fail when copying logs. Fixed by terminating |xtrabackup| process immediately on log copying failure. Bug fixed :bug:`1170806`.
+
+ |innobackupex| would fail if the ``SQL_MODE`` was set to ``ANSI_QUOTES``.  Bug fixed :bug:`945161`.
+
+ Missing space_id from ``*.ibd.meta`` would lead to assertion. Fixed by replacing the assertion with the error message. Bug fixed :bug:`1112224`.
+
+ Fixed the typo in the |innobackupex| error output. Bug fixed :bug:`1157225`.
+
+ When building from source ``innodb56`` target didn't have an option to disable DTrace like ``innodb55`` has. Fixed by adding ``-DENABLE_DTRACE=OFF`` build option for ``innodb56`` as well. Bug fixed :bug:`1169509`.
+
+ |innobackupex| wasn't handling the :option:`innodb_data_file_path` option which could cause backup to fail. Bug fixed :bug:`1169726`.
+
+ For the *Debian* and the *Linux* binaries, the :option:`--version` message which should include the revision was showing "undefined". Bug fixed :bug:`1171721`.
+
+ Redundant code has been removed from ``xtrabackup.cc``. Bug fixed :bug:`1162765`.
+
+Other bug fixes: bug fixed :bug:`1158154`, bug fixed :bug:`1170340`, bug fixed :bug:`1088309`, bug fixed :bug:`1088307`.
 
=== modified file 'doc/source/xtrabackup_bin/exporting_importing_tables.rst'
--- doc/source/xtrabackup_bin/exporting_importing_tables.rst	2013-03-06 09:17:17 +0000
+++ doc/source/xtrabackup_bin/exporting_importing_tables.rst	2013-05-06 13:57:23 +0000
@@ -1,8 +1,10 @@
+.. _export_import_tables:
+
 ================================
  Exporting and Importing Tables
 ================================
 
-In standard InnoDB, it is not normally possible to copy tables between servers by copying the files, even with :term:`innodb_file_per_table`. However, with the |xtrabackup| binary, you can export individual tables from any |InnoDB| database, and import them into |Percona Server| with |XtraDB|. (The source doesn't have to be |XtraDB|, but the destination does.) This functionality requires :term:`innodb_file_per_table` to be used on both servers, and requires :term:`innodb_expand_import` to be enabled on the destination server. It only works on individual :term:`.ibd` files, and cannot export a table that is not contained in its own :term:`.ibd` file.
+In |InnoDB| versions prior to 5.6, it is not possible to copy tables between servers by copying the files, even with :term:`innodb_file_per_table`. However, with the |xtrabackup| binary, you can export individual tables from any |InnoDB| database, and import them into |Percona Server| with |XtraDB| or |MySQL| 5.6. (The source doesn't have to be |XtraDB| or or |MySQL| 5.6, but the destination does.) This functionality requires :term:`innodb_file_per_table` to be used on both servers, and requires :term:`innodb_expand_import` to be enabled on the destination server. It only works on individual :term:`.ibd` files, and cannot export a table that is not contained in its own :term:`.ibd` file.
 
 Let's see how to export and import the following table: ::
 
@@ -27,19 +29,24 @@
   $ find /data/backups/mysql/ -name export_test.*
   /data/backups/mysql/test/export_test.exp
   /data/backups/mysql/test/export_test.ibd
-
-These two files are all you need to import the table into a server running |Percona Server| with |XtraDB|.
+  /data/backups/mysql/test/export_test.cfg
+
+These three files are all you need to import the table into a server running |Percona Server| with |XtraDB| or |MySQL| 5.6.
+
+.. note:: 
+
+  |MySQL| uses ``.cfg`` file which contains |InnoDB| dictionary dump in special format. This format is different from the ``.exp`` one which is used in |XtraDB| for the same purpose.
 
 Importing the Table
 ===================
 
-On the destination server running |Percona Server| with |XtraDB|, with :term:`innodb_expand_import` enabled, create a table with the same structure, and then perform the following steps:
+On the destination server running |Percona Server| with |XtraDB| and :term:`innodb_expand_import` option enabled, or |MySQL| 5.6, create a table with the same structure, and then perform the following steps:
 
 * Execute ``ALTER TABLE test.export_test DISCARD TABLESPACE;``
   
   * If you see the following message, then you must enable :term:`innodb_file_per_table` and create the table again: ``ERROR 1030 (HY000): Got error -1 from storage engine``
 
-* Copy the exported files to the ``test/`` subdirectory of the destination server's data directory
+* Copy the exported files to the ``test/`` subdirectory of the destination server's data directory 
 
 * Execute ``ALTER TABLE test.export_test IMPORT TABLESPACE;``