The xtrabackup in Percona is really a good tool to simply introduce his features:
1, create hot backup (mainly rely on InnoDB crash recovery function)
2. Incremental backup
3, directly to the backup file compression package
4. Small load
The problem was found when testing the latest version 2.0:
This tool in importing and exporing individual tables does not work with Oracle's original MySQL.
This column more highlights: http://www.bianceng.cn/database/MySQL/
Explained as follows: In the original MySQL is not allowed to move the database. IDB file, the official explanation is: The table definition this is stored in the InnoDB shared tablespace includes the Database name, and Becauseinnodb must preserve the consistency of transaction IDs and log sequence numbers. That is, the table definition is stored in a shared tablespace in InnoDB, and the transaction ID and log sequence number are placed in a single table space file. (This restriction has been removed in the Percona server)
After consultation: This tool for the original MySQL is still available. Specifically as follows:
To back up a single table:
Innobackupex--tables-file=/tmp/tables.txt/path/to/backup
The key is the following step:
--export First Use this option to obtain a fully independent IDB file (not officially mentioned)
Innobackupex--defaults-file=/usr/local/mysql/my.cnf--export/tmp
The following is a consistent backup of the application log:
Innobackupex--defaults-file=/usr/local/mysql/my.cnf--export--apply-log/path/to/backup
Finally, import tablespace;