Support remote InnoDB tablespaces in MySQL 5.6

Registered by Alexey Kopytov on 2012-11-23

InnoDB in MySQL 5.6 allows to specify arbitrary locations for specific tablespaces: https://blogs.oracle.com/mysqlinnodb/entry/choose_the_location_of_your

XtraBackup should correctly backup and restore remote tablespaces.

Blueprint information

Status:
Complete
Approver:
Alexey Kopytov
Priority:
High
Drafter:
Alexey Kopytov
Direction:
Approved
Assignee:
Alexey Kopytov
Definition:
Approved
Series goal:
Accepted for 2.1
Implementation:
Implemented
Milestone target:
None
Started by
Alexey Kopytov on 2013-04-21
Completed by
Alexey Kopytov on 2013-04-29

Whiteboard

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.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.