-
Committer:
Alexey Kopytov
-
Date:
2013-04-23 06:38:06 UTC
-
mto:
This revision was merged to the branch mainline in
revision
545.
-
Revision ID:
akopytov@gmail.com-20130423063806-mmbk2x1u3tkrba3v
Implementation of
https://blueprints.launchpad.net/percona-xtrabackup/+spec/support-remote-tablespaces
On backup, copy both .isl and .ibd files for remote tablespaces. Remote
.ibd files are copied to the corresponding database directory under the
backup root directory as if there were local tablespaces.
On prepare, ignore .isl files and possible inconsistencies of tablespace
locations with the data dictionary, i.e. handle all tablespaces as local
ones.
On restore, innobackupex checks if there's an .isl file corresponding to
the .ibd file being copied. If so, it uses the original remote
tablespace location instead of the default location under the data
directory.
Changes in the ib_part_* tests are necessery to support 2 additional SYS_*
tables in the data dictionary (SYS_TABLESPACES and SYS_DATAFILES). To
avoid dependency on the number of SYS_* tables, they are now excluded
from the 'xtrabackup --stats' output, i.e. only user tables are counted.