Merge lp:~hrvojem/percona-xtrabackup/rn-2.0.8-2.1 into lp:percona-xtrabackup/2.1

[Hrvoje Matijakovic]

[Hrvoje Matijakovic (hrvojem)]

self-approving 2.0 upmerge

review: Approve

=== modified file 'doc/source/conf.py'
--- doc/source/conf.py	2013-08-18 06:54:14 +0000
+++ doc/source/conf.py	2013-08-30 09:58:59 +0000
@@ -106,7 +106,7 @@
 
 .. |LSN|  replace:: :term:`LSN`
 
-.. |XtraBackup|  replace:: *XtraBackup*
+.. |XtraBackup|  replace:: *Percona XtraBackup*
 
 .. |Percona XtraBackup|  replace:: *Percona XtraBackup*
 
@@ -155,7 +155,7 @@
 html_title = 'Percona XtraBackup Documentation'
 
 # A shorter title for the navigation bar.  Default is the same as html_title.
-html_short_title = 'XtraBackup Docs'
+html_short_title = 'Percona XtraBackup Docs'
 
 # The name of an image file (relative to this directory) to place at the top
 # of the sidebar.

=== modified file 'doc/source/faq.rst'
--- doc/source/faq.rst	2013-04-29 09:29:00 +0000
+++ doc/source/faq.rst	2013-08-30 09:58:59 +0000
@@ -2,15 +2,15 @@
  Frequently Asked Questions
 ============================
 
-Do I need an InnoDB Hot Backup license to use XtraBackup?
-=========================================================
+Do I need an InnoDB Hot Backup license to use Percona XtraBackup?
+=================================================================
 
-No. Although ``innobackupex`` is derived from the same GPL and open-source wrapper script that InnoDB Hot Backup uses, it does not execute ``ibbackup``, and the ``xtrabackup`` binary does not execute or link to ``ibbackup``. You can use XtraBackup without any license; it is completely separate from InnoDB Hot Backup.
+No. Although ``innobackupex`` is derived from the same GPL and open-source wrapper script that InnoDB Hot Backup uses, it does not execute ``ibbackup``, and the ``xtrabackup`` binary does not execute or link to ``ibbackup``. You can use |Percona XtraBackup| without any license; it is completely separate from InnoDB Hot Backup.
 
 Why is innobackupex distributed as innobackupex-1.5.1?
 ======================================================
 
-That's the way the source for the tool was distributed from Oracle. Nowadays, it is a symbolic link to |innobackupex| for backward compatibility with |XtraBackup|.
+That's the way the source for the tool was distributed from Oracle. Nowadays, it is a symbolic link to |innobackupex| for backward compatibility with |Percona XtraBackup|.
 
 What's the difference between :program:`innobackupex` and :program:`innobackup`?
 ================================================================================
@@ -39,16 +39,12 @@
 
 However, for some specific tasks, you must use :program:`xtrabackup` directly. See the :ref:`user-manual` for details on each one.
 
-Are you aware of any web-based backup management tools (commercial or not) built around |Xtrabackup|?
-=====================================================================================================
-
-`Zmanda Recovery Manager <http://www.zmanda.com/zrm-mysql-enterprise.html>`_ is a commercial tool that uses XtraBackup for Non-Blocking Backups: *"ZRM provides support for
-non-blocking backups of MySQL using XtraBackup. ZRM with XtraBackup
-provides resource utilization management by providing throttling based
-on the number of IO operations per second. XtraBackup based backups also
-allow for table level recovery even though the backup was done at the
-database level (needs the recovery database server to be Percona Server
-with XtraDB)."*
+Are you aware of any web-based backup management tools (commercial or not) built around |Percona XtraBackup|?
+=============================================================================================================
+
+`Zmanda Recovery Manager <http://www.zmanda.com/zrm-mysql-enterprise.html>`_ is a commercial tool that uses |Percona XtraBackup| for Non-Blocking Backups: 
+
+ *"ZRM provides support for non-blocking backups of MySQL using |Percona XtraBackup|. ZRM with |Percona XtraBackup| provides resource utilization management by providing throttling based on the number of IO operations per second. |Percona XtraBackup| based backups also allow for table level recovery even though the backup was done at the database level (needs the recovery database server to be |Percona Server| with XtraDB)."*
 
 |xtrabackup| binary fails with a floating point exception
 =========================================================

=== modified file 'doc/source/glossary.rst'
--- doc/source/glossary.rst	2013-04-29 09:29:00 +0000
+++ doc/source/glossary.rst	2013-08-30 09:58:59 +0000
@@ -18,7 +18,7 @@
       or start the server with ``--innodb_file_per_table``.
 
    innodb_expand_import
-     This feature of |Percona Server| implements the ability to import arbitrary :term:`.ibd` files exported using the |XtraBackup| :option:`--export` option.
+     This feature of |Percona Server| implements the ability to import arbitrary :term:`.ibd` files exported using the |Percona XtraBackup| :option:`--export` option.
      
      See the `the full documentation <http://www.percona.com/doc/percona-server/5.5/management/innodb_expand_import.html>`_ for more information.
 
@@ -70,7 +70,7 @@
     The directory in which the database server stores its databases. Most Linux distribution use :file:`/var/lib/mysql` by default.
 
    xbstream
-     To support simultaneous compression and streaming, a new custom streaming format called xbstream was introduced to XtraBackup in addition to the TAR format. 
+     To support simultaneous compression and streaming, a new custom streaming format called xbstream was introduced to |Percona XtraBackup| in addition to the TAR format. 
 
    ibdata
      Default prefix for tablespace files, e.g. :file:`ibdata1` is a 10MB  autoextensible file that |MySQL| creates for the shared tablespace by default. 
@@ -88,7 +88,7 @@
      Each |MyISAM| table has ``.MYI`` (MYIndex) file which contains the table's indexes.
 
    .exp
-     When :doc:`exporting a table <xtrabackup_bin/exporting_importing_tables>` with |XtraBackup|, it creates a file with ``.exp`` extension per exported table containing the information for importing it.
+     When :doc:`exporting a table <xtrabackup_bin/exporting_importing_tables>` with |Percona XtraBackup|, it creates a file with ``.exp`` extension per exported table containing the information for importing it.
 
    .MRG
      Each table using the :program:`MERGE` storage engine, besides of a :term:`.frm` file, will have :term:`.MRG` file containing the names of the |MyISAM| tables associated with it.

=== modified file 'doc/source/how_xtrabackup_works.rst'
--- doc/source/how_xtrabackup_works.rst	2012-11-19 02:09:59 +0000
+++ doc/source/how_xtrabackup_works.rst	2013-08-30 09:58:59 +0000
@@ -1,14 +1,14 @@
-========================
- How |XtraBackup| Works
-========================
+================================
+ How |Percona XtraBackup| Works
+================================
 
-|XtraBackup| is based on :term:`InnoDB`'s crash-recovery functionality. It copies your |InnoDB| data files, which results in data that is internally inconsistent; but then it performs crash recovery on the files to make them a consistent, usable database again.
+|Percona XtraBackup| is based on :term:`InnoDB`'s crash-recovery functionality. It copies your |InnoDB| data files, which results in data that is internally inconsistent; but then it performs crash recovery on the files to make them a consistent, usable database again.
 
 This works because |InnoDB| maintains a redo log, also called the transaction log. This contains a record of every change to InnoDB's data. When |InnoDB| starts, it inspects the data files and the transaction log, and performs two steps. It applies committed transaction log entries to the data files, and it performs an undo operation on any transactions that modified data but did not commit.
 
-|XtraBackup| works by remembering the log sequence number (:term:`LSN`) when it starts, and then copying away the data files. It takes some time to do this, so if the files are changing, then they reflect the state of the database at different points in time. At the same time, |XtraBackup| runs a background process that watches the transaction log files, and copies changes from it. |XtraBackup| needs to do this continually because the transaction logs are written in a round-robin fashion, and can be reused after a while. |XtraBackup| needs the transaction log records for every change to the data files since it began execution.
+|Percona XtraBackup| works by remembering the log sequence number (:term:`LSN`) when it starts, and then copying away the data files. It takes some time to do this, so if the files are changing, then they reflect the state of the database at different points in time. At the same time, |Percona XtraBackup| runs a background process that watches the transaction log files, and copies changes from it. |Percona XtraBackup| needs to do this continually because the transaction logs are written in a round-robin fashion, and can be reused after a while. |Percona XtraBackup| needs the transaction log records for every change to the data files since it began execution.
 
-The above is the backup process. Next is the prepare process. During this step, |XtraBackup| performs crash recovery against the copied data files, using the copied transaction log file. After this is done, the database is ready to restore and use.
+The above is the backup process. Next is the prepare process. During this step, |Percona XtraBackup| performs crash recovery against the copied data files, using the copied transaction log file. After this is done, the database is ready to restore and use.
 
 The above process is implemented in the |xtrabackup| compiled binary program. The |innobackupex| program adds more convenience and functionality by also permitting you to back up |MyISAM| tables and :term:`.frm` files. It starts |xtrabackup|, waits until it finishes copying files, and then issues ``FLUSH TABLES WITH READ LOCK`` to prevent further changes to |MySQL|'s data and flush all |MyISAM| tables to disk. It holds this lock, copies the |MyISAM| files, and then releases the lock.
 

=== modified file 'doc/source/howtos/recipes_ibkx_partition.rst'
--- doc/source/howtos/recipes_ibkx_partition.rst	2013-07-24 09:15:20 +0000
+++ doc/source/howtos/recipes_ibkx_partition.rst	2013-08-30 09:58:59 +0000
@@ -2,7 +2,7 @@
  Backing Up and Restoring Individual Partitions
 ================================================
 
-|XtraBackup| features :doc:`partial backups <../innobackupex/partial_backups_innobackupex>`, which means that you may backup individual partitions as well because from the storage engines perspective partitions are regular tables with specially formatted names. The only requirement for this feature is having the :term:`innodb_file_per_table` option enabled in the server.
+|Percona XtraBackup| features :doc:`partial backups <../innobackupex/partial_backups_innobackupex>`, which means that you may backup individual partitions as well because from the storage engines perspective partitions are regular tables with specially formatted names. The only requirement for this feature is having the :term:`innodb_file_per_table` option enabled in the server.
 
 There is only one caveat about using this kind of backup: you can't copy back the prepared backup. Restoring partial backups should be done by importing the tables, and not by using the traditional :option:`--copy-back` option. Although there are some scenarios where restoring can be done by copying back the files, this may be lead to database inconsistencies in many cases and it is not the recommended way to do it.
 

=== modified file 'doc/source/howtos/setting_up_replication.rst'
--- doc/source/howtos/setting_up_replication.rst	2013-07-31 10:55:11 +0000
+++ doc/source/howtos/setting_up_replication.rst	2013-08-30 09:58:59 +0000
@@ -1,19 +1,19 @@
 .. _replication_howto:
 
-========================================================================
- How to setup a slave for replication in 6 simple steps with Xtrabackup
-========================================================================
-
-  Data is, by far, the most valuable part of a system. Having a backup done systematically and available for a rapid recovery in case of failure is admittedly essential to a system. However, it is not common practice because of its costs, infrastructure needed or even the boredom associated to the task. Xtrabackup is designed to solve this problem.
-
-  You can have almost real-time backups in 6 simple steps by setting up a replication environment with |XtraBackup|. 
-
- *Percona* |XtraBackup| is a tool for backing up your data extremely easy and without interruption. It performs "hot backups" on unmodified versions of |MySQL| servers (5.1, 5.5 and 5.6), as well as |MariaDB| and *Percona Servers*. It is a totally free and open source software distributed only under the *GPLv2* license.
+================================================================================
+ How to setup a slave for replication in 6 simple steps with Percona XtraBackup
+================================================================================
+
+  Data is, by far, the most valuable part of a system. Having a backup done systematically and available for a rapid recovery in case of failure is admittedly essential to a system. However, it is not common practice because of its costs, infrastructure needed or even the boredom associated to the task. |Percona XtraBackup| is designed to solve this problem.
+
+  You can have almost real-time backups in 6 simple steps by setting up a replication environment with |Percona XtraBackup|. 
+
+ |Percona XtraBackup| is a tool for backing up your data extremely easy and without interruption. It performs "hot backups" on unmodified versions of |MySQL| servers (5.1, 5.5 and 5.6), as well as |MariaDB| and *Percona Servers*. It is a totally free and open source software distributed only under the *GPLv2* license.
 
 All the things you will need
 ============================
 
-Setting up a slave for replication with |XtraBackup| is really a very straightforward procedure. In order to keep it simple, here is a list of the things you need to follow the steps without hassles:
+Setting up a slave for replication with |Percona XtraBackup| is really a very straightforward procedure. In order to keep it simple, here is a list of the things you need to follow the steps without hassles:
 
 * ``TheMaster`` 
   A system with a |MySQL|-based server installed, configured and running. This system will be called ``TheMaster``, as it is where your data is stored and the one to be replicated. We will assume the following about this system:
@@ -32,7 +32,7 @@
 * ``TheSlave`` 
   Another system, with a |MySQL|-based server installed on it. We will refer to this machine as ``TheSlave`` and we will assume the same things we did about ``TheMaster``, except that the server-id on ``TheSlave`` is 2.
 
-* ``Xtrabackup``
+* ``Percona XtraBackup``
   The backup tool we will use. It should be installed in both computers for convenience.
 
 STEP 1: Make a backup on ``TheMaster`` and prepare it
@@ -50,7 +50,7 @@
 
    innobackupex: completed OK! 
 
-This will make a copy of your |MySQL| data dir to the /path/to/backupdir/$TIMESTAMP. You have told |XtraBackup| (through the |innobackupex| script) to connect to the database server using your database user and password, and do a hot backup of all your data in it (all |MyISAM|, |InnoDB| tables and indexes in them).
+This will make a copy of your |MySQL| data dir to the /path/to/backupdir/$TIMESTAMP. You have told |Percona XtraBackup| (through the |innobackupex| script) to connect to the database server using your database user and password, and do a hot backup of all your data in it (all |MyISAM|, |InnoDB| tables and indexes in them).
 
 In order for snapshot to be consistent you need to prepare the data:
 
@@ -61,7 +61,7 @@
 
 You need to select path where your snapshot has been taken, for example /home/backups/2012-01-16_11-14-43. If everything is ok you should get the same OK message. Now the transaction logs are applied to the data files, and new ones are created: your data files are ready to be used by the MySQL server.
 
-|XtraBackup| knows where your data is by reading your :term:`my.cnf`. If you have your configuration file in a non-standard place, you should use the flag :option:`--defaults-file` ``=/location/of/my.cnf``.
+|Percona XtraBackup| knows where your data is by reading your :term:`my.cnf`. If you have your configuration file in a non-standard place, you should use the flag :option:`--defaults-file` ``=/location/of/my.cnf``.
 
 If you want to skip writing the username/password every time you want to access |MySQL|, you can set it up in your $HOME folder. Just edit .my.cnf and add:
 
@@ -187,7 +187,7 @@
 Adding more slaves to The Master
 ================================
 
-You can use this procedure with slight variation to add new slaves to a master. We will use |Xtrabackup| to clone an already configured slave. We will continue using the previous scenario for convenience but we will add ``TheNewSlave`` to the plot.
+You can use this procedure with slight variation to add new slaves to a master. We will use |Percona XtraBackup| to clone an already configured slave. We will continue using the previous scenario for convenience but we will add ``TheNewSlave`` to the plot.
 
 At ``TheSlave``, do a full backup:
 
@@ -196,7 +196,7 @@
    TheSlave$ innobackupex --user=yourDBuser --password=MaGiCiGaM /
              --slave-info /path/to/backupdir 
 
-By using the :option:`--slave-info` Xtrabackup creates additional file called :file:`xtrabackup_slave_info`.
+By using the :option:`--slave-info` |Percona XtraBackup| creates additional file called :file:`xtrabackup_slave_info`.
 
 Apply the logs:
 

=== modified file 'doc/source/innobackupex/compact_backups_innobackupex.rst'
--- doc/source/innobackupex/compact_backups_innobackupex.rst	2013-07-25 20:00:02 +0000
+++ doc/source/innobackupex/compact_backups_innobackupex.rst	2013-08-30 09:58:59 +0000
@@ -64,11 +64,11 @@
     Dropping 4 index(es).
     Rebuilding 4 index(es).
 
-Since |XtraBackup| has no information when applying an incremental backup to a compact full one, on whether there will be more incremental backups applied to it later or not, rebuilding indexes needs to be explicitly requested by a user whenever a full backup with some incremental backups merged is ready to be restored. Rebuilding indexes unconditionally on every incremental backup merge is not an option, since it is an expensive operation.
+Since |Percona XtraBackup| has no information when applying an incremental backup to a compact full one, on whether there will be more incremental backups applied to it later or not, rebuilding indexes needs to be explicitly requested by a user whenever a full backup with some incremental backups merged is ready to be restored. Rebuilding indexes unconditionally on every incremental backup merge is not an option, since it is an expensive operation.
 
 .. note::
 
-  To process individual tables in parallel when rebuilding indexes, :option:`innobackupex --rebuild-threads` option can be used to specify the number of threads started by XtraBackup when rebuilding secondary indexes on --apply-log --rebuild-indexes. Each thread rebuilds indexes for a single ``.ibd`` tablespace at a time.
+  To process individual tables in parallel when rebuilding indexes, :option:`innobackupex --rebuild-threads` option can be used to specify the number of threads started by |Percona XtraBackup| when rebuilding secondary indexes on --apply-log --rebuild-indexes. Each thread rebuilds indexes for a single ``.ibd`` tablespace at a time.
 
 Restoring Compact Backups
 =========================

=== modified file 'doc/source/innobackupex/how_innobackupex_works.rst'
--- doc/source/innobackupex/how_innobackupex_works.rst	2013-04-29 11:08:57 +0000
+++ doc/source/innobackupex/how_innobackupex_works.rst	2013-08-30 09:58:59 +0000
@@ -25,7 +25,7 @@
 
 .. note:: 
 
-  Locking is done only for MyISAM and other non-InnoDB tables, and only **after** XtraBackup is finished backing up all InnoDB/XtraDB data and logs.
+  Locking is done only for MyISAM and other non-InnoDB tables, and only **after** |Percona XtraBackup| is finished backing up all InnoDB/XtraDB data and logs.
 
 Once this is done, the backup of the files will begin. It will backup :term:`.frm`, :term:`.MRG`, :term:`.MYD`, :term:`.MYI`, :term:`.TRG`, :term:`.TRN`, :term:`.ARM`, :term:`.ARZ`, :term:`.CSM`, :term:`.CSV`, ``.par``,  and :term:`.opt` files.
 

=== modified file 'doc/source/innobackupex/innobackupex_option_reference.rst'
--- doc/source/innobackupex/innobackupex_option_reference.rst	2013-08-01 08:54:47 +0000
+++ doc/source/innobackupex/innobackupex_option_reference.rst	2013-08-30 09:58:59 +0000
@@ -100,7 +100,7 @@
 
 .. option:: --ibbackup=IBBACKUP-BINARY
 
-   This option accepts a string argument that specifies which |xtrabackup| binary should be used. The string should be the command used to run *XtraBackup*. The option can be useful if the :program:`xtrabackup` binary is not in your search path or working directory and the database server is not accessible at the moment. If this option is not specified, :program:`innobackupex` attempts to determine the binary to use automatically. By default, :program:`xtrabackup` is the command used. When option :option:`--apply-log` is specified, the binary is used whose name is in the file :file:`xtrabackup_binary` in the backup directory, if that file exists, or will attempt to autodetect it. However, if :option:`--copy-back` or :option:`--move-back` is used, :program:`xtrabackup` is used unless other is specified.
+   This option accepts a string argument that specifies which |xtrabackup| binary should be used. The string should be the command used to run |Percona XtraBackup|. The option can be useful if the :program:`xtrabackup` binary is not in your search path or working directory and the database server is not accessible at the moment. If this option is not specified, :program:`innobackupex` attempts to determine the binary to use automatically. By default, :program:`xtrabackup` is the command used. When option :option:`--apply-log` is specified, the binary is used whose name is in the file :file:`xtrabackup_binary` in the backup directory, if that file exists, or will attempt to autodetect it. However, if :option:`--copy-back` or :option:`--move-back` is used, :program:`xtrabackup` is used unless other is specified.
 
 .. option:: --include=REGEXP
 
@@ -213,7 +213,7 @@
 
 .. option:: --stream=STREAMNAME
 
-   This option accepts a string argument that specifies the format in which to do the streamed backup. The backup will be done to ``STDOUT`` in the specified format. Currently, supported formats are `tar` and `xbstream`. Uses :doc:`xbstream <../xbstream/xbstream>`, which is available in *XtraBackup* distributions. If you specify a path after this option, it will be interpreted as the value of :option:`tmpdir`
+   This option accepts a string argument that specifies the format in which to do the streamed backup. The backup will be done to ``STDOUT`` in the specified format. Currently, supported formats are `tar` and `xbstream`. Uses :doc:`xbstream <../xbstream/xbstream>`, which is available in |Percona XtraBackup| distributions. If you specify a path after this option, it will be interpreted as the value of :option:`tmpdir`
 
 .. option:: --tables-file=FILE
 

=== modified file 'doc/source/innobackupex/partial_backups_innobackupex.rst'
--- doc/source/innobackupex/partial_backups_innobackupex.rst	2013-04-29 09:29:00 +0000
+++ doc/source/innobackupex/partial_backups_innobackupex.rst	2013-08-30 09:58:59 +0000
@@ -2,7 +2,7 @@
  Partial Backups
 =================
 
-|XtraBackup| features partial backups, which means that you may backup only some specific tables or databases. The tables you back up must be in separate tablespaces, as a result of being created or altered after you enabled the :term:`innodb_file_per_table` option on the server.
+|Percona XtraBackup| features partial backups, which means that you may backup only some specific tables or databases. The tables you back up must be in separate tablespaces, as a result of being created or altered after you enabled the :term:`innodb_file_per_table` option on the server.
 
 There is only one caveat about partial backups: do not copy back the prepared backup. Restoring partial backups should be done by importing the tables, not by using the traditional :option:`--copy-back` option. Although there are some scenarios where restoring can be done by copying back the files, this may be lead to database inconsistencies in many cases and it is not the recommended way to do it.
 
@@ -52,7 +52,7 @@
 
 .. note:: 
  
- Currently in XtraBackup the --databases option has no effect for InnoDB files for both local and streaming backups, i.e. all InnoDB files are always backed up. Currently, only .frm and non-InnoDB tables are limited by that option.
+ Currently in |Percona XtraBackup| the --databases option has no effect for InnoDB files for both local and streaming backups, i.e. all InnoDB files are always backed up. Currently, only .frm and non-InnoDB tables are limited by that option.
 
 Preparing Partial Backups
 =========================

=== modified file 'doc/source/innobackupex/privileges.rst'
--- doc/source/innobackupex/privileges.rst	2013-04-29 11:08:57 +0000
+++ doc/source/innobackupex/privileges.rst	2013-08-30 09:58:59 +0000
@@ -2,7 +2,7 @@
  Connection and Privileges Needed
 ==================================
 
-|XtraBackup| needs to be able to connect to the database server and perform operations on the server and the :term:`datadir` when creating a backup, when preparing in some scenarios and when restoring it. In order to do so, there are privileges and permission requirements on its execution that must be fulfilled.
+|Percona XtraBackup| needs to be able to connect to the database server and perform operations on the server and the :term:`datadir` when creating a backup, when preparing in some scenarios and when restoring it. In order to do so, there are privileges and permission requirements on its execution that must be fulfilled.
 
 Privileges refers to the operations that a system user is permitted to do in the database server. **They are set at the database server and only apply to users in the database server**.
 
@@ -21,7 +21,7 @@
   $ innobackupex --user=LUKE  --password=US3TH3F0RC3 --stream=tar ./ | bzip2 - 
   $ xtrabackup --user=DVADER --password=14MY0URF4TH3R --backup --target-dir=/data/bkps/
 
-If you don't use the :option:`--user` option, |XtraBackup| will assume the database user whose name is the system user executing it.
+If you don't use the :option:`--user` option, |Percona XtraBackup| will assume the database user whose name is the system user executing it.
 
 Other Connection Options
 ------------------------

=== modified file 'doc/source/innobackupex/restoring_a_backup_ibk.rst'
--- doc/source/innobackupex/restoring_a_backup_ibk.rst	2013-04-29 09:29:00 +0000
+++ doc/source/innobackupex/restoring_a_backup_ibk.rst	2013-08-30 09:58:59 +0000
@@ -14,7 +14,7 @@
 
 .. note:: 
 
- The :term:`datadir` must be empty; XtraBackup :option:`--copy-back` option will not copy over existing files. Also it's important to note that MySQL server needs to be shut down before restore is performed. You can't restore to a :term:`datadir` of a running mysqld instance (except when importing a partial backup). 
+ The :term:`datadir` must be empty; |Percona XtraBackup| :option:`innobackupex --copy-back` option will not copy over existing files. Also it's important to note that MySQL server needs to be shut down before restore is performed. You can't restore to a :term:`datadir` of a running mysqld instance (except when importing a partial backup). 
 
 As files' attributes will be preserved, in most cases you will need to change the files’ ownership to ``mysql`` before starting the database server, as they will be owned by the user who created the backup::
 

=== modified file 'doc/source/innobackupex/streaming_backups_innobackupex.rst'
--- doc/source/innobackupex/streaming_backups_innobackupex.rst	2013-07-25 20:00:02 +0000
+++ doc/source/innobackupex/streaming_backups_innobackupex.rst	2013-08-30 09:58:59 +0000
@@ -2,7 +2,7 @@
  Streaming and Compressing Backups
 ===================================
 
-Streaming mode, supported by |XtraBackup|, sends backup to ``STDOUT`` in special ``tar`` or |xbstream| format instead of copying files to the backup directory.
+Streaming mode, supported by |Percona XtraBackup|, sends backup to ``STDOUT`` in special ``tar`` or |xbstream| format instead of copying files to the backup directory.
 
 This allows you to use other programs to filter the output of the backup, providing greater flexibility for storage of the backup. For example, compression is achieved by piping the output to a compression utility. One of the benefits of streaming backups and using Unix pipes is that the backups can be automatically encrypted. 
 
@@ -46,7 +46,7 @@
 
  $ innobackupex --stream=tar ./ | ssh user@destination \ "cat - > /data/backups/backup.tar"
 
-.. warning::  To extract |XtraBackup|'s archive you **must** use |tar| with ``-i`` option::
+.. warning::  To extract |Percona XtraBackup|'s archive you **must** use |tar| with ``-i`` option::
 
   $ tar -xizf backup.tar.gz
 

=== modified file 'doc/source/installation.rst'
--- doc/source/installation.rst	2013-06-19 08:48:19 +0000
+++ doc/source/installation.rst	2013-08-30 09:58:59 +0000
@@ -1,10 +1,10 @@
-=======================================
- Installing |XtraBackup| from Binaries
-=======================================
+===============================================
+ Installing |Percona XtraBackup| from Binaries
+===============================================
 
 Before installing, you might want to read the :doc:`release-notes`.
 
-Ready-to-use binaries are available from the |XtraBackup| `download page <http://www.percona.com/downloads/XtraBackup/>`_, including:
+Ready-to-use binaries are available from the |Percona XtraBackup| `download page <http://www.percona.com/downloads/XtraBackup/>`_, including:
 
  * ``RPM`` packages for *RHEL* 5 and *RHEL* 6 (including compatible distributions such as CentOS and Oracle Enterprise Linux)
 
@@ -21,6 +21,6 @@
    installation/apt_repo
    installation/yum_repo
 
-|Percona| provides repositories for :program:`yum` (``RPM`` packages for *Red Hat Enterprise Linux* and compatible distributions such as *CentOS*, *Oracle Enterprise Linux*, *Amazon Linux AMI*, and *Fedora*) and :program:`apt` (:file:`.deb` packages for *Ubuntu* and *Debian*) for software such as |Percona Server|, |XtraDB|, |XtraBackup|, and |Percona Toolkit|. This makes it easy to install and update your software and its dependencies through your operating system's package manager.
+|Percona| provides repositories for :program:`yum` (``RPM`` packages for *Red Hat Enterprise Linux* and compatible distributions such as *CentOS*, *Oracle Enterprise Linux*, *Amazon Linux AMI*, and *Fedora*) and :program:`apt` (:file:`.deb` packages for *Ubuntu* and *Debian*) for software such as |Percona Server|, |XtraDB|, |Percona XtraBackup|, and |Percona Toolkit|. This makes it easy to install and update your software and its dependencies through your operating system's package manager.
 
 This is the recommend way of installing where possible.

=== modified file 'doc/source/installation/compiling_xtrabackup.rst'
--- doc/source/installation/compiling_xtrabackup.rst	2013-04-30 07:47:49 +0000
+++ doc/source/installation/compiling_xtrabackup.rst	2013-08-30 09:58:59 +0000
@@ -15,7 +15,7 @@
 Prerequisites
 -------------
 
-The following packages and tools must be installed to compile *Percona XtraBackup* from source. These might vary from system to system.
+The following packages and tools must be installed to compile |Percona XtraBackup| from source. These might vary from system to system.
 
 In Debian-based distributions, you need to: ::
 
@@ -44,7 +44,7 @@
   innodb56           5.6        build against InnoDB in MySQL 5.6
   ================== =========  ============================================
 
-Note that the script must be executed from the base directory of |Xtrabackup| sources, and that directory must contain the packages with the source code of the codebase selected. This may appear cumbersome, but if the variable ``AUTO_LOAD="yes"`` is set, the :command:`build.sh` script will download all the source code needed for the build.
+Note that the script must be executed from the base directory of |Percona XtraBackup| sources, and that directory must contain the packages with the source code of the codebase selected. This may appear cumbersome, but if the variable ``AUTO_LOAD="yes"`` is set, the :command:`build.sh` script will download all the source code needed for the build.
 
 .. note:: 
   The exact versions expected by build.sh script should be used. Changing the version info in build.sh to have it build against a different server version is not supported.
@@ -65,6 +65,6 @@
   innodb56           5.6        http://s3.amazonaws.com/percona.com/downloads/community/mysql-5.6.10.tar.gz
   ================== =========  ===========================================================================
 
-After the build has finished |XtraBackup| will be ready to be used. The |xtrabackup| binary will be located in the ``percona-xtrabackup/src`` subdirectory.
+After the build has finished |Percona XtraBackup| will be ready to be used. The |xtrabackup| binary will be located in the ``percona-xtrabackup/src`` subdirectory.
 
-After this you’ll need to copy |innobackupex| (in the root folder used to retrieve |XtraBackup|) and the corresponding xtrabackup binary (in the src folder) to some directory listed in the PATH environment variable, e.g. ``/usr/bin``.
+After this you’ll need to copy |innobackupex| (in the root folder used to retrieve |Percona XtraBackup|) and the corresponding xtrabackup binary (in the src folder) to some directory listed in the PATH environment variable, e.g. ``/usr/bin``.

=== modified file 'doc/source/intro.rst'
--- doc/source/intro.rst	2013-04-29 11:08:57 +0000
+++ doc/source/intro.rst	2013-08-30 09:58:59 +0000
@@ -17,9 +17,9 @@
 
 |XtraBackup| makes |MySQL| hot backups for all versions of |Percona Server|, |MySQL|, |MariaDB|, and |Drizzle|. It performs streaming, compressed, and incremental |MySQL| backups.
 
-|Percona| |XtraBackup| works with |MySQL|, |MariaDB|, |Percona Server|, and |Drizzle| databases (support for |Drizzle| is beta). It supports completely non-blocking backups of |InnoDB|, |XtraDB|, and *HailDB* storage engines. In addition, it can back up the following storage engines by briefly pausing writes at the end of the backup: |MyISAM|, :term:`Merge <.MRG>`, and :term:`Archive <.ARM>`, including partitioned tables, triggers, and database options.
+|Percona XtraBackup| works with |MySQL|, |MariaDB|, |Percona Server|, and |Drizzle| databases (support for |Drizzle| is beta). It supports completely non-blocking backups of |InnoDB|, |XtraDB|, and *HailDB* storage engines. In addition, it can back up the following storage engines by briefly pausing writes at the end of the backup: |MyISAM|, :term:`Merge <.MRG>`, and :term:`Archive <.ARM>`, including partitioned tables, triggers, and database options.
 
-Percona's enterprise-grade commercial `MySQL Support <http://www.percona.com/mysql-support/>`_ contracts include support for XtraBackup. We recommend support for critical production deployments.
+Percona's enterprise-grade commercial `MySQL Support <http://www.percona.com/mysql-support/>`_ contracts include support for |Percona XtraBackup|. We recommend support for critical production deployments.
 
 MySQL Backup Tool Feature Comparison
 ====================================
@@ -77,7 +77,7 @@
 What are the features of Percona XtraBackup?
 ============================================
 
-Here is a short list of |XtraBackup| features. See the documentation for more.
+Here is a short list of |Percona XtraBackup| features. See the documentation for more.
 
 * Create hot |InnoDB| backups without pausing your database
 * Make incremental backups of |MySQL|
@@ -92,10 +92,10 @@
 
 .. [#n-1] |MyISAM| backups require a table lock.
 
-.. [#n-2] |XtraBackup| performs throttling based on the number of IO operations per second. *MySQL Enterprise Backup* supports a configurable sleep time between operations.
-
-.. [#n-3] |XtraBackup| tunes the operating system buffers to avoid swapping. See the documentation.
-
-.. [#n-4] |XtraBackup| is linked against the |MySQL| client libraries, so it behaves the same as standard |MySQL| command-line programs. *MySQL Enterprise Backup* has its own command-line and configuration-file behaviors.
+.. [#n-2] |Percona XtraBackup| performs throttling based on the number of IO operations per second. *MySQL Enterprise Backup* supports a configurable sleep time between operations.
+
+.. [#n-3] |Percona XtraBackup| tunes the operating system buffers to avoid swapping. See the documentation.
+
+.. [#n-4] |Percona XtraBackup| is linked against the |MySQL| client libraries, so it behaves the same as standard |MySQL| command-line programs. *MySQL Enterprise Backup* has its own command-line and configuration-file behaviors.
 
 

=== modified file 'doc/source/manindex.rst'
--- doc/source/manindex.rst	2013-06-19 08:48:19 +0000
+++ doc/source/manindex.rst	2013-08-30 09:58:59 +0000
@@ -7,13 +7,13 @@
  Percona Xtrabackup - Documentation
 ====================================
 
-*Percona* |XtraBackup| is an open-source hot backup utility for |MySQL| - based servers that doesn't lock your database during the backup. 
+|Percona XtraBackup| is an open-source hot backup utility for |MySQL| - based servers that doesn't lock your database during the backup. 
 
 It can back up data from |InnoDB|, |XtraDB|, and |MyISAM| tables on unmodified |MySQL| 5.1 and 5.5 servers, as well as |Percona Server| with |XtraDB|. For a high-level overview of many of its advanced features, including a feature comparison, please see :doc:`intro`.
 
-Whether it is a 24x7 highly loaded server or a low-transaction-volume environment, *Percona* |XtraBackup| is designed to make backups a seamless procedure without disrupting the performance of the server in a production environment. `Commercial support contracts are available <http://www.percona.com/mysql-support/>`_.
+Whether it is a 24x7 highly loaded server or a low-transaction-volume environment, |Percona XtraBackup| is designed to make backups a seamless procedure without disrupting the performance of the server in a production environment. `Commercial support contracts are available <http://www.percona.com/mysql-support/>`_.
 
-*Percona* |XtraBackup| is a combination of the |xtrabackup| *C* program, and the |innobackupex| *Perl* script. The |xtrabackup| program copies and manipulates |InnoDB| and |XtraDB| data files, and the *Perl* script enables enhanced functionality, such as interacting with a running |MySQL| server and backing up |MyISAM| tables. |XtraBackup| works with unmodified |MySQL| servers, as well as |Percona Server| with |XtraDB|. It runs on *Linux* and *FreeBSD*. 
+|Percona XtraBackup| is a combination of the |xtrabackup| *C* program, and the |innobackupex| *Perl* script. The |xtrabackup| program copies and manipulates |InnoDB| and |XtraDB| data files, and the *Perl* script enables enhanced functionality, such as interacting with a running |MySQL| server and backing up |MyISAM| tables. |Percona XtraBackup| works with unmodified |MySQL| servers, as well as |Percona Server| with |XtraDB|. It runs on *Linux* and *FreeBSD*. 
 
 Introduction
 ============

=== modified file 'doc/source/manual.rst'
--- doc/source/manual.rst	2013-03-29 10:33:27 +0000
+++ doc/source/manual.rst	2013-08-30 09:58:59 +0000
@@ -14,7 +14,7 @@
    xbcrypt/xbcrypt
    how_xtrabackup_works
 
-|XtraBackup| is a set of following tools:
+|Percona XtraBackup| is a set of following tools:
 
 :doc:`innobackupex <innobackupex/innobackupex_script>`
     a wrapper script that provides functionality to backup a whole |MySQL| database instance with :term:`MyISAM`, :term:`InnoDB`, and :term:`XtraDB` tables.

=== modified file 'doc/source/percona-theme/layout.html'
--- doc/source/percona-theme/layout.html	2013-07-24 09:33:08 +0000
+++ doc/source/percona-theme/layout.html	2013-08-30 09:58:59 +0000
@@ -214,9 +214,9 @@
     <div class="logo"><a href="http://www.percona.com/" onfocus="this.blur()"><img src="http://s3.percona.com/ui-logo.png" alt="Percona Performance Consulting Experts" width="220" height="55" /></a></div>
     <div class="right">
       <div class="searchlink"><a onmouseover="SEARCH.Open()"><img id="searchlink-anchor" src="http://s2.percona.com/ui-search.png" alt="" /></a></div>
-      <span class="inv"><![CDATA[<noindex>]]></span>
-     	<div class="navicontainer"><div class="navi">
-      <span id="navilink-span-menu-914"><a href="http://www.percona.com/about-percona" id="navilink-a-menu-914">About</a></span><span id="navilink-span-menu-915"><a href="http://www.percona.com/products" id="navilink-a-menu-915">Products</a></span><span id="navilink-span-menu-1125"><a href="http://www.percona.com/software" title="" id="navilink-a-menu-1125">Software</a></span><span id="navilink-span-menu-918"><a href="http://www.percona.com/resources" id="navilink-a-menu-918">Resources</a></span><span id="navilink-span-menu-919"><a href="http://www.percona.com/news-and-events" title="" id="navilink-a-menu-919">News/Events</a></span><span id="navilink-span-menu-1129"><a href="http://www.percona.com/percona-community" id="navilink-a-menu-1129">Community</a></span><span id="navilink-span-menu-920"><a href="http://www.percona.com/contact" title="" id="navilink-a-menu-920">Contact</a></span><span id="navilink-span-menu-1060"><a href="http://www.percona.com/live" title="" id="navilink-a-menu-1060">Percona Live</a></span>        </div></div>
+        <span class="inv"><![CDATA[<noindex>]]></span>
+        <div class="navicontainer"><div class="navi">
+      <span id="navilink-span-menu-914"><a href="http://www.percona.com/about-percona" id="navilink-a-menu-914">About</a></span><span id="navilink-span-menu-915"><a href="http://www.percona.com/products" id="navilink-a-menu-915">Products</a></span><span id="navilink-span-menu-1125"><a href="http://www.percona.com/software" title="" id="navilink-a-menu-1125">Software</a></span><span id="navilink-span-menu-918"><a href="http://www.percona.com/resources" id="navilink-a-menu-918">Resources</a></span><span id="navilink-span-menu-919"><a href="http://www.percona.com/news-and-events" title="Get all of the latest Percona news, events and press releases on the MySQL community. Update yourself with the latest MySQL and MariaDB developments today." id="navilink-a-menu-919">News/Events</a></span><span id="navilink-span-menu-1129"><a href="http://www.percona.com/percona-community" id="navilink-a-menu-1129">Community</a></span><span id="navilink-span-menu-920"><a href="http://www.percona.com/contact" title="" id="navilink-a-menu-920">Contact</a></span><span id="navilink-span-menu-1060"><a href="http://www.percona.com/live" title="" id="navilink-a-menu-1060">Percona Live</a></span>       </div></div>
         <span class="inv"><![CDATA[</noindex>]]></span>
 	    </div>
   	</div></div><!-- /.header /#header -->
@@ -329,12 +329,12 @@
 {%- endblock %}
 <span class="inv"><!--[CDATA[<noindex-->]]&gt;</span>
 <div id="submenus"> 
-<div class="navi-dropdown" id="navi-dropdown-menu-914"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/about-us/our-mission">Mission</a></div><div class="item"><a href="http://www.percona.com/about-us/our-team">Team</a></div><div class="item"><a href="http://www.percona.com/about-us/customers">Customers</a></div><div class="item"><a href="http://www.percona.com/about-us/careers">Careers</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-915"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/mysql-support">MySQL Support</a></div><div class="item"><a href="http://www.percona.com/mysql-consulting">MySQL Consulting</a></div><div class="item"><a href="http://www.percona.com/training">MySQL Training</a></div><div class="item"><a href="http://www.percona.com/products/mysql-remote-dba">MySQL Remote DBA</a></div><div class="item"><a href="http://www.percona.com/development">MySQL Server Development</a></div><div class="item"><a href="http://www.percona.com/mysql-5.6-solutions-from-percona">MySQL 5.6 Ready</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-1125"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/software">Percona Software for MySQL</a></div><div class="item"><a href="http://www.percona.com/software/percona-server">Percona Server with XtraDB</a></div><div class="item"><a href="http://www.percona.com/software/percona-xtradb-cluster">Percona XtraDB Cluster</a></div><div class="item"><a href="http://www.percona.com/software/percona-toolkit">Percona Toolkit for MySQL</a></div><div class="item"><a href="http://www.percona.com/software/percona-monitoring-plugins">Percona Monitoring Plugins</a></div><div class="item"><a href="http://www.percona.com/software/mysql-innodb-data-recovery-tools">Data Recovery Toolkit</a></div><div class="item"><a href="http://www.percona.com/software/percona-xtrabackup">Percona XtraBackup</a></div><div class="item"><a href="http://www.percona.com/software/percona-xtradb">Percona XtraDB</a></div><div class="item"><a href="http://www.percona.com/downloads">Downloads</a></div><div class="item"><a href="http://www.percona.com/software/repositories">Repositories</a></div><div class="item"><a href="http://www.percona.com/software/documentation">Documentation</a></div><div class="item"><a href="http://www.percona.com/mysql-5.6-solutions-from-percona">MySQL 5.6 Compatibility</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-918"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/webinars">Webinars</a></div><div class="item"><a href="http://tools.percona.com">Percona Online Tools</a></div><div class="item"><a href="https://tools.percona.com/wizard">MySQL Configuration Wizard</a></div><div class="item"><a href="https://tools.percona.com/query-advisor">MySQL Query Advisor</a></div><div class="item"><a href="http://www.percona.com/about-us/blogs">Blogs</a></div><div class="item"><a href="http://www.percona.com/about-us/presentations">Technical Presentations</a></div><div class="item"><a href="http://www.percona.com/about-us/books">Books by Percona Authors</a></div><div class="item"><a href="http://www.percona.com/about-us/mysql-white-papers">White Papers</a></div><div class="item"><a href="http://www.percona.com/resources/mysql-case-studies">Case Studies</a></div><div class="item"><a rel="nofollow" href="http://percona.tv/">Videos</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-919"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/percona-news">In The News</a></div><div class="item"><a href="http://www.percona.com/about-us/pressreleases">Press Releases</a></div><div class="item"><a href="http://www.percona.com/live-2">Percona Live Conferences</a></div><div class="item"><a href="http://www.percona.com/mysql-events">MySQL Events</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-1129"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/forums">Forums</a></div><div class="item"><a href="http://www.mysqlperformanceblog.com/">MySQL Performance Blog</a></div><div class="item"><a rel="nofollow" href="http://groups.google.com/group/percona-discussion">Google Discussion Group</a></div><div class="item"><a rel="nofollow" href="http://twitter.com/percona">Twitter</a></div><div class="item"><a rel="nofollow" href="https://www.facebook.com/Percona">Facebook</a></div><div class="item"><a rel="nofollow" href="http://www.linkedin.com/groups?gid=2299033&amp;trk=hb_side_g">Linkedin</a></div><div class="item"><a rel="nofollow" href="https://launchpad.net/percona-project">Launchpad</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-920"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/contact/24x7-emergency">24x7 Emergency</a></div><div class="item"><a href="http://www.percona.com/contact/sales">Sales &amp; General Inquiries</a></div><div class="item"><a href="http://www.percona.com/contact/billing">Billing Inquiries</a></div><div class="item"><a href="https://customers.percona.com/">Customer Portal Login</a></div><div class="item"><a href="http://www.percona.com/contact/phone-directory">Phone Directory</a></div><div class="item"><a href="http://www.percona.com/subscribe">Subscribe to Newsletter</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-1060"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/live/london-2013/">London 2013</a></div><div class="item"><a href="http://www.percona.com/live/mysql-conference-2013/">MySQL Conference &amp; Expo 2013</a></div><div class="item"><a href="http://www.percona.com/live/london-2012/">London 2012</a></div><div class="item"><a href="http://www.percona.com/live/nyc-2012/">New York 2012</a></div><div class="item"><a href="http://www.percona.com/live/mysql-conference-2012/">MySQL Conference &amp; Expo 2012</a></div><div class="item"><a href="http://www.percona.com/live">Previous Percona Live Events</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div>  <div id="search-dropdown" class="search-dropdown">
+<div class="navi-dropdown" id="navi-dropdown-menu-914"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/about-us/our-mission">Mission</a></div><div class="item"><a href="http://www.percona.com/about-us/our-team">Team</a></div><div class="item"><a href="http://www.percona.com/about-us/customers">Customers</a></div><div class="item"><a href="http://www.percona.com/about-us/partners">Partners</a></div><div class="item"><a href="http://www.percona.com/about-us/careers">Careers</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-915"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/products/mysql-support">MySQL Support</a></div><div class="item"><a href="http://www.percona.com/products/mysql-consulting">MySQL Consulting</a></div><div class="item"><a href="http://www.percona.com/products/mysql-remote-dba">MySQL Remote DBA</a></div><div class="item"><a href="http://www.percona.com/products/mysql-training">MySQL Training</a></div><div class="item"><a href="http://www.percona.com/products/mysql-development">MySQL Server Development</a></div><div class="item"><a href="http://www.percona.com/mysql-5.6-solutions-from-percona">MySQL 5.6 Ready</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-1125"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/software">Percona Software for MySQL</a></div><div class="item"><a href="http://www.percona.com/software/percona-server">Percona Server with XtraDB</a></div><div class="item"><a href="http://www.percona.com/software/percona-xtradb-cluster">Percona XtraDB Cluster</a></div><div class="item"><a href="http://www.percona.com/software/percona-toolkit">Percona Toolkit for MySQL</a></div><div class="item"><a href="http://www.percona.com/software/percona-monitoring-plugins">Percona Monitoring Plugins</a></div><div class="item"><a href="http://www.percona.com/software/mysql-innodb-data-recovery-tools">Data Recovery Toolkit</a></div><div class="item"><a href="http://www.percona.com/software/percona-xtrabackup">Percona XtraBackup</a></div><div class="item"><a href="http://www.percona.com/software/percona-xtradb">Percona XtraDB</a></div><div class="item"><a href="http://www.percona.com/downloads">Downloads</a></div><div class="item"><a href="http://www.percona.com/software/repositories">Repositories</a></div><div class="item"><a href="http://www.percona.com/software/documentation">Documentation</a></div><div class="item"><a href="http://www.percona.com/mysql-5.6-solutions-from-percona">MySQL 5.6 Compatibility</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-918"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/resources/mysql-webinars">Webinars</a></div><div class="item"><a href="http://www.percona.com/resources/percona-tools-for-mysql">Percona Tools for MySQL</a></div><div class="item"><a href="http://www.percona.com/resources/presentations">Technical Presentations</a></div><div class="item"><a href="http://www.percona.com/resources/mysql-white-papers">White Papers</a></div><div class="item"><a href="http://www.percona.com/resources/mysql-case-studies">Case Studies</a></div><div class="item"><a href="http://www.percona.com/resources/books">Books by Percona Authors</a></div><div class="item"><a href="http://www.percona.com/resources/mysql-blogs">Blogs</a></div><div class="item"><a rel="nofollow" href="http://percona.tv/">Videos</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-919"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/news-and-events/percona-in-the-news">In The News</a></div><div class="item"><a href="http://www.percona.com/news-and-events/pressreleases">Press Releases</a></div><div class="item"><a href="http://www.percona.com/news-and-events/awards">Awards</a></div><div class="item"><a href="http://www.percona.com/news-and-events/mysql-events">MySQL Events</a></div><div class="item"><a href="http://www.percona.com/news-and-events/percona-university">Percona University</a></div><div class="item"><a href="http://www.percona.com/live/conferences">Percona Live Conferences</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-1129"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/forums">Forums</a></div><div class="item"><a href="http://www.mysqlperformanceblog.com/">MySQL Performance Blog</a></div><div class="item"><a rel="nofollow" href="http://groups.google.com/group/percona-discussion">Google Discussion Group</a></div><div class="item"><a rel="nofollow" href="http://twitter.com/percona">Twitter</a></div><div class="item"><a rel="nofollow" href="https://www.facebook.com/Percona">Facebook</a></div><div class="item"><a rel="nofollow" href="http://www.linkedin.com/groups?gid=2299033&amp;trk=hb_side_g">Linkedin</a></div><div class="item"><a rel="nofollow" href="https://launchpad.net/percona-project">Launchpad</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-920"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/contact/24x7-emergency">24x7 Emergency</a></div><div class="item"><a href="http://www.percona.com/contact/sales">Sales &amp; General Inquiries</a></div><div class="item"><a href="http://www.percona.com/contact/billing">Billing Inquiries</a></div><div class="item"><a href="https://customers.percona.com/">Customer Portal Login</a></div><div class="item"><a href="http://www.percona.com/contact/phone-directory">Phone Directory</a></div><div class="item"><a href="http://www.percona.com/subscribe">Subscribe to Newsletter</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div><div class="navi-dropdown" id="navi-dropdown-menu-1060"><div class="navi-dropdown-header-l"><!-- //--></div><div class="navi-dropdown-content"><div class="item"><a href="http://www.percona.com/live/london-2013/">London 2013</a></div><div class="item"><a href="http://www.percona.com/live/mysql-conference-2013/">MySQL Conference &amp; Expo 2013</a></div><div class="item"><a href="http://www.percona.com/live/london-2012/">London 2012</a></div><div class="item"><a href="http://www.percona.com/live/nyc-2012/">New York 2012</a></div><div class="item"><a href="http://www.percona.com/live/mysql-conference-2012/">MySQL Conference &amp; Expo 2012</a></div><div class="item"><a href="http://www.percona.com/live">Previous Percona Live Events</a></div></div><div class="navi-dropdown-footer"><!-- //--></div></div>  <div id="search-dropdown" class="search-dropdown">
     <div class="search-dropdown-header"><!-- //--></div>
     <div class="search-dropdown-content">
       <div class="search-info">Search Percona.com:</div>
-      <form method="get" action="http://search.percona.com/search/" id="search-form">
-        <div class="form"><input type="text" id="search-input" name="q" maxlength="100" /></div>
+      <form method="get" action="http://www.percona.com/search" id="search-form">
+        <div class="form"><input type="text" id="search-input" name="s" maxlength="100" /></div>
       </form>
     </div>
     <div class="search-dropdown-footer"><!-- //--></div>
@@ -342,11 +342,18 @@
 </div>
 <div id="stats">
 <!-- GA //-->
-  <script src="http://www.percona.com/static/js/urchin.js" type="text/javascript"></script>
   <script type="text/javascript">
-  _uacct = "UA-343802-3";
-  urchinTracker();
-  </script>
+  var _gaq = _gaq || [];
+  _gaq.push(['b._setAccount', 'UA-343802-3']);
+  _gaq.push(['b._setDomainName', 'percona.com']);
+  _gaq.push(['b._trackPageview']);
+  (function() {
+  var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+  ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google- analytics.com/ga.js';
+  var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+  })();
+</script>
+
 <!-- /GA //-->
 <!-- NAVI //-->
 <script type="text/javascript">//<![CDATA[
@@ -354,7 +361,7 @@
 for(var i = 0, c = navi.length; i < c; i++) {
   window.jQuery('#navilink-a-' + navi[i].id).bind('mouseover',{id: navi[i].id, direction:navi[i].direction}, function(e) { NAVI.Open(e.data.id, e.data.direction); } );
 }
-window.jQuery('#search-form').bind('submit', function() { window.location.href = jQuery('#search-form').attr('action') + jQuery('#search-input').val(); return false; });
+window.jQuery('#search-form').bind('submit', function() { window.location.href = jQuery('#search-form').attr('action') + '?s=' + jQuery('#search-input').val(); return false; });
 
 //]]></script>
 <!-- /NAVI //-->

=== modified file 'doc/source/release-notes.rst'
--- doc/source/release-notes.rst	2013-05-14 06:09:45 +0000
+++ doc/source/release-notes.rst	2013-08-30 09:58:59 +0000
@@ -1,5 +1,5 @@
 ======================================
- |Percona| |XtraBackup| Release Notes
+ |Percona XtraBackup| Release Notes
 ======================================
 
 Older releases
@@ -13,7 +13,7 @@
    release-notes/1.4
    release-notes/1.5
 
-Percona |XtraBackup| 1.6 
+|Percona XtraBackup| 1.6 
 =========================
 
 .. toctree::
@@ -22,7 +22,7 @@
 
    release-notes/1.6/*
 
-Percona |XtraBackup| 2.0 
+|Percona XtraBackup| 2.0 
 =========================
 
 .. toctree::

=== modified file 'doc/source/release-notes/1.4.rst'
--- doc/source/release-notes/1.4.rst	2012-02-02 20:25:55 +0000
+++ doc/source/release-notes/1.4.rst	2013-08-30 09:58:59 +0000
@@ -4,14 +4,14 @@
 
 Released on November 22, 2010
 
-Percona |XtraBackup| version 1.4 fixes problems related to incremental backups. If you do incremental backups, it's strongly recommended that you upgrade to this release.
+|Percona XtraBackup| version 1.4 fixes problems related to incremental backups. If you do incremental backups, it's strongly recommended that you upgrade to this release.
 
 Functionality Added or Changed
 ------------------------------
 
 * `Incremental backups <http://www.percona.com/docs/wiki/percona-xtrabackup:xtrabackup:incremental>`_ have changed and now allow the restoration of full backups containing certain rollback transactions that previously caused problems. Please see `Preparing the Backups <http://www.percona.com/docs/wiki/percona-xtrabackup:xtrabackup:incremental#Preparing_the_Backups>`_  and the :option:`--apply-log-only`. (From |innobackupex|, the :option:`--redo-only` option should be used.) (Yasufumi Kinoshita)
 
-  * The |XtraBackup| Test Suite was implemented and is now a standard part of each distribution. (Aleksandr Kuzminsky)
+  * The |Percona XtraBackup| Test Suite was implemented and is now a standard part of each distribution. (Aleksandr Kuzminsky)
 
 * Other New Features
 
@@ -25,7 +25,7 @@
 
   * Ported to the |Percona Server| 5.1.47 code base. (Yasufumi Kinoshita)
 
-  * |XtraBackup| now uses the memory allocators of the host operating system, rather than the built-in |InnoDB| allocators (see `Using Operating System Memory Allocators <http://dev.mysql.com/doc/innodb-plugin/1.1/en/innodb-performance-use_sys_malloc.html>`_). (Yasufumi Kinoshita)
+  * |Percona XtraBackup| now uses the memory allocators of the host operating system, rather than the built-in |InnoDB| allocators (see `Using Operating System Memory Allocators <http://dev.mysql.com/doc/innodb-plugin/1.1/en/innodb-performance-use_sys_malloc.html>`_). (Yasufumi Kinoshita)
 
 Bugs Fixed
 ----------

=== modified file 'doc/source/release-notes/1.5.rst'
--- doc/source/release-notes/1.5.rst	2012-02-02 20:25:55 +0000
+++ doc/source/release-notes/1.5.rst	2013-08-30 09:58:59 +0000
@@ -1,17 +1,17 @@
 =============================
-Percona |XtraBackup| 1.5-Beta
+|Percona XtraBackup| 1.5-Beta
 =============================
 
 Released December 13, 2010 (`downloads <http://www.percona.com/downloads/XtraBackup/XtraBackup-1.5/>`_)
 
-This release adds additional functionality to Percona |XtraBackup| 1.4, the current general availability version of |XtraBackup|. This is a beta release.
+This release adds additional functionality to |Percona XtraBackup| 1.4, the current general availability version of |Percona XtraBackup|. This is a beta release.
 
 Functionality Added or Changes
 ------------------------------
 
 * Support for |MySQL| 5.5 databases has been implemented. (Yasufumi Kinoshita)
 
-* |XtraBackup| can now be built from the |MySQL| 5.1.52, |MySQL| 5.5.7, or |Percona Server| 5.1.53-12 code bases (fixes bug `#683507 <https://bugs.launchpad.net/bugs/683507>`_). (Alexey Kopytov)
+* |Percona XtraBackup| can now be built from the |MySQL| 5.1.52, |MySQL| 5.5.7, or |Percona Server| 5.1.53-12 code bases (fixes bug `#683507 <https://bugs.launchpad.net/bugs/683507>`_). (Alexey Kopytov)
 
 * The program is now distributed as three separate binaries:
 
@@ -23,9 +23,9 @@
 
 * Backing up only specific tables can now be done by specifying them in a file, using the :option:`--tables-file`. (Yasufumi Kinoshita & Daniel Nichter)
 
-* Additional checks were added to monitor the rate the log file is being overwritten, to determine if |XtraBackup| is keeping up. If the log file is being overwritten faster than |XtraBackup| can keep up, a warning is given that the backup may be inconsistent. (Yasufumi Kinoyasu) 
+* Additional checks were added to monitor the rate the log file is being overwritten, to determine if |Percona XtraBackup| is keeping up. If the log file is being overwritten faster than |Percona XtraBackup| can keep up, a warning is given that the backup may be inconsistent. (Yasufumi Kinoyasu) 
 
-* The |XtraBackup| binaries are now compiled with the ``-O3`` :command:`gcc` option, which may improve backup speed in stream mode in some cases.
+* The |Percona XtraBackup| binaries are now compiled with the ``-O3`` :command:`gcc` option, which may improve backup speed in stream mode in some cases.
 
 * It is now possible to copy multiple data files concurrently in parallel threads when creating a backup, using the :option:`--parallel` option. See `The xtrabackup Option Reference <http://www.percona.com/docs/wiki/percona-xtrabackup:xtrabackup:option-and-variable-reference>`_ and `Parallel Backups <http://www.percona.com/docs/wiki/percona-xtrabackup:innobackupex:how_to_recipes#Parallel_Backups>`_. (Alexey Kopytov)
 

=== modified file 'doc/source/release-notes/1.6/1.6.0.rst'
--- doc/source/release-notes/1.6/1.6.0.rst	2012-02-02 20:25:55 +0000
+++ doc/source/release-notes/1.6/1.6.0.rst	2013-08-30 09:58:59 +0000
@@ -1,5 +1,5 @@
 ==========================
-|Percona| |XtraBackup| 1.6
+|Percona XtraBackup| 1.6
 ==========================
 
 Released on April 12, 2011 (Downloads are available `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-1.6/>`_ and from the `Percona Software Repositories <http://www.percona.com/docs/wiki/repositories:start>`_.)
@@ -22,17 +22,17 @@
 
 * 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 :command:`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)
+* Ported |Percona 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 :command:`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 the built-in |innobackupex| usage docs. (Baron Schwartz, Fred Linhoss)
 
-* Added a manual page for |XtraBackup|. (Aleksandr Kuzminsky)
+* Added a manual page for |Percona XtraBackup|. (Aleksandr Kuzminsky)
 
 * Disabled auto-creating :file:`ib_logfile*` when |innobackupex| is called with :option:`--redo-only` or with :option:`--incremental-dir`. If necessary :file:`ib_logfile*` can be created later with :command:`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)
+* For portability, the |Percona XtraBackup| build script now tries to link with ``libaio`` only on Linux. (Aleksandr Kuzminsky)
 
 Bugs Fixed
 ----------

=== modified file 'doc/source/release-notes/1.6/1.6.2.rst'
--- doc/source/release-notes/1.6/1.6.2.rst	2012-02-02 20:25:55 +0000
+++ doc/source/release-notes/1.6/1.6.2.rst	2013-08-30 09:58:59 +0000
@@ -1,10 +1,10 @@
 ============================
-|Percona| |XtraBackup| 1.6.2
+|Percona XtraBackup| 1.6.2
 ============================
 
 Percona is glad to announce the release of Percona XtraBackup 1.6.2 on 25 July, 2011 (Downloads are available `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-1.6.2/>`_ and from the `Percona Software Repositories <http://www.percona.com/docs/wiki/repositories:start>`_).
 
-This release is purely composed of bug fixes and is the current stable release of |Percona| |Xtrabackup|.
+This release is purely composed of bug fixes and is the current stable release of |Percona XtraBackup|.
 
 All of |Percona|'s software is open-source and free, all the details of the release and its development process can be found in the `1.6.2 milestone at Launchpad <https://launchpad.net/percona-xtrabackup/+milestone/1.6.2>`_.
 
@@ -33,8 +33,8 @@
 Other Changes
 -------------
 
-   * Improvements and fixes on the XtraBackup Test Suite: `#744303 <https://bugs.launchpad.net/bugs/744303>`_, `#787966 < <https://bugs.launchpad.net/bugs/787966>`_ (Alexey Kopytov)
+   * Improvements and fixes on the |Percona XtraBackup| Test Suite: `#744303 <https://bugs.launchpad.net/bugs/744303>`_, `#787966 < <https://bugs.launchpad.net/bugs/787966>`_ (Alexey Kopytov)
 
    * Improvements and fixes on platform-specific distribution: `#785556 <https://bugs.launchpad.net/bugs/785556>`_ (Ignacio Nin)
 
-   * Improvements and fixes on the XtraBackup Documentation: `#745185 <https://bugs.launchpad.net/bugs/745185>`_, `#721339 <https://bugs.launchpad.net/bugs/721339>`_ (Rodrigo Gadea)
+   * Improvements and fixes on the |Percona XtraBackup| Documentation: `#745185 <https://bugs.launchpad.net/bugs/745185>`_, `#721339 <https://bugs.launchpad.net/bugs/721339>`_ (Rodrigo Gadea)

=== modified file 'doc/source/release-notes/1.6/1.6.3.rst'
--- doc/source/release-notes/1.6/1.6.3.rst	2012-02-02 20:25:55 +0000
+++ doc/source/release-notes/1.6/1.6.3.rst	2013-08-30 09:58:59 +0000
@@ -1,12 +1,12 @@
 ============================
-|Percona| |XtraBackup| 1.6.3
+|Percona XtraBackup| 1.6.3
 ============================
 
 Percona is glad to announce the release of Percona XtraBackup 1.6.3 on 22 September, 2011 (Downloads are available `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-1.6.3/>`_ and from the :doc:`Percona Software Repositories </installation>`).
 
-This release is purely composed of bug fixes and is the current stable release of |Percona| |Xtrabackup|.
+This release is purely composed of bug fixes and is the current stable release of |Percona XtraBackup|.
 
-If the :term:`innodb_file_per_table` server option is been used and ``DDL`` operations, ``TRUNCATE TABLE``, ``DROP/CREATE the_same_table`` or ``ALTER`` statements on |InnoDB| tables are executed while taking a backup, an upgrade to |XtraBackup| 1.6.3 is **strongly recommended**. Under this scenario, if the server version is prior to 5.5.11 in 5.5 series or prior to 5.1.49 in 5.1 series, a server upgrade is also recommended.
+If the :term:`innodb_file_per_table` server option is been used and ``DDL`` operations, ``TRUNCATE TABLE``, ``DROP/CREATE the_same_table`` or ``ALTER`` statements on |InnoDB| tables are executed while taking a backup, an upgrade to |Percona XtraBackup| 1.6.3 is **strongly recommended**. Under this scenario, if the server version is prior to 5.5.11 in 5.5 series or prior to 5.1.49 in 5.1 series, a server upgrade is also recommended.
 
 All of |Percona| 's software is open-source and free, all the details of the release and its development process can be found in the `1.6.3 milestone at Launchpad <https://launchpad.net/percona-xtrabackup/+milestone/1.6.3>`_.
 
@@ -16,9 +16,9 @@
 
   * Streaming backups did not work for compressed |InnoDB| tables due to missing support for compressed pages in |tar4ibd|. Bug Fixed: :bug:`665210` (*Alexey Kopytov*).
 
-  * |XtraBackup| failed when ``innodb_flush_method`` in the server configuration file was set to ``ALL_O_DIRECT``. Bug Fixed: :bug:`759225` (*Alexey Kopytov*).
+  * |Percona XtraBackup| failed when ``innodb_flush_method`` in the server configuration file was set to ``ALL_O_DIRECT``. Bug Fixed: :bug:`759225` (*Alexey Kopytov*).
 
-  * Due to a regression introduced in |XtraBackup| 1.6.2, :command:`innobackupex --copy-back` did not work if the :command:`xtrabackup` binary was not specified explicitly with the :option:`--ibbackup` option. Bug Fixed: :bug:`817132` (*Alexey Kopytov*).
+  * Due to a regression introduced in |Percona XtraBackup| 1.6.2, :command:`innobackupex --copy-back` did not work if the :command:`xtrabackup` binary was not specified explicitly with the :option:`--ibbackup` option. Bug Fixed: :bug:`817132` (*Alexey Kopytov*).
 
   * The :option:`--slave-info` option now works correctly with :option:`--safe-slave-backup` when either :option:`--no-lock` or :option:`--incremental` is also specified. Bug Fixed: :bug:`834657` (*Alexey Kopytov*).
 
@@ -27,14 +27,14 @@
   * Unsupported command line options could cause a :program:`tar4ibd` crash. Such options have been removed. Bug Fixed: :bug:`677279` (*Alexey Kopytov*).
 
   * Executing ``DDL`` operations, ``TRUNCATE TABLE``, ``DROP/CREATE the_same_table`` or ``ALTER`` statements on |InnoDB| tables while taking a backup could lead to a |xtrabackup| failure due to a tablespace ``ID`` mismatch when using per-table tablespaces. Note that this fix may not work correctly with |MySQL| 5.5 or |Percona Server| 5.5 prior to version 5.5.11. 5.1 releases from 5.1.49 or higher have been confirmed not to be affected. 
-    If the :term:`innodb_file_per_table` option is been used, an upgrade to |XtraBackup| 1.6.3 is **strongly recommended**. Under this scenario, if the server version is prior to 5.5.11 in 5.5 series or prior to 5.1.49 in 5.1 series, a server upgrade is also recommended. Bug Fixed: :bug:`722638` (*Alexey Kopytov*).
+    If the :term:`innodb_file_per_table` option is been used, an upgrade to |Percona XtraBackup| 1.6.3 is **strongly recommended**. Under this scenario, if the server version is prior to 5.5.11 in 5.5 series or prior to 5.1.49 in 5.1 series, a server upgrade is also recommended. Bug Fixed: :bug:`722638` (*Alexey Kopytov*).
 
 
 Other Changes
 -------------
 
-  * Improvements and fixes on the |XtraBackup| Test Suite: :bug:`855035`, :bug:`787966` (*Alexey Kopytov*)
+  * Improvements and fixes on the |Percona XtraBackup| Test Suite: :bug:`855035`, :bug:`787966` (*Alexey Kopytov*)
 
   * Improvements and fixes on distribution: :bug:`775463`, :bug:`745168`, :bug:`849872`, :bug:`785556` (*Ignacio Nin*)
 
-  * Improvements and fixes on the |XtraBackup| Documentation: :bug:`837754`, :bug:`745185`, :bug:`836907` (*Rodrigo Gadea*)
+  * Improvements and fixes on the |Percona XtraBackup| Documentation: :bug:`837754`, :bug:`745185`, :bug:`836907` (*Rodrigo Gadea*)

=== modified file 'doc/source/release-notes/1.6/1.6.4.rst'
--- doc/source/release-notes/1.6/1.6.4.rst	2012-02-02 20:25:55 +0000
+++ doc/source/release-notes/1.6/1.6.4.rst	2013-08-30 09:58:59 +0000
@@ -1,5 +1,5 @@
 ============================
-|Percona| |XtraBackup| 1.6.4
+|Percona XtraBackup| 1.6.4
 ============================
 
 Percona is glad to announce the release of Percona XtraBackup 1.6.4 on 19 December, 2011 (Downloads are available `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-1.6.4/>`_ and from the :doc:`Percona Software Repositories </installation>`).

=== modified file 'doc/source/release-notes/1.6/1.6.5.rst'
--- doc/source/release-notes/1.6/1.6.5.rst	2012-02-08 23:19:52 +0000
+++ doc/source/release-notes/1.6/1.6.5.rst	2013-08-30 09:58:59 +0000
@@ -1,10 +1,10 @@
 ============================
-|Percona| |XtraBackup| 1.6.5
+|Percona XtraBackup| 1.6.5
 ============================
 
 Percona is glad to announce the release of Percona XtraBackup 1.6.5 on 10 February, 2012 (Downloads are available `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-1.6.5/>`_ and from the :doc:`Percona Software Repositories </installation>`).
 
-This release is purely composed of bug fixes and is the current stable release of |Percona| |Xtrabackup|.
+This release is purely composed of bug fixes and is the current stable release of |Percona XtraBackup|.
 
 Bugs Fixed
 ----------

=== modified file 'doc/source/release-notes/1.6/1.6.6.rst'
--- doc/source/release-notes/1.6/1.6.6.rst	2012-12-17 12:42:00 +0000
+++ doc/source/release-notes/1.6/1.6.6.rst	2013-08-30 09:58:59 +0000
@@ -1,12 +1,12 @@
 ============================
-|Percona| |XtraBackup| 1.6.6
+|Percona XtraBackup| 1.6.6
 ============================
 
 Percona is glad to announce the release of Percona XtraBackup 1.6.6 on April 4th, 2012 (Downloads are available `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-1.6.6/>`_ and from the :doc:`Percona Software Repositories </installation>`).
 
 Option --remote-host for |innobackupex| has been deprecated in favor of the --stream option and it will be removed in future versions.
 
-This release is purely composed of bug fixes and is the current stable release of |Percona| |Xtrabackup|.
+This release is purely composed of bug fixes and is the current stable release of |Percona XtraBackup|.
 
 Bugs Fixed
 ----------

=== modified file 'doc/source/release-notes/1.6/1.6.7.rst'
--- doc/source/release-notes/1.6/1.6.7.rst	2013-01-02 04:03:16 +0000
+++ doc/source/release-notes/1.6/1.6.7.rst	2013-08-30 09:58:59 +0000
@@ -1,10 +1,10 @@
 ============================
-|Percona| |XtraBackup| 1.6.7
+|Percona XtraBackup| 1.6.7
 ============================
 
 Percona is glad to announce the release of Percona XtraBackup 1.6.7 on December 20th, 2012 (Downloads are available `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-1.6.7/>`_ and from the :doc:`Percona Software Repositories </installation>`).
 
-This release is purely composed of bug fixes and is the current stable release of |Percona| |Xtrabackup|.
+This release is purely composed of bug fixes and is the current stable release of |Percona XtraBackup|.
 
 Bugs Fixed
 ----------
@@ -15,7 +15,7 @@
 
   Option :option:`--safe-slave-backup` was resulting in incorrect binlog info, because in some cases innobackupex confused the response from SHOW SLAVE STATUS with the one from SHOW MASTER STATUS. Bug fixed :bug:`977101` (*Alexey Kopytov*). 
 
-  `innodb_data_file_path` was not written to :file:`backup-my.cnf`, this was a regression introduced in |XtraBackup| 1.6.5. Bug fixed :bug:`983685` (*Sergei Glushchenko*).
+  `innodb_data_file_path` was not written to :file:`backup-my.cnf`, this was a regression introduced in |Percona XtraBackup| 1.6.5. Bug fixed :bug:`983685` (*Sergei Glushchenko*).
 
   Fixed spurious test suite failures with grep 2.10. Bug fixed :bug:`996483` (*Alexey Kopytov*).
 
@@ -23,7 +23,7 @@
 
   |innobackupex| could copy files to a wrong directory when merging an incremental backup to a full one. Bug fixed :bug:`1002688` (*Alexey Kopytov*).
 
-  |XtraBackup| binary was leaking file descriptors on :option:`--backup`. This was fixed by reusing the existing file descriptor so no leak occurs. Bug fixed :bug:`713267` (*Alexey Kopytov*).
+  |Percona XtraBackup| binary was leaking file descriptors on :option:`--backup`. This was fixed by reusing the existing file descriptor so no leak occurs. Bug fixed :bug:`713267` (*Alexey Kopytov*).
 
 Other bugs fixed: bug :bug:`1021954` (*Hrvoje Matijakovic*).
 

=== modified file 'doc/source/release-notes/2.0/1.9.0.rst'
--- doc/source/release-notes/2.0/1.9.0.rst	2012-02-08 23:39:07 +0000
+++ doc/source/release-notes/2.0/1.9.0.rst	2013-08-30 09:58:59 +0000
@@ -1,23 +1,23 @@
 =======================================
-|Percona| |XtraBackup| 1.9.0 (2.0 BETA)
+|Percona XtraBackup| 1.9.0 (2.0 BETA)
 =======================================
 
 Percona is glad to announce the release of Percona XtraBackup 1.9.0 on 9th February 2012. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/BETA/1.9.0/>`_. For this BETA release, we will not be making APT and YUM repositories available, just base deb and RPM packages.
 
 This is a *BETA* quality release and is not inteded for production. If you want a high quality, Generally Available release, you should use the current Stable version - currently 1.6.4 in the 1.6 series at the time of writing.
 
-The 1.9.x version numbers will be used to distinguish between pre-release versions of |Percona| |XtraBackup| 2.0 and the Generally Available final release.
+The 1.9.x version numbers will be used to distinguish between pre-release versions of |Percona XtraBackup| 2.0 and the Generally Available final release.
 
 This release contains all of the features and bug fixes in :doc:`Percona XtraBackup 1.6.4 </release-notes/1.6/1.6.4>`, plus the following:
 
 New features
 ------------
 
-  * |Percona| |XtraBackup| can now save Galera replication information while performing a backup when given the ``--galera-info`` option to innobackupex.
-
-  * The documentation is now bundled with |Percona| |XtraBackup|. It may not be included in binary packages for this beta release.
-
-  * Support for compiling and running |Percona| |XtraBackup| against debug versions of InnoDB. This is only for *very* advanced users.
+  * |Percona XtraBackup| can now save Galera replication information while performing a backup when given the ``--galera-info`` option to innobackupex.
+
+  * The documentation is now bundled with |Percona XtraBackup|. It may not be included in binary packages for this beta release.
+
+  * Support for compiling and running |Percona XtraBackup| against debug versions of InnoDB. This is only for *very* advanced users.
 
 Bugs Fixed
 ----------
@@ -32,7 +32,7 @@
 
   * ``xtrabackup_binary`` was not included in tar archive when streaming, instead it was written to the current directory. This could cause backups with ``--remote-host`` to fail. Bugs Fixed: :bug:`723318` (*Alexey Kopytov*) and :bug:`787988` (*Alexey Kopytov*)
 
-  * Compiling |Percona| |XtraBackup| with GCC 4.6 produced compiler warnings. Bug fixed: :bug:`748064` (*Stewart Smith*)
+  * Compiling |Percona XtraBackup| with GCC 4.6 produced compiler warnings. Bug fixed: :bug:`748064` (*Stewart Smith*)
 
   * Improvements to incremental backups when using streaming, the addition of the ``--extra-lsndir`` option. Bug fixed: :bug:`680936` (*Vadim Tkachenko*)
 

=== modified file 'doc/source/release-notes/2.0/1.9.1.rst'
--- doc/source/release-notes/2.0/1.9.1.rst	2012-03-22 13:46:42 +0000
+++ doc/source/release-notes/2.0/1.9.1.rst	2013-08-30 09:58:59 +0000
@@ -1,21 +1,21 @@
 =======================================
-|Percona| |XtraBackup| 1.9.1 (2.0 BETA)
+|Percona XtraBackup| 1.9.1 (2.0 BETA)
 =======================================
 
 Percona is glad to announce the release of Percona XtraBackup 1.9.1 on 24th February 2012. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/BETA/1.9.1/>`_. For this BETA release, we will not be making APT and YUM repositories available, just base deb and RPM packages.
 
 This is a *BETA* quality release and is not inteded for production. If you want a high quality, Generally Available release, you should use the current Stable version - currently 1.6.5 in the 1.6 series at the time of writing.
 
-The 1.9.x version numbers will be used to distinguish between pre-release versions of |Percona| |XtraBackup| 2.0 and the Generally Available final release.
+The 1.9.x version numbers will be used to distinguish between pre-release versions of |Percona XtraBackup| 2.0 and the Generally Available final release.
 
 This release contains all of the features and bug fixes in :doc:`Percona XtraBackup 1.9.0 </release-notes/2.0/1.9.0>`, plus the following:
 
 New features
 ------------
 
-  * |Xtrabackup| now supports compressed backups. These backups can be done in a parallel way, thus utilizing multiple CPU cores if needed. In previous versions, compression was only possible with streaming backups + external (usually single-threaded) compression utilities, which also had a number of other limitations (e.g. could not be used with parallel file copying, it was required to uncompress the entire backup to restore a single table)  (*Alexey Kopytov*).
+  * |Percona XtraBackup| now supports compressed backups. These backups can be done in a parallel way, thus utilizing multiple CPU cores if needed. In previous versions, compression was only possible with streaming backups + external (usually single-threaded) compression utilities, which also had a number of other limitations (e.g. could not be used with parallel file copying, it was required to uncompress the entire backup to restore a single table)  (*Alexey Kopytov*).
 
-  * |Percona| |XtraBackup| now supports streaming incremental backups. In previous versions streaming backups were performed by the innobackupex script but incremental backups were done by the xtrabackup binary which calculated deltas by scanning data files. Which meant those two feature were mutually exclusive, i.e. one couldn't do streaming incremental backups (*Alexey Kopytov*).
+  * |Percona XtraBackup| now supports streaming incremental backups. In previous versions streaming backups were performed by the innobackupex script but incremental backups were done by the xtrabackup binary which calculated deltas by scanning data files. Which meant those two feature were mutually exclusive, i.e. one couldn't do streaming incremental backups (*Alexey Kopytov*).
 
   * As part of the backup, the LRU dump is now included as well (*Sergei Glushchenko*).
 

=== modified file 'doc/source/release-notes/2.0/1.9.2.rst'
--- doc/source/release-notes/2.0/1.9.2.rst	2012-03-28 14:13:15 +0000
+++ doc/source/release-notes/2.0/1.9.2.rst	2013-08-30 09:58:59 +0000
@@ -1,12 +1,12 @@
 =======================================
-|Percona| |XtraBackup| 1.9.2 (2.0 BETA)
+|Percona XtraBackup| 1.9.2 (2.0 BETA)
 =======================================
 
 Percona is glad to announce the release of Percona XtraBackup 1.9.2 on 28th March 2012. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/BETA/1.9.2/>`_. For this BETA release, we will not be making APT and YUM repositories available, just base deb and RPM packages.
 
 This is a *BETA* quality release and is not inteded for production. If you want a high quality, Generally Available release, you should use the current Stable version - currently 1.6.5 in the 1.6 series at the time of writing.
 
-The 1.9.x version numbers will be used to distinguish between pre-release versions of |Percona| |XtraBackup| 2.0 and the Generally Available final release.
+The 1.9.x version numbers will be used to distinguish between pre-release versions of |Percona XtraBackup| 2.0 and the Generally Available final release.
 
 Package name has been changed from xtrabackup to full product name, **percona-xtrabackup**.
 
@@ -19,6 +19,6 @@
 
   * In MySQL 5.1.57 a new assertion was added as a part of the fix for `bug #59641 <http://bugs.mysql.com/bug.php?id=59641>`_. That assertion wasn't applicable when doing recovery with --apply-log-only option, and it was failing after successfully applying the log. Fix was implemented by bypassing that code. Fixed bug :bug:`938594` (*Alexey Kopytov*).
 
-  * In some cases if XtraBackup had discovered corruption it wouldn't say which file it is. Now it mentions the file name along with the error. Bug fixed :bug:`766033` (*Sergei Glushchenko*).
+  * In some cases if |Percona XtraBackup| had discovered corruption it wouldn't say which file it is. Now it mentions the file name along with the error. Bug fixed :bug:`766033` (*Sergei Glushchenko*).
  
   * Fixed *posix_fadvise* bug :bug:`925441` (*Alexey Kopytov*).

=== modified file 'doc/source/release-notes/2.0/2.0.0.rst'
--- doc/source/release-notes/2.0/2.0.0.rst	2012-04-04 13:17:13 +0000
+++ doc/source/release-notes/2.0/2.0.0.rst	2013-08-30 09:58:59 +0000
@@ -1,5 +1,5 @@
 ============================
-|Percona| |XtraBackup| 2.0.0
+|Percona XtraBackup| 2.0.0
 ============================
 
 Percona is glad to announce the release of Percona XtraBackup 2.0.0 on 4th April 2012. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-2.0.0/>`_ and :doc:`Percona Software Repositories </installation>`.

=== modified file 'doc/source/release-notes/2.0/2.0.1.rst'
--- doc/source/release-notes/2.0/2.0.1.rst	2012-08-03 12:12:02 +0000
+++ doc/source/release-notes/2.0/2.0.1.rst	2013-08-30 09:58:59 +0000
@@ -1,5 +1,5 @@
 ============================
-|Percona| |XtraBackup| 2.0.1
+|Percona XtraBackup| 2.0.1
 ============================
 
 Percona is glad to announce the release of Percona XtraBackup 2.0.1 on June 25th, 2012. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-2.0.1/>`_ and :doc:`Percona Software Repositories </installation>`.
@@ -25,7 +25,7 @@
 
   * `innodb_data_file_path` was not written to backup-my.cnf, this was a regression introduced in previous version. Bug fixed :bug:`983685` (*Sergei Glushchenko*). 
  
-  * |XtraBackup| would fail to find the `datadir` when using :option:`mysqld_multi`. This was fixed by adding new option :option:`--defaults-group`, to both innobackupex and xtrabackup, now it can be specified which section of my.cnf to handle. Bug fixed :bug:`483827` (*Sergei Glushchenko* and *Daniël van Eeden*).
+  * |Percona XtraBackup| would fail to find the `datadir` when using :option:`mysqld_multi`. This was fixed by adding new option :option:`--defaults-group`, to both innobackupex and xtrabackup, now it can be specified which section of my.cnf to handle. Bug fixed :bug:`483827` (*Sergei Glushchenko* and *Daniël van Eeden*).
 
   * InnoDB tables with names containing: *opt*, *par*, *CSV*, *MYD* were backed up twice. These tables were backed up by xtrabackup binary and by innobackupex script. Regular expression for filtering database directory contents was fixed. Bug fixed :bug:`989397` (*Sergei Glushchenko*).
 
@@ -33,17 +33,17 @@
 
   * |innobackupex| could copy files to a wrong directory when merging an incremental backup to a full one. Bug fixed :bug:`1002688` (*Alexey Kopytov*).
 
-  * Incremental backups were not working correctly with :option:`--stream=tar`. This was fixed by making :option:`--incremental-lsn` incompatible with :option:`--stream=tar`. |XtraBackup| will fail with an error message suggesting to use :option:`--stream=xbstream`. Bug fixed :bug:`999750` (*Alexey Kopytov*).
+  * Incremental backups were not working correctly with :option:`--stream=tar`. This was fixed by making :option:`--incremental-lsn` incompatible with :option:`--stream=tar`. |Percona XtraBackup| will fail with an error message suggesting to use :option:`--stream=xbstream`. Bug fixed :bug:`999750` (*Alexey Kopytov*).
 
-  * |innobackupex| failed to copy-back backup if destination dir wasn't empty. Exceptions were added for `my.cnf` and `master.info` as |XtraBackup| doesn't backup those files, so it won't overwrite anything. Bug fixed :bug:`935847` (*Igor Tverdovskiy*). 
+  * |innobackupex| failed to copy-back backup if destination dir wasn't empty. Exceptions were added for `my.cnf` and `master.info` as |Percona XtraBackup| doesn't backup those files, so it won't overwrite anything. Bug fixed :bug:`935847` (*Igor Tverdovskiy*). 
 
   * |innobackupex| :option:`--copy-back` could skip some files when copying from a Windows filesystem mounted over NFS. Bug fixed :bug:`1003518` (*Alexey Kopytov*).
 
-  * |XtraBackup| binary was leaking file descriptors on :option:`--backup`. This was fixed by reusing the existing file descriptor so no leak occurs. Bug fixed :bug:`713267` (*Alexey Kopytov*).
-
-  * There were no source files in tar.gz archive for Percona XtraBackup 2.0.0. Bug fixed :bug:`1002841` (*Ignacio Nin*).
-
-  * |XtraBackup| binary could fail with the "log block checksum
+  * |Percona XtraBackup| binary was leaking file descriptors on :option:`--backup`. This was fixed by reusing the existing file descriptor so no leak occurs. Bug fixed :bug:`713267` (*Alexey Kopytov*).
+
+  * There were no source files in tar.gz archive for |Percona XtraBackup| 2.0.0. Bug fixed :bug:`1002841` (*Ignacio Nin*).
+
+  * |Percona XtraBackup| binary could fail with the "log block checksum
      mismatch" error when reading an partially written log block.  Bug
      fixed :bug:`1015416` (*Alexey Kopytov*).
 

=== modified file 'doc/source/release-notes/2.0/2.0.2.rst'
--- doc/source/release-notes/2.0/2.0.2.rst	2012-08-06 01:06:32 +0000
+++ doc/source/release-notes/2.0/2.0.2.rst	2013-08-30 09:58:59 +0000
@@ -1,5 +1,5 @@
 ============================
-|Percona| |XtraBackup| 2.0.2
+|Percona XtraBackup| 2.0.2
 ============================
 
 Percona is glad to announce the release of Percona XtraBackup 2.0.2 on August 13th, 2012. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-2.0.2/>`_ and :doc:`Percona Software Repositories </installation>`.

=== modified file 'doc/source/release-notes/2.0/2.0.3.rst'
--- doc/source/release-notes/2.0/2.0.3.rst	2012-11-22 09:55:05 +0000
+++ doc/source/release-notes/2.0/2.0.3.rst	2013-08-30 09:58:59 +0000
@@ -1,5 +1,5 @@
 ============================
-|Percona| |XtraBackup| 2.0.3
+|Percona XtraBackup| 2.0.3
 ============================
 
 Percona is glad to announce the release of Percona XtraBackup 2.0.3 on October 1st, 2012. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-2.0.3/>`_ and :doc:`Percona Software Repositories </installation>`.
@@ -14,9 +14,9 @@
 Bugs Fixed
 ==========
 
-  * Symlink for ``innobackupex-1.5.1`` binary has been broken in the previous version of |XtraBackup|. Bug fixed :bug:`1038198` (*Ignacio Nin*).
+  * Symlink for ``innobackupex-1.5.1`` binary has been broken in the previous version of |Percona XtraBackup|. Bug fixed :bug:`1038198` (*Ignacio Nin*).
 
-  * |XtraBackup| 2.0.2 was not backwards compatible which caused incremental backups created with previous versions to fail on prepare. Bug fixed :bug:`1038127` (*Sergei Glushchenko*).
+  * |Percona XtraBackup| 2.0.2 was not backwards compatible which caused incremental backups created with previous versions to fail on prepare. Bug fixed :bug:`1038127` (*Sergei Glushchenko*).
 
   * Fix for bug :bug:`1022562` introduced a regression that may potentially lead to a 5x increase in disk space occupied by incremental backups. Bug fixed :bug:`1043762` (*Laurynas Biveinis*).
 

=== modified file 'doc/source/release-notes/2.0/2.0.4.rst'
--- doc/source/release-notes/2.0/2.0.4.rst	2013-01-15 11:54:46 +0000
+++ doc/source/release-notes/2.0/2.0.4.rst	2013-08-30 09:58:59 +0000
@@ -1,5 +1,5 @@
 ============================
-|Percona| |XtraBackup| 2.0.4
+|Percona XtraBackup| 2.0.4
 ============================
 
 Percona is glad to announce the release of Percona XtraBackup 2.0.4 on December 3rd, 2012. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-2.0.4/>`_ and :doc:`Percona Software Repositories </installation>`.
@@ -9,24 +9,24 @@
 Bugs Fixed
 ==========
 
-  * Bug fix for :bug:`932623` introduced the regression in |XtraBackup| 2.0.2 which caused incremental backups to fail because the init parameter values were not normalized to the values used inside |InnoDB|. Bug fixed :bug:`1062684` (*Sergei Glushchenko*).
-
-  * Bug fix for :bug:`932623` introduced the regression in |XtraBackup| 2.0.2 because it didn't take the separate doublewrite tablespace into an account. Bug fixed :bug:`1066843` (*Sergei Glushchenko*).
-
-  * |XtraBackup| was handling the separate doublewrite buffer file incorrectly. File path of the doublewrite buffer wasn't added to the :file:`backup-my.cnf` and after the restore old doublewrite buffer file was used instead of one made during the prepare stage.  Bug fixed :bug:`1068470` (*Sergei Glushchenko*).
-
-  * |XtraBackup| now accepts the :option:`--innodb=force` option, previously it would throw an error if the option was set. Bug fixed :bug:`528752` (*Laurynas Biveinis*).
+  * Bug fix for :bug:`932623` introduced the regression in |Percona XtraBackup| 2.0.2 which caused incremental backups to fail because the init parameter values were not normalized to the values used inside |InnoDB|. Bug fixed :bug:`1062684` (*Sergei Glushchenko*).
+
+  * Bug fix for :bug:`932623` introduced the regression in |Percona XtraBackup| 2.0.2 because it didn't take the separate doublewrite tablespace into an account. Bug fixed :bug:`1066843` (*Sergei Glushchenko*).
+
+  * |Percona XtraBackup| was handling the separate doublewrite buffer file incorrectly. File path of the doublewrite buffer wasn't added to the :file:`backup-my.cnf` and after the restore old doublewrite buffer file was used instead of one made during the prepare stage.  Bug fixed :bug:`1068470` (*Sergei Glushchenko*).
+
+  * |Percona XtraBackup| now accepts the :option:`--innodb=force` option, previously it would throw an error if the option was set. Bug fixed :bug:`528752` (*Laurynas Biveinis*).
 
   * Option :option:`safe-slave-backup` wasn't working correctly. Bug fixed :bug:`887803` (*Alexey Kopytov*).
 
   * In case ``safe-slave-backup-timeout`` was reached when using the :option:`safe-slave-backup` option, ``SQL_THREAD`` was left in stopped state causing the slave thread to lag behind. This was fixed by checking the initial ``SQL_THREAD`` state and starting it before terminating with a timeout error and starting the ``SQL_THREAD`` only if it was running initially. Bug fixed :bug:`1037379` (*Alexey Kopytov*).
   
-  * |Xtrabackup| would fail on ``--apply-log`` when filesystem didn't support Linux AIO. Bug fixed :bug:`1065561` (*Alexey Kopytov*).
-
-  * |Xtrabackup| binary would ignore :option:`innodb_use_native_aio` when it's specified either in :file:`my.cnf` or as a command line option. Bug fixed :bug:`1068459` (*Alexey Kopytov*).
-
-  * |Xtrabackup| would print a warning message during the prepare stage about :option:`innodb_file_io_threads` being deprecated, even if the variable wasn't set. Bug fixed :bug:`1068485` (*Alexey Kopytov*).
-
-  * |Xtrabackup| Galera tests can now be run concurrently. Bug fixed :bug:`1077800` (*Stewart Smith*).
+  * |Percona XtraBackup| would fail on ``--apply-log`` when filesystem didn't support Linux AIO. Bug fixed :bug:`1065561` (*Alexey Kopytov*).
+
+  * ``xtrabackup`` binary would ignore :option:`innodb_use_native_aio` when it's specified either in :file:`my.cnf` or as a command line option. Bug fixed :bug:`1068459` (*Alexey Kopytov*).
+
+  * |Percona XtraBackup| would print a warning message during the prepare stage about :option:`innodb_file_io_threads` being deprecated, even if the variable wasn't set. Bug fixed :bug:`1068485` (*Alexey Kopytov*).
+
+  * |Percona XtraBackup| Galera tests can now be run concurrently. Bug fixed :bug:`1077800` (*Stewart Smith*).
 
 

=== modified file 'doc/source/release-notes/2.0/2.0.5.rst'
--- doc/source/release-notes/2.0/2.0.5.rst	2013-01-15 11:54:46 +0000
+++ doc/source/release-notes/2.0/2.0.5.rst	2013-08-30 09:58:59 +0000
@@ -1,5 +1,5 @@
 ============================
-|Percona| |XtraBackup| 2.0.5
+|Percona XtraBackup| 2.0.5
 ============================
 
 Percona is glad to announce the release of Percona XtraBackup 2.0.5 on January 18th, 2013. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-2.0.5/>`_ and :doc:`Percona Software Repositories </installation>`.
@@ -14,17 +14,17 @@
 Bugs Fixed
 ==========
 
-  In case of streaming backups, |innobackupex| would resume the |XtraBackup| process and then wait for it to finish before running ``UNLOCK TABLES``. This caused database to be unnecessarily locked with ``FLUSH TABLES WITH READ LOCK``. Innobackupex now waits only till log copying is finished to unlock the databases. Bug fixed :bug:`1055989` (*Alexey Kopytov*).
+  In case of streaming backups, |innobackupex| would resume the |Percona XtraBackup| process and then wait for it to finish before running ``UNLOCK TABLES``. This caused database to be unnecessarily locked with ``FLUSH TABLES WITH READ LOCK``. Innobackupex now waits only till log copying is finished to unlock the databases. Bug fixed :bug:`1055989` (*Alexey Kopytov*).
 
   |innobackupex| error messages referencing the data directory have been extended to show the path of the data directory mentioned in the error message. Bug fixed :bug:`1089375` (*Hartmut Holzgraefe*).
 
-  Partitioned tables were not correctly handled by the :option:`--databases`, :option:`--include`, :option:`--tables-file` options of |innobackupex|, and by the :option:`--tables` and :option:`--tables-file` options of |XtraBackup|. Fixed by removing the partition suffix (#P#...) before doing filtering. Bug fixed :bug:`711166` (*Sergei Glushchenko*).
+  Partitioned tables were not correctly handled by the :option:`--databases`, :option:`--include`, :option:`--tables-file` options of |innobackupex|, and by the :option:`--tables` and :option:`--tables-file` options of |Percona XtraBackup|. Fixed by removing the partition suffix (#P#...) before doing filtering. Bug fixed :bug:`711166` (*Sergei Glushchenko*).
 
-  When built-in compression was used, |XtraBackup| was doing unbuffered writes to the destination file or stream in very small chunks which in return caused inefficient I/O. Fixed by using a 1M buffer for output similar to the uncompressed backups. Bug fixed :bug:`1095249` (*Alexey Kopytov*).
+  When built-in compression was used, |Percona XtraBackup| was doing unbuffered writes to the destination file or stream in very small chunks which in return caused inefficient I/O. Fixed by using a 1M buffer for output similar to the uncompressed backups. Bug fixed :bug:`1095249` (*Alexey Kopytov*).
 
   Unnecessary long sleep() in |innobackupex| lead to ``FLUSH TABLES WITH READ LOCK`` taking too long. Fixed by replacing 2 seconds sleep interval with 100 milliseconds one. Bug fixed :bug:`1095551` (*Sergei Glushchenko*).
 
-  If |innobackupex| would crash it would leave the ``xtrabackup_suspended`` file on the filesystem. This could then cause |innobackupex| to think |XtraBackup| has suspended itself the moment it started, and then when xtrabackup actually does suspend itself innobackupex would wait for it to end and wouldn't re-remove the suspend_file, leading to a wait deadlock. Fixed by removing the stale ``xtrabackup_suspended`` file when |innobackupex| is started. Bug fixed :bug:`1007446` (*George Ormond Lorch III*).
+  If |innobackupex| would crash it would leave the ``xtrabackup_suspended`` file on the filesystem. This could then cause |innobackupex| to think |Percona XtraBackup| has suspended itself the moment it started, and then when xtrabackup actually does suspend itself innobackupex would wait for it to end and wouldn't re-remove the suspend_file, leading to a wait deadlock. Fixed by removing the stale ``xtrabackup_suspended`` file when |innobackupex| is started. Bug fixed :bug:`1007446` (*George Ormond Lorch III*).
 
   |innobackupex| would fail to recognize MariaDB 5.2 and MariaDB 5.3. Fixed by augmenting version checks in |innobackupex|. Bug fixed :bug:`733665` (*Daniël van Eeden*, *Alexey Kopytov*).
 

=== modified file 'doc/source/release-notes/2.0/2.0.6.rst'
--- doc/source/release-notes/2.0/2.0.6.rst	2013-03-13 09:02:32 +0000
+++ doc/source/release-notes/2.0/2.0.6.rst	2013-08-30 09:58:59 +0000
@@ -1,5 +1,5 @@
 ============================
-|Percona| |XtraBackup| 2.0.6
+|Percona XtraBackup| 2.0.6
 ============================
 
 Percona is glad to announce the release of Percona XtraBackup 2.0.6 on March 20, 2013. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-2.0.6/>`_ and :doc:`Percona Software Repositories </installation>`.
@@ -9,26 +9,26 @@
 New Features
 =============
 
- |XtraBackup| has implemented basic support for |MySQL| 5.6, |Percona Server| 5.6 and *MariaDB* 10.0. Basic support means that these versions are are recognized by |XtraBackup|, and that backup/restore works as long as no 5.6-specific features are used (such as ``GTID``, remote/transportable tablespaces, separate undo tablespace, 5.6-style buffer pool dump files).
+ |Percona XtraBackup| has implemented basic support for |MySQL| 5.6, |Percona Server| 5.6 and *MariaDB* 10.0. Basic support means that these versions are are recognized by |Percona XtraBackup|, and that backup/restore works as long as no 5.6-specific features are used (such as ``GTID``, remote/transportable tablespaces, separate undo tablespace, 5.6-style buffer pool dump files).
 
 Bugs Fixed
 ==========
 
  Individual *InnoDB* tablespaces with size less than 1MB were extended to 1MB on the backup prepare operation. This led to a large increase in disk usage in cases when there are many small *InnoDB* tablespaces. Bug fixed :bug:`950334` (*Daniel Frett*, *Alexey Kopytov*).
 
- Fixed the issue that caused databases corresponding to inaccessible :term:`datadir` subdirectories to be ignored by |XtraBackup| without warning or error messages. This was happening because |InnoDB| code silently ignored :term:`datadir` subdirectories it could not open. Bug fixed :bug:`664986` (*Alexey Kopytov*).
+ Fixed the issue that caused databases corresponding to inaccessible :term:`datadir` subdirectories to be ignored by |Percona XtraBackup| without warning or error messages. This was happening because |InnoDB| code silently ignored :term:`datadir` subdirectories it could not open. Bug fixed :bug:`664986` (*Alexey Kopytov*).
 
- Under some circumstances |XtraBackup| could fail to copy a tablespace with a high :option:`--parallel` option value and a low :option:`innodb_open_files` value. Bug fixed :bug:`870119` (*Alexey Kopytov*).
+ Under some circumstances |Percona XtraBackup| could fail to copy a tablespace with a high :option:`--parallel` option value and a low :option:`innodb_open_files` value. Bug fixed :bug:`870119` (*Alexey Kopytov*).
 
  Fix for the bug :bug:`711166` introduced a regression that caused individual partition backups to fail when used with :option:`--include` option in |innobackupex| or the :option:`--tables` option in xtrabackup. Bug fixed :bug:`1130627` (*Alexey Kopytov*).
 
- |innobackupex| didn't add the :option:`file-per-table` setting for table-independent backups. Fixed by making |XtraBackup| auto-enable :option:`innodb_file_per_table` when the :option:`--export` option is used. Bug fixed :bug:`930062` (*Alexey Kopytov*).
+ |innobackupex| didn't add the :option:`file-per-table` setting for table-independent backups. Fixed by making |Percona XtraBackup| auto-enable :option:`innodb_file_per_table` when the :option:`--export` option is used. Bug fixed :bug:`930062` (*Alexey Kopytov*).
 
- Under some circumstances |XtraBackup| could fail on a backup prepare with :option:`innodb_flush_method=O_DIRECT`. Bug fixed :bug:`1055547` (*Alexey Kopytov*).
+ Under some circumstances |Percona XtraBackup| could fail on a backup prepare with :option:`innodb_flush_method=O_DIRECT`. Bug fixed :bug:`1055547` (*Alexey Kopytov*).
 
  |innobackupex| did not pass the :option:`--tmpdir` option to the xtrabackup binary resulting in the server's ``tmpdir`` always being used for temporary files. Bug fixed :bug:`1085099` (*Alexey Kopytov*).
 
- |XtraBackup| has improved the error reporting for unrecognized server versions. Bug fixed :bug:`1087219` (*Alexey Kopytov*).
+ |Percona XtraBackup| has improved the error reporting for unrecognized server versions. Bug fixed :bug:`1087219` (*Alexey Kopytov*).
 
  Fixed the missing ``rpm`` dependency for Perl ``Time::HiRes`` package that caused |innobackupex| to fail on minimal CentOS installations. Bug fixed :bug:`1121573` (*Alexey Bychko*).
 
@@ -36,6 +36,6 @@
 
  Fix for the bug :bug:`1055989` introduced a regression that caused :file:`xtrabackup_pid` file to remain in the temporary dir after execution. Bug fixed :bug:`1114955` (*Alexey Kopytov*).
 
- Unnecessary debug messages have been removed from the |XtraBackup| output. Bug fixed :bug:`1131084` (*Alexey Kopytov*).
+ Unnecessary debug messages have been removed from the |Percona XtraBackup| output. Bug fixed :bug:`1131084` (*Alexey Kopytov*).
 
 Other bug fixes: bug fixed :bug:`1153334` (*Alexey Kopytov*), bug fixed :bug:`1098498` (*Laurynas Biveinis*), bug fixed :bug:`1132763` (*Laurynas Biveinis*), bug fixed :bug:`1142229` (*Laurynas Biveinis*), bug fixed :bug:`1130581` (*Laurynas Biveinis*).

=== modified file 'doc/source/release-notes/2.0/2.0.7.rst'
--- doc/source/release-notes/2.0/2.0.7.rst	2013-05-07 06:57:31 +0000
+++ doc/source/release-notes/2.0/2.0.7.rst	2013-08-30 09:58:59 +0000
@@ -1,5 +1,5 @@
 ============================
-|Percona| |XtraBackup| 2.0.7
+|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>`.
@@ -13,7 +13,7 @@
 
  |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.
+ 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 |Percona 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 ``GTID`` mode enabled. 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/>`_.
 
@@ -34,11 +34,11 @@
 
  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`.
+ 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 |Percona 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 |Percona 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 |Percona 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`.
 

=== added file 'doc/source/release-notes/2.0/2.0.8.rst'
--- doc/source/release-notes/2.0/2.0.8.rst	1970-01-01 00:00:00 +0000
+++ doc/source/release-notes/2.0/2.0.8.rst	2013-08-30 09:58:59 +0000
@@ -0,0 +1,39 @@
+============================
+|Percona XtraBackup| 2.0.8
+============================
+
+Percona is glad to announce the release of Percona XtraBackup 2.0.8 on September 4th, 2013. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-2.0.8/>`_ and :doc:`Percona Software Repositories </installation>`.
+
+This release is the current GA (Generally Available) stable release in the 2.0 series. 
+
+
+Bugs Fixed
+==========
+
+ |Percona XtraBackup| 2.0 will now be offered in :doc:`Percona Software Repositories </installation>`. Bug fixed :bug:`1190055`.
+
+ |Percona XtraBackup| would assume the table has been dropped if the tablespace was renamed after it was scanned by |XtraBackup| on startup and before |XtraBackup| attempted to copy it. Bug fixed :bug:`1079700`.
+
+ Fixed the ``libssl.so.6`` dependency issues in binary tarballs releases. Bug fixed :bug:`1172916`.
+
+ Orphaned ``xtrabackup_pid`` file left inside tmpdir could cause `SST <http://www.percona.com/doc/percona-xtradb-cluster/manual/state_snapshot_transfer.html>`_ to fail. Fixed by fix checking if ``xtrabackup_pid`` file exists once |innobackupex| starts, and try to remove it or fail if it cannot be removed. Bug fixed :bug:`1175860`.
+
+ During the backup process loading tablespaces was started before the log copying, this could lead to a race between the datafiles state in the resulting backup and xtrabackup_logfile. Tablespace created at a sensitive time would be missing in both the backup itself and as the corresponding log record in :file:`xtrabackup_logfile`, so it would not be created on :option:`innobackupex --apply-log` either. Bug fixed :bug:`1177206`.
+
+ |innobackupex| automatic version detection did not work correctly for latest |Percona Server| and |MySQL| 5.1 releases which could cause innobackupex to fail. Bugs fixed :bug:`1181092` and :bug:`1181099`.
+
+ Difference in behavior between |InnoDB| 5.5 and 5.6 codebases in cases when a newly created tablespace has uninitialized first page at the time when |Percona XtraBackup| opens it while creating a list of tablespaces to backup would cause assertion error. Bug fixed :bug:`1187071`.
+
+ Debug builds would fail due to compiler errors on *Ubuntu* Quantal/Raring builds. Fixed compiler warnings by backporting the corresponding changes from upstream. Bug fixed :bug:`1192454`.
+
+ |Percona XtraBackup| would stop in case log block numbers had to wrap around, which only happens once per 1 GB of log writes, and the wrap-around point was between the last checkpoint and the current log tail at the time the backup starts. Bug fixed :bug:`1206309`.
+
+ ``xtrabackup_56`` binary would fail to create a suspend file, which would result in an error. Bug fixed :bug:`1210266`.
+
+ Under some circumstances |Percona XtraBackup| could fail on a backup prepare with ``innodb_flush_method=O_DIRECT`` when ``XFS`` filesystem was being used. Bug fixed :bug:`1190779`.
+
+ |Percona XtraBackup| didn't recognize checkpoint ``#0`` as a valid checkpoint on :option:`xtrabackup --prepare` which would cause an error. Bug fixed :bug:`1196475`.
+
+ :option:`xtrabackup --stats` option would not work with server :term:`datadir` if the server isn't running and logs were in a separate directory. Bug fixed :bug:`1174314`.
+
+Other bug fixes: bug fixed :bug:`1097434`, bug fixed :bug:`1214272`, bug fixed :bug:`1211173`, bug fixed :bug:`1201599`, bug fixed :bug:`1097444`, bug fixed :bug:`1042796`, bug fixed :bug:`1214730`, bug fixed :bug:`1204463`, bug fixed :bug:`1197249`, bug fixed :bug:`1196894`, bug fixed :bug:`1194813`, bug fixed :bug:`1183500`, bug fixed :bug:`1177182`, bug fixed :bug:`1175309`, bug fixed :bug:`1201686`, bug fixed :bug:`1182995`, bug fixed :bug:`1175566`.

=== modified file 'doc/source/release-notes/2.1/2.1.0-rc1.rst'
--- doc/source/release-notes/2.1/2.1.0-rc1.rst	2013-05-07 07:01:29 +0000
+++ doc/source/release-notes/2.1/2.1.0-rc1.rst	2013-08-30 09:58:59 +0000
@@ -13,7 +13,7 @@
 
  |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.
+ 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 |Percona 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 ``GTID`` mode enabled. 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/>`_.
 
@@ -28,7 +28,7 @@
 
  |Percona XtraBackup| would leave stale ``xtrabackup_tmp*`` files in the :term:`datadir` after applying incremental backups. Bug fixed :bug:`1079135`.
 
- 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`.
+ If there are thousands of tables and slow IO then |Percona XtraBackup| can spend a lot of time opening all the tablespaces. Optimization has been implemented and |Percona XtraBackup| now avoids loading non-relevant tablespaces when partial backup is being taken which speeds up the backup process. Bug fixed :bug:`1130145`.
 
  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`
 

=== modified file 'doc/source/release-notes/2.1/2.1.4.rst'
--- doc/source/release-notes/2.1/2.1.4.rst	2013-08-01 08:54:47 +0000
+++ doc/source/release-notes/2.1/2.1.4.rst	2013-08-30 09:58:59 +0000
@@ -28,7 +28,7 @@
 
  |innobackupex| did not encrypt non-InnoDB files when doing local (i.e. non-streaming) backups. Bug fixed :bug:`1160778`.
 
- Difference in behavior between |InnoDB| 5.5 and 5.6 codebases in cases when a newly created tablespace has uninitialized first page at the time when |XtraBackup| opens it while creating a list of tablespaces to backup would cause assertion error. Bug fixed :bug:`1187071`. 
+ Difference in behavior between |InnoDB| 5.5 and 5.6 codebases in cases when a newly created tablespace has uninitialized first page at the time when |Percona XtraBackup| opens it while creating a list of tablespaces to backup would cause assertion error. Bug fixed :bug:`1187071`. 
 
  **xbcrypt** could sometimes fail when reading encrypted stream from a pipe or network. Bug fixed :bug:`1190610`.
 
@@ -38,7 +38,7 @@
 
  |innobackupex| would terminate with an error if :option:`innobackupex --safe-slave-backup` option was used for backing up the master server. Bug fixed :bug:`1190716`.
 
- Under some circumstances |XtraBackup| could fail on a backup prepare with ``innodb_flush_method=O_DIRECT`` when ``XFS`` filesystem was being used. Bug fixed :bug:`1190779`.
+ Under some circumstances |Percona XtraBackup| could fail on a backup prepare with ``innodb_flush_method=O_DIRECT`` when ``XFS`` filesystem was being used. Bug fixed :bug:`1190779`.
 
  |Percona XtraBackup| didn't recognize checkpoint ``#0`` as a valid checkpoint on :option:`xtrabackup --prepare` which would cause an error. Bug fixed :bug:`1196475`.
  

=== modified file 'doc/source/xbcrypt/xbcrypt.rst'
--- doc/source/xbcrypt/xbcrypt.rst	2013-03-29 10:33:27 +0000
+++ doc/source/xbcrypt/xbcrypt.rst	2013-08-30 09:58:59 +0000
@@ -4,9 +4,9 @@
  The xbcrypt binary
 ======================
 
-To support encryption and decryption of the backups, a new tool ``xbcrypt`` was introduced to XtraBackup. 
+To support encryption and decryption of the backups, a new tool ``xbcrypt`` was introduced to |Percona XtraBackup|. 
 
-This utility has been modeled after :ref:`xbstream_binary` to perform encryption and decryption outside of |XtraBackup|. Xbcrypt has following command line options: 
+This utility has been modeled after :ref:`xbstream_binary` to perform encryption and decryption outside of |Percona XtraBackup|. Xbcrypt has following command line options: 
 
 .. option:: -d, --decrypt
 

=== modified file 'doc/source/xbstream/xbstream.rst'
--- doc/source/xbstream/xbstream.rst	2013-03-29 10:33:27 +0000
+++ doc/source/xbstream/xbstream.rst	2013-08-30 09:58:59 +0000
@@ -4,7 +4,7 @@
  The xbstream Binary
 ======================
 
-To support simultaneous compression and streaming, a new custom streaming format called xbstream was introduced to XtraBackup in addition to the TAR format. That was required to overcome some limitations of traditional archive formats such as tar, cpio and others which did not allow streaming dynamically generated files, for example dynamically compressed files. Other advantages of xbstream over traditional streaming/archive format include ability to stream multiple files concurrently (so it is possible to use streaming in the xbstream format together with the --parallel option) and more compact data storage. 
+To support simultaneous compression and streaming, a new custom streaming format called xbstream was introduced to |Percona XtraBackup| in addition to the TAR format. That was required to overcome some limitations of traditional archive formats such as tar, cpio and others which did not allow streaming dynamically generated files, for example dynamically compressed files. Other advantages of xbstream over traditional streaming/archive format include ability to stream multiple files concurrently (so it is possible to use streaming in the xbstream format together with the --parallel option) and more compact data storage. 
 
 This utility has a tar-like interface:
 

=== modified file 'doc/source/xtrabackup-files.rst'
--- doc/source/xtrabackup-files.rst	2013-04-29 11:08:57 +0000
+++ doc/source/xtrabackup-files.rst	2013-08-30 09:58:59 +0000
@@ -1,8 +1,8 @@
 .. _xtrabackup_files :
 
-=====================================
-Index of files created by XtraBackup
-=====================================
+============================================
+Index of files created by Percona XtraBackup
+============================================
 
 * Information related to the backup and the server
 

=== modified file 'doc/source/xtrabackup_bin/compact_backups.rst'
--- doc/source/xtrabackup_bin/compact_backups.rst	2013-05-03 05:17:03 +0000
+++ doc/source/xtrabackup_bin/compact_backups.rst	2013-08-30 09:58:59 +0000
@@ -61,7 +61,7 @@
 
   $ xtrabackup --prepare --rebuild-indexes --rebuild-threads=16 /data/backups/
 
-In this case |XtraBackup| will create 16 worker threads with each thread rebuilding indexes for one table at a time. It will also show thread IDs for each message ::
+In this case |Percona XtraBackup| will create 16 worker threads with each thread rebuilding indexes for one table at a time. It will also show thread IDs for each message ::
 
   Starting 16 threads to rebuild indexes.
 
@@ -74,7 +74,7 @@
   [11]   Found index idx_last_name
   [11]   Rebuilding 3 index(es).
 
-Since |XtraBackup| has no information when applying an incremental backup to a compact full one, on whether there will be more incremental backups applied to it later or not, rebuilding indexes needs to be explicitly requested by a user whenever a full backup with some incremental backups merged is ready to be restored. Rebuilding indexes unconditionally on every incremental backup merge is not an option, since it is an expensive operation.
+Since |Percona XtraBackup| has no information when applying an incremental backup to a compact full one, on whether there will be more incremental backups applied to it later or not, rebuilding indexes needs to be explicitly requested by a user whenever a full backup with some incremental backups merged is ready to be restored. Rebuilding indexes unconditionally on every incremental backup merge is not an option, since it is an expensive operation.
 
 Restoring Compact Backups
 =========================

=== modified file 'doc/source/xtrabackup_bin/lru_dump.rst'
--- doc/source/xtrabackup_bin/lru_dump.rst	2012-04-21 07:12:28 +0000
+++ doc/source/xtrabackup_bin/lru_dump.rst	2013-08-30 09:58:59 +0000
@@ -2,7 +2,7 @@
 LRU dump backup
 ================
 
-This feature reduces the warm up time by restoring buffer pool state from :file:`ib_lru_dump` file after restart. |Xtrabackup| discovers :file:`ib_lru_dump` and backs it up automatically.
+This feature reduces the warm up time by restoring buffer pool state from :file:`ib_lru_dump` file after restart. |Percona Xtrabackup| discovers :file:`ib_lru_dump` and backs it up automatically.
 
 .. image:: /_static/lru_dump.png
 

=== modified file 'innobackupex'
--- innobackupex	2013-08-18 07:14:43 +0000
+++ innobackupex	2013-08-30 09:58:59 +0000
@@ -3631,7 +3631,7 @@
 
 =item --galera-info
 
-This options creates the xtrabackup_galera_info file which contians the local node state at the time of the backup. Option should be used when performing the backup of Percona-XtraDB-Cluster.
+This options creates the xtrabackup_galera_info file which contains the local node state at the time of the backup. Option should be used when performing the backup of Percona-XtraDB-Cluster.
 
 =item --help