Merge lp:~hrvojem/percona-xtrabackup/bug1222818-2.0 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: | 589 | ||||||||||||||||
Proposed branch: | lp:~hrvojem/percona-xtrabackup/bug1222818-2.0 | ||||||||||||||||
Merge into: | lp:percona-xtrabackup/2.0 | ||||||||||||||||
Diff against target: |
260 lines (+54/-31) 11 files modified
doc/source/faq.rst (+5/-0) doc/source/glossary.rst (+1/-1) doc/source/howtos/recipes_ibkx_partition.rst (+4/-3) doc/source/index.rst (+3/-3) doc/source/innobackupex/innobackupex_script.rst (+1/-1) doc/source/innobackupex/partial_backups_innobackupex.rst (+3/-3) doc/source/innobackupex/restoring_individual_tables_ibk.rst (+24/-11) doc/source/percona-theme/layout.html (+1/-1) doc/source/xtrabackup_bin/restoring_individual_tables.rst (+10/-6) doc/source/xtrabackup_bin/xbk_option_reference.rst (+1/-1) doc/source/xtrabackup_bin/xtrabackup_binary.rst (+1/-1) |
||||||||||||||||
To merge this branch: | bzr merge lp:~hrvojem/percona-xtrabackup/bug1222818-2.0 | ||||||||||||||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alexey Kopytov (community) | Approve | ||
Review via email: mp+194349@code.launchpad.net |
To post a comment you must log in.
Hrvoje,
1. This text is a bit misleading:
"When :doc:`restoring individual tables bin/restoring_ individual_ tables> ` with |Percona XtraBackup|,
<xtrabackup_
it creates a file with ``.exp`` extension per exported table containing
the information for importing it"
I suggest something along the following lines:
"Files with the ``.exp`` extension are created by |Percona XtraBackup| bin/restoring_ individual_ tables> `"
per each InnoDB tablespace when the --export option is used on
prepare. These files can be used to import those tablespaces on Percona
Server 5.5 or lower versions, see :doc:`restoring individual tables
<xtrabackup_
2. Strictly speaking, a .cfg file is _not_ required to import a
tablespace to MySQL 5.6 or Percona Server 5.6. A tablespace will be
imported successfully even if it is from another server, but InnoDB will
do schema validation if the corresponding .cfg file is present in the
same directory.
3. “In |InnoDB| versions prior to 5.6” -> “In server versions...”?
4. “However, with the |xtrabackup| binary” – you don’t necessarily have
to use the xtrabackup binary, “innobackupex --apply-log --export” will
work as well. Can we just say “with Percona XtraBackup” in both
innobackupex and xtrabackup sections?
5. We should make it clear that innodb_ import_ table_from_ xtrabackup is import_ table_from_ xtrabackup www.percona. com/doc/ percona- server/ 5.5/management/ innodb_ expand_ import. html#innodb_ import_ table_from_ xtrabackup>`_
only required when importing a table to Percona Server version 5.5 or
lower. Which we do in the following note, but that means the following
text can be removed from preceding paragraph: “... and requires
`innodb_
<http://
to be enabled on the destination server”