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

Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Alexey Kopytov
Approved revision: no longer in the source branch.
Merged at revision: 471
Proposed branch: lp:~hrvojem/percona-xtrabackup/rn-2.0.3
Merge into: lp:percona-xtrabackup/2.0
Diff against target: 85 lines (+31/-9)
4 files modified
doc/source/conf.py (+2/-2)
doc/source/innobackupex/innobackupex_option_reference.rst (+1/-3)
doc/source/release-notes/2.0/2.0.3.rst (+24/-0)
innobackupex (+4/-4)
To merge this branch: bzr merge lp:~hrvojem/percona-xtrabackup/rn-2.0.3
Reviewer Review Type Date Requested Status
Alexey Kopytov (community) Approve
Review via email: mp+125658@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Alexey Kopytov (akopytov) wrote :

Hrvoje,

I would clarify a couple of things:

- s/which caused incremental backups to fail in some cases/which caused incremental backups created with previous versions to fail on prepare/

- s/which caused incorrect handling of compressed tablespaces/which caused incorrect handling of compressed tablespaces with the page size of 16K/

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 2012-08-03 12:12:02 +0000
3+++ doc/source/conf.py 2012-09-21 12:39:25 +0000
4@@ -51,9 +51,9 @@
5 # built documents.
6 #
7 # The short X.Y version.
8-version = '2.0.2'
9+version = '2.0.3'
10 # The full version, including alpha/beta/rc tags.
11-release = '2.0.2'
12+release = '2.0.3'
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 2012-09-19 13:00:42 +0000
19+++ doc/source/innobackupex/innobackupex_option_reference.rst 2012-09-21 12:39:25 +0000
20@@ -32,9 +32,7 @@
21
22 .. option:: --move-back
23
24- Move all the files in a previously made backup from the backup
25- directory to their original locations. As this option removes
26- backup files, it must be used with caution.
27+ Move all the files in a previously made backup from the backup directory to their original locations. As this option removes backup files, it must be used with caution.
28
29 .. option:: --include=REGEXP
30
31
32=== added file 'doc/source/release-notes/2.0/2.0.3.rst'
33--- doc/source/release-notes/2.0/2.0.3.rst 1970-01-01 00:00:00 +0000
34+++ doc/source/release-notes/2.0/2.0.3.rst 2012-09-21 12:39:25 +0000
35@@ -0,0 +1,24 @@
36+============================
37+|Percona| |XtraBackup| 2.0.3
38+============================
39+
40+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>`.
41+
42+This release is the current GA (Generally Available) stable release in the 2.0 series.
43+
44+New Features
45+=============
46+
47+ * |innobackupex| now supports new :option:`--move-back` option that can be used instead of :option:`--copy-back` in case there isn't enough free disk space on the server to copy files. As this option removes backup files, it must be used with caution.
48+
49+Bugs Fixed
50+==========
51+
52+ * Symlink for ``innobackupex-1.5.1`` binary has been broken in the previous version of |XtraBackup|. Bug fixed :bug:`1038198` (*Ignacio Nin*).
53+
54+ * |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*).
55+
56+ * 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:`1028949` (*Laurynas Biveinis*).
57+
58+ * A regression was introduced in fix for bug :bug:`932623` which caused incorrect handling of compressed tablespaces with the page size of 16K, that were created between the last full or incremental and the next incremental backup. Bugs fixed :bug:`1049174` and :bug:`1044398` (*Laurynas Biveinis*).
59+
60
61=== modified file 'innobackupex'
62--- innobackupex 2012-09-19 11:35:43 +0000
63+++ innobackupex 2012-09-21 12:39:25 +0000
64@@ -2782,10 +2782,6 @@
65
66 Copy all the files in a previously made backup from the backup directory to their original locations.
67
68-=item --move-back
69-
70-Move all the files in a previously made backup from the backup directory to the actual datadir location. Use with caution, as it removes backup files.
71-
72 =item --databases=LIST
73
74 This option specifies the list of databases that innobackupex should back up. The option accepts a string argument or path to file that contains the list of databases to back up. The list is of the form "databasename1[.table_name1] databasename2[.table_name2] . . .". If this option is not specified, all databases containing MyISAM and InnoDB tables will be backed up. Please make sure that --databases contains all of the InnoDB databases and tables, so that all of the innodb.frm files are also backed up. In case the list is very long, this can be specified in a file, and the full path of the file can be specified instead of the list. (See option --tables-file.)
75@@ -2838,6 +2834,10 @@
76
77 This option specifies the log sequence number (LSN) to use for the incremental backup. The option accepts a string argument. It is used with the --incremental option. It is used instead of specifying --incremental-basedir. For databases created by MySQL and Percona Server 5.0-series versions, specify the LSN as two 32-bit integers in high:low format. For databases created in 5.1 and later, specify the LSN as a single 64-bit integer.
78
79+=item --move-back
80+
81+Move all the files in a previously made backup from the backup directory to the actual datadir location. Use with caution, as it removes backup files.
82+
83 =item --no-lock
84
85 Use this option to disable table lock with "FLUSH TABLES WITH READ LOCK". Use it only if ALL your tables are InnoDB and you DO NOT CARE about the binary log position of the backup.

Subscribers

People subscribed via source and target branches