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

Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Alexey Kopytov
Approved revision: no longer in the source branch.
Merged at revision: 699
Proposed branch: lp:~hrvojem/percona-xtrabackup/rn-2.1.6-2.1
Merge into: lp:percona-xtrabackup/2.1
Diff against target: 125 lines (+59/-3)
5 files modified
doc/source/conf.py (+2/-2)
doc/source/innobackupex/innobackupex_option_reference.rst (+8/-0)
doc/source/installation/apt_repo.rst (+1/-0)
doc/source/release-notes/2.1/2.1.6.rst (+43/-0)
innobackupex.pl (+5/-1)
To merge this branch: bzr merge lp:~hrvojem/percona-xtrabackup/rn-2.1.6-2.1
Reviewer Review Type Date Requested Status
Alexey Kopytov (community) Approve
Review via email: mp+196071@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Alexey Kopytov (akopytov) wrote :

> :option:`innobackupex --copy-back` would fail if the :option:`innodb_data_home_dir` was empty. Bug fixed :bug:`1049291`.

I guess it's either "the innodb_data_home_dir option is empty" or just "innodb_data_home_dir is empty", but the processed text will be "the innodb_data_home_dir is empty"?

> |innobackupex| wasn't able to perform backups to the ``NFS`` mount...

I'd say "to the NFS mount in some NFS configurations".

> Other bugs fixed: bug fixed :bug:`1248488`, bug fixed :bug:`1247057`, bug fixed :bug:`1250738`, bug fixed :bug:`1214274`.

Is that "bug fixed" being repeated multiple times intentional?

review: Needs Fixing
Revision history for this message
Alexey Kopytov (akopytov) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/source/conf.py'
2--- doc/source/conf.py 2013-09-19 13:06:49 +0000
3+++ doc/source/conf.py 2013-11-21 10:09:50 +0000
4@@ -51,9 +51,9 @@
5 # built documents.
6 #
7 # The short X.Y version.
8-version = '2.1.5'
9+version = '2.1.6'
10 # The full version, including alpha/beta/rc tags.
11-release = '2.1.5'
12+release = '2.1.6'
13
14 # The language for content autogenerated by Sphinx. Refer to documentation
15 # for a list of supported languages.
16
17=== modified file 'doc/source/innobackupex/innobackupex_option_reference.rst'
18--- doc/source/innobackupex/innobackupex_option_reference.rst 2013-09-19 13:06:49 +0000
19+++ doc/source/innobackupex/innobackupex_option_reference.rst 2013-11-21 10:09:50 +0000
20@@ -86,6 +86,10 @@
21
22 This option accepts a string argument that specifies the directory in which to save an extra copy of the :file:`xtrabackup_checkpoints` file. It is passed directly to |xtrabackup|'s :option:`--extra-lsndir` option. See the :program:`xtrabackup` documentation for details.
23
24+.. option:: --force-non-empty-directories
25+
26+ When specified, it makes :option:`innobackupex --copy-back` option or :option:`innobackupex --move-back` option transfer files to non-empty directories. No existing files will be overwritten. If --copy-back or --move-back has to copy a file from the backup directory which already exists in the destination directory, it will still fail with an error.
27+
28 .. option:: --galera-info
29
30 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.
31@@ -159,6 +163,10 @@
32
33 This option prevents creation of a time-stamped subdirectory of the ``BACKUP-ROOT-DIR`` given on the command line. When it is specified, the backup is done in ``BACKUP-ROOT-DIR`` instead.
34
35+.. option:: --no-version-check
36+
37+ This option disables the version check which is enabled by the --version-check option.
38+
39 .. option:: --parallel=NUMBER-OF-THREADS
40
41 This option accepts an integer argument that specifies the number of threads the :program:`xtrabackup` child process should use to back up files concurrently. Note that this option works on file level, that is, if you have several .ibd files, they will be copied in parallel. If your tables are stored together in a single tablespace file, it will have no effect. It is passed directly to xtrabackup's :option:`xtrabackup --parallel` option. See the :program:`xtrabackup` documentation for details
42
43=== modified file 'doc/source/installation/apt_repo.rst'
44--- doc/source/installation/apt_repo.rst 2013-07-25 20:00:02 +0000
45+++ doc/source/installation/apt_repo.rst 2013-11-21 10:09:50 +0000
46@@ -37,6 +37,7 @@
47 * 12.04LTS (precise)
48 * 12.10 (quantal)
49 * 13.04 (raring)
50+ * 13.10 (saucy)
51
52 Experimental Repository
53 =======================
54
55=== added file 'doc/source/release-notes/2.1/2.1.6.rst'
56--- doc/source/release-notes/2.1/2.1.6.rst 1970-01-01 00:00:00 +0000
57+++ doc/source/release-notes/2.1/2.1.6.rst 2013-11-21 10:09:50 +0000
58@@ -0,0 +1,43 @@
59+============================
60+ |Percona XtraBackup| 2.1.6
61+============================
62+
63+Percona is glad to announce the release of |Percona XtraBackup| 2.1.6 on November 25th 2013. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/XtraBackup-2.1.6/>`_ and :doc:`Percona Software Repositories </installation>`.
64+
65+This release is the current GA (Generally Available) stable release in the 2.1 series.
66+
67+New Features
68+------------
69+
70+ |Percona XtraBackup| now supports logs created with the new log block checksums option `innodb_log_checksum_algorithm <http://www.percona.com/doc/percona-server/5.6/scalability/innodb_io.html#innodb_log_checksum_algorithm>`_ in |Percona Server| 5.6
71+
72+ New :option:`innobackupex --force-non-empty-directories` option has been implemented. When specified, it makes :option:`innobackupex --copy-back` option or :option:`innobackupex --move-back` option transfer files to non-empty directories. No existing files will be overwritten. If :option:`--copy-back` or :option:`--move-back` has to copy a file from the backup directory which already exists in the destination directory, it will still fail with an error.
73+
74+Bugs Fixed
75+----------
76+
77+ :option:`innobackupex --copy-back` would fail if :option:`innodb_data_home_dir` is empty. Bug fixed :bug:`1049291`.
78+
79+ A fixed initialization vector (constant string) was used while encrypting the data. This opened the encrypted stream/data to plaintext attacks among others. Bug fixed :bug:`1185343`.
80+
81+ :option:`innobackupex --version-check` is now on by default. Bug fixed :bug:`1227988`.
82+
83+ :file:`xtrabackup_slave_info` didn't contain any ``GTID`` information, which could cause ``master_auto_position`` not to work properly. Bug fixed :bug:`1239670`.
84+
85+ ``xtrabackup_56`` was using ``CRC32`` as the default checksum algorithm. This could cause error if the `innodb_checksum_algorithm <http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_checksum_algorithm>`_ value was changed to ``strict_innodb`` value after a restore. Bug fixed :bug:`1247586`.
86+
87+ ``xtrabackup_56`` binary didn't store the server's `innodb_checksum_algorithm <http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_checksum_algorithm>`_ value to :file:`backup-my.cnf`. This value is needed because it affects the on-disk data format. Bug fixed :bug:`1248065`.
88+
89+ Since Version Check is enabled by default in |Percona XtraBackup| 2.1.6, new :option:`innobackupex --no-version-check` option has been introduced to disable it. Bug fixed :bug:`1248900`.
90+
91+ |Percona XtraBackup| now supports absolute paths in :option:`innodb_data_file_path` variable. Bug fixed :bug:`382742`.
92+
93+ |innobackupex| wasn't able to perform backups to the ``NFS`` mount in some ``NFS`` configurations, because it was trying to preserve file ownership. Bug fixed :bug:`943750`.
94+
95+ |Percona XtraBackup| wouldn't back up the empty directory created with ``mkdir`` (i.e. ``test``) outside of the server which could lead to inconsistencies during the |Percona XtraDB Cluster| State Snapshot Transfer. Bug fixed :bug:`1217426`.
96+
97+ If the `innodb_log_arch_dir <http://www.percona.com/doc/percona-server/5.6/management/log_archiving.html#innodb_log_arch_dir>`_ variable was specified in the |Percona Server| configuration file :file:`my.cnf` |Percona XtraBackup| was unable to perform the backup. Bug fixed :bug:`1227240`.
98+
99+ Race condition in ``start_query_killer`` child code could cause parent |MySQL| connection to close. Bug fixed :bug:`1239728`.
100+
101+Other bugs fixed: :bug:`1248488`, :bug:`1247057`, :bug:`1250738`, :bug:`1214274`.
102
103=== modified file 'innobackupex.pl'
104--- innobackupex.pl 2013-11-20 09:19:56 +0000
105+++ innobackupex.pl 2013-11-21 10:09:50 +0000
106@@ -4996,7 +4996,7 @@
107
108 This option specifies the directory in which to save an extra copy of the "xtrabackup_checkpoints" file. The option accepts a string argument. It is passed directly to xtrabackup's --extra-lsndir option. See the xtrabackup documentation for details.
109
110-==item --force-non-empty-directories
111+==item --force-non-empty-directories
112
113 This option, when specified, makes --copy-back or --move-back transfer files to non-empty directories. Note that no existing files will be overwritten. If --copy-back or --nove-back has to copy a file from the backup directory which already exists in the destination directory, it will still fail with an error.
114
115@@ -5077,6 +5077,10 @@
116
117 This option prevents creation of a time-stamped subdirectory of the BACKUP-ROOT-DIR given on the command line. When it is specified, the backup is done in BACKUP-ROOT-DIR instead.
118
119+=item --no-version-check
120+
121+This option disables the version check which is enabled by the --version-check option.
122+
123 =item --parallel=NUMBER-OF-THREADS
124
125 On backup, this option specifies the number of threads the xtrabackup child process should use to back up files concurrently. The option accepts an integer argument. It is passed directly to xtrabackup's --parallel option. See the xtrabackup documentation for details.

Subscribers

People subscribed via source and target branches