最近用innobackup进行备份测试，我们只备份一个innodb类型的库，数据大小大概50多G，用innobackupex大概用了5个多小时，但是mysqldump只用了大约2个小时，这让我很费解，有哪位知道的同志能够交流下？按理说innobackupex应该快的，还有就是大家在备份时不要放到高峰期，因为innobackupex备份时比较吃系统IO，下面就是我备份脚本，分为全备和增备，使用innobackupex需要安装依赖包：

  1. yum install perl-DBD-MySQL*

一、全备

1、全备脚本

--全备到远程服务器

  1. /data/mysql/bin/innobackupex  --defaults-file=/etc/my.cnf --user=root  --password="*******" --database=report
  2. --stream=tar /data/backup/fullbackup 2>/data/backup/fullbackup/bak.log |gzip| ssh root@192.168.1.1 "cat - > /data/backup/fullbackup/`date +%F_%H-%M-%S`.tar.gz "

--全量备份到本地

  1. /data/mysql/bin/innobackupex  --defaults-file=/etc/my.cnf --user=root  --password="******" --database=report
  2. --stream=tar /data/backup/fullbackup 2>/data/backup/fullbackup/bak.log | gzip > /data/backup/fullbackup/`date +%F_%H-%M-%S`.tar.gz

注意事项：1、--defaults-file参数需要放在第一个位置，否则报错提示，通过这个参数，将数据文件（由cnf里的变量datadir指定）拷贝至备份目录下。备份成功后，将在备份目录下创建一个时间戳目录，在该目录下存放备份文件。

2、--stream=tar表示通过流的方式将文件传送给tar进行归档。

　　　　　3、还有其他的参数请参考官方文档。

2、全备恢复
--解压

  1. tar -izxvf 2015-10-26_18-11-16.tar.gz -C 2015-10-26_18-11-16

注意事项：需要添加-i参数，否则解压出来的文件不全，通过-C指定目标目录
--全量恢复：假设恢复还原到3307端口的库中

恢复分为两步，第一步需要“prepare”，其实就是xtrabackup应用事务日志，对于已经commit的操作进行前滚，对于rollback的操作进行回滚，这个跟crash recovery类似。
     --应用日志：

  1. /data/mysql/bin/innobackupex --apply-log  /data/backup/fullbackup/2015-10-26_18-11-16

注意：apply-log后备份目录会出现xtrabackup_binlog_pos_innodb，这个文件记录应用到binlog日志的文件和位置。有时可能会有xtrabackup_binlog_info文件，如果做从库，那么以哪个为准呢？

1 对于纯 InnoDB 操作，备份出来的数据中上述两个文件的内容是一致的
           2 对于 InnoDB 和非事务存储引擎混合操作，xtrabackup_binlog_info 中所示的 position 应该会比 xtrabackup_pos_innodb 所示的数值大。此时应以 xtrabackup_binlog_info 为准；

--copy文件

  1. #需先关闭mysql服务
  2. /data/mysql/bin/mysqladmin -S /tmp/mysql3307.sock --user=root  --password="*******" shutdown
  3. #删除数据库目录文件和日志
  4.  rm -rf /data/mysql/data2/report ib*
  5. #进行文件同步
  6. rsync -avz report ib* /data/mysql/data2
  7. #最后别忘了修改权限
  8. chown -R mysql:mysql /data/mysql/data2/*

注意事项：使用--copy-back，要求data目录下面为空，如不为空，会报错如下Original data directory /data/mysql/data2 is not empty!这种适合备份实例下的所有数据库的情况，这时可以清空data目录。但是不适合只备份特定的某些库，由于我们是备份特定report库，所以这里直接用rsync来同步文件。下面的是官方的copy-back供参考：

  1. /data/mysql/bin/innobackupex   --defaults-file=/etc/my_3307.cnf --copy-back  /data/backup/fullbackup/2015-10-26_18-11-16

到这里，数据库就恢复还原好了，可以重新启动mysql服务，登录mysql查看数据恢复情况。一般来说全备的恢复比较简单。但是每次备份的数据量比较大，时间也长，大家根据实际情况决定备份方式。

二、增备
增量备份：以某个特定的全备为基础，个人理解可以细分两种：一种是每天都以该全备为基础进行增备。另一种是以前一天的增量为基础进行增量。

  1. /data/mysql/bin/innobackupex  --user=root  --password="*******" --database=report
  2. --incremental --incremental-basedir=/data/backup/fullbackup/2015-10-27_15-27-04 /data/backup/fullbackup

注意事项：--incremental参数指明用增量备份方式；--incremental-basedir参数指定以哪个全备为基础

对于第一种恢复方法：

  1. /data/mysql/bin/innobackupex --apply-log --redo-only /data/backup/fullbackup/2015-10-27_15-27-04
  2. /data/mysql/bin/innobackupex --apply-log /data/backup/fullbackup/2015-10-27_15-27-04 --incremental-dir=/data/backup/fullbackup/2015-10-27_16-28-40

对于第二种恢复方法：

  1. /data/mysql/bin/innobackupex --apply-log --redo-only /data/backup/fullbackup/2015-10-27_14-20-35
  2. /data/mysql/bin/innobackupex --apply-log --redo-only /data/backup/fullbackup/2015-10-27_14-20-37
  3. ......redo每一天的增量
  4. /data/mysql/bin/innobackupex --apply-log /data/backup/fullbackup/2015-10-27_14-20-35 --incremental-dir=/data/backup/fullbackup/2015-10-27_14-35-11

注意事项：

对于第一种方式:由于每次都是以全备为基础增量，所以只需恢复全备和最后一次的增量即可。

对于第二种方式：需要按顺序对全备，第一次增备...第N-1次增备进行应用事务日志文件，最后一次的增量不需要，最终日志都应用到全备中了，故最后只需要将全备文件夹中的文件copy到对应data目录即可。

三、从全备中恢复指定的表

其实，我们很多情况下并不需要恢复整个库，更多的是恢复指定的表，如果用mysqldump备份的就非常蛋疼了，我曾经从一个mysqldump备份的70G文件中抽取恢复一张有2000万记录的表，可想而知，这种方式效率有多低下吧，下面我介绍下应用innobackupex全备情况下，如何恢复还原指定表。

使用innobackupex恢复指定表前提条件：

  • 源和目标数据库server需要使用独立表空间，即开启InnoDB_File_Per_Table = ON参数
  • 目标数据库需要使用mysql5.6及以上版本或者xtradb引擎，源数据库不作限制

【恢复还原】

1、应用日志，这里需要加上--export参数：

  1. /data/mysql/bin/innobackupex --apply-log --export /data/backup/test

打印应用日志过程如下：

  1.  InnoDB: Table kartriderrushplus3_log/t_order_notify_log in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  2.  InnoDB: It will be removed from the data dictionary.
  3.  InnoDB: Please refer to
  4.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  5.  InnoDB: for how to resolve the issue.
  6.  InnoDB: Table kartriderrushplus3_log/t_tsi_transaction_sync_error in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  7.  InnoDB: It will be removed from the data dictionary.
  8.  InnoDB: Please refer to
  9.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  10.  InnoDB: for how to resolve the issue.
  11.  InnoDB: Table kartriderrushplus3_log/t_user_buy_item_count_log in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  12.  InnoDB: It will be removed from the data dictionary.
  13.  InnoDB: Please refer to
  14.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  15.  InnoDB: for how to resolve the issue.
  16.  InnoDB: Table kartriderrushplus3_log/t_user_kart_log in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  17.  InnoDB: It will be removed from the data dictionary.
  18.  InnoDB: Please refer to
  19.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  20.  InnoDB: for how to resolve the issue.
  21.  InnoDB: Table kartriderrushplus3_log/t_user_lotto_log in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  22.  InnoDB: It will be removed from the data dictionary.
  23.  InnoDB: Please refer to
  24.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  25.  InnoDB: for how to resolve the issue.
  26.  InnoDB: Table kartriderrushplus3_log/t_user_lucci_log in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  27.  InnoDB: It will be removed from the data dictionary.
  28.  InnoDB: Please refer to
  29.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  30.  InnoDB: for how to resolve the issue.
  31.  InnoDB: Table kartriderrushplus3_log/t_user_mall_log in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  32.  InnoDB: It will be removed from the data dictionary.
  33.  InnoDB: Please refer to
  34.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  35.  InnoDB: for how to resolve the issue.
  36.  InnoDB: Table kartriderrushplus3_log/t_user_oil_log in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  37.  InnoDB: It will be removed from the data dictionary.
  38.  InnoDB: Please refer to
  39.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  40.  InnoDB: for how to resolve the issue.
  41.  InnoDB: Table kartriderrushplus3_log/t_user_pve_log in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  42.  InnoDB: It will be removed from the data dictionary.
  43.  InnoDB: Please refer to
  44.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  45.  InnoDB: for how to resolve the issue.
  46.  InnoDB: Table kartriderrushplus3_log/t_user_recharge_log in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  47.  InnoDB: It will be removed from the data dictionary.
  48.  InnoDB: Please refer to
  49.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  50.  InnoDB: for how to resolve the issue.
  51.  InnoDB: Table kartriderrushplus3_log/t_user_silver_log in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  52.  InnoDB: It will be removed from the data dictionary.
  53.  InnoDB: Please refer to
  54.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  55.  InnoDB: for how to resolve the issue.
  56.  InnoDB: Table kartriderrushplus3_log/t_user_world_pve_log in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  57.  InnoDB: It will be removed from the data dictionary.
  58.  InnoDB: Please refer to
  59.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  60.  InnoDB: for how to resolve the issue.
  61.  InnoDB: Table mysql/innodb_index_stats in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  62.  InnoDB: It will be removed from the data dictionary.
  63.  InnoDB: Please refer to
  64.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  65.  InnoDB: for how to resolve the issue.
  66.  InnoDB: Table mysql/innodb_table_stats in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  67.  InnoDB: It will be removed from the data dictionary.
  68.  InnoDB: Please refer to
  69.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  70.  InnoDB: for how to resolve the issue.
  71.  InnoDB: Table mysql/slave_master_info in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  72.  InnoDB: It will be removed from the data dictionary.
  73.  InnoDB: Please refer to
  74.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  75.  InnoDB: for how to resolve the issue.
  76.  InnoDB: Table mysql/slave_relay_log_info in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  77.  InnoDB: It will be removed from the data dictionary.
  78.  InnoDB: Please refer to
  79.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  80.  InnoDB: for how to resolve the issue.
  81.  InnoDB: Table mysql/slave_worker_info in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  82.  InnoDB: It will be removed from the data dictionary.
  83.  InnoDB: Please refer to
  84.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  85.  InnoDB: for how to resolve the issue.
  86.  InnoDB: Table test/boxgetitem in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  87.  InnoDB: It will be removed from the data dictionary.
  88.  InnoDB: Please refer to
  89.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  90.  InnoDB: for how to resolve the issue.
  91.  InnoDB: Table test/cart in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  92.  InnoDB: It will be removed from the data dictionary.
  93.  InnoDB: Please refer to
  94.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  95.  InnoDB: for how to resolve the issue.
  96.  InnoDB: Table test/dgoldsilversave in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  97.  InnoDB: It will be removed from the data dictionary.
  98.  InnoDB: Please refer to
  99.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  100.  InnoDB: for how to resolve the issue.
  101.  InnoDB: Table test/getoil in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  102.  InnoDB: It will be removed from the data dictionary.
  103.  InnoDB: Please refer to
  104.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  105.  InnoDB: for how to resolve the issue.
  106.  InnoDB: Table test/getplayahead in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  107.  InnoDB: It will be removed from the data dictionary.
  108.  InnoDB: Please refer to
  109.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  110.  InnoDB: for how to resolve the issue.
  111.  InnoDB: Table test/getplayaheadpnum in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  112.  InnoDB: It will be removed from the data dictionary.
  113.  InnoDB: Please refer to
  114.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  115.  InnoDB: for how to resolve the issue.
  116.  InnoDB: Table test/goldcostitem in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  117.  InnoDB: It will be removed from the data dictionary.
  118.  InnoDB: Please refer to
  119.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  120.  InnoDB: for how to resolve the issue.
  121.  InnoDB: Table test/goldgetcost in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  122.  InnoDB: It will be removed from the data dictionary.
  123.  InnoDB: Please refer to
  124.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  125.  InnoDB: for how to resolve the issue.
  126.  InnoDB: Table test/goldsilversave in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  127.  InnoDB: It will be removed from the data dictionary.
  128.  InnoDB: Please refer to
  129.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  130.  InnoDB: for how to resolve the issue.
  131.  InnoDB: Table test/matchplay in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  132.  InnoDB: It will be removed from the data dictionary.
  133.  InnoDB: Please refer to
  134.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  135.  InnoDB: for how to resolve the issue.
  136.  InnoDB: Table test/mg_basic_stat in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  137.  InnoDB: It will be removed from the data dictionary.
  138.  InnoDB: Please refer to
  139.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  140.  InnoDB: for how to resolve the issue.
  141.  InnoDB: Table test/mg_basic_stat_monthly in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  142.  InnoDB: It will be removed from the data dictionary.
  143.  InnoDB: Please refer to
  144.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  145.  InnoDB: for how to resolve the issue.
  146.  InnoDB: Table test/onlinestatus in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  147.  InnoDB: It will be removed from the data dictionary.
  148.  InnoDB: Please refer to
  149.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  150.  InnoDB: for how to resolve the issue.
  151.  InnoDB: Table test/pvemodepass in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  152.  InnoDB: It will be removed from the data dictionary.
  153.  InnoDB: Please refer to
  154.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  155.  InnoDB: for how to resolve the issue.
  156.  InnoDB: Table test/pvepoint in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  157.  InnoDB: It will be removed from the data dictionary.
  158.  InnoDB: Please refer to
  159.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  160.  InnoDB: for how to resolve the issue.
  161.  InnoDB: Table test/pvepointpasslv in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  162.  InnoDB: It will be removed from the data dictionary.
  163.  InnoDB: Please refer to
  164.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  165.  InnoDB: for how to resolve the issue.
  166.  InnoDB: Table test/pvplog in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  167.  InnoDB: It will be removed from the data dictionary.
  168.  InnoDB: Please refer to
  169.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  170.  InnoDB: for how to resolve the issue.
  171.  InnoDB: Table test/shop_log in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  172.  InnoDB: It will be removed from the data dictionary.
  173.  InnoDB: Please refer to
  174.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  175.  InnoDB: for how to resolve the issue.
  176.  InnoDB: Table test/silvercostitem in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  177.  InnoDB: It will be removed from the data dictionary.
  178.  InnoDB: Please refer to
  179.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  180.  InnoDB: for how to resolve the issue.
  181.  InnoDB: Table test/silvergetcost in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  182.  InnoDB: It will be removed from the data dictionary.
  183.  InnoDB: Please refer to
  184.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  185.  InnoDB: for how to resolve the issue.
  186.  InnoDB: Table test/t_conf_user_level_exp in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  187.  InnoDB: It will be removed from the data dictionary.
  188.  InnoDB: Please refer to
  189.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  190.  InnoDB: for how to resolve the issue.
  191.  InnoDB: Table test/t_monthly_index in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  192.  InnoDB: It will be removed from the data dictionary.
  193.  InnoDB: Please refer to
  194.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  195.  InnoDB: for how to resolve the issue.
  196.  InnoDB: Table test/userlvnum in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  197.  InnoDB: It will be removed from the data dictionary.
  198.  InnoDB: Please refer to
  199.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  200.  InnoDB: for how to resolve the issue.
  201.  InnoDB: Table test/userviplevelnum in the InnoDB data dictionary has tablespace id , but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  202.  InnoDB: It will be removed from the data dictionary.
  203.  InnoDB: Please refer to
  204.  InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  205.  InnoDB: for how to resolve the issue.
  206.  InnoDB:  rollback segment(s) are active.
  207.  InnoDB: Waiting for purge to start
  208.  InnoDB: 5.6. started; log sequence number
  209.  xtrabackup: export option is specified.
  210.  xtrabackup: export metadata of table 'KartRiderRushPlus3/connection_log' to file `./KartRiderRushPlus3/connection_log.exp` ( indexes)
  211.  xtrabackup:     name=PRIMARY, id.low=, page=
  212.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_buy_egg_log' to file `./KartRiderRushPlus3/t_buy_egg_log.exp` ( indexes)
  213.  xtrabackup:     name=PRIMARY, id.low=, page=
  214.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_lotto' to file `./KartRiderRushPlus3/t_user_lotto.exp` ( indexes)
  215.  xtrabackup:     name=PRIMARY, id.low=, page=
  216.  xtrabackup:     name=idx_user_id, id.low=, page=
  217.  xtrabackup:     name=key_user_idx, id.low=, page=
  218.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_treasure_const' to file `./KartRiderRushPlus3/t_conf_treasure_const.exp` ( indexes)
  219.  xtrabackup:     name=PRIMARY, id.low=, page=
  220.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_admin_ptcl_record' to file `./KartRiderRushPlus3/t_admin_ptcl_record.exp` ( indexes)
  221.  xtrabackup:     name=PRIMARY, id.low=, page=
  222.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_server_user_status' to file `./KartRiderRushPlus3/t_server_user_status.exp` ( indexes)
  223.  xtrabackup:     name=PRIMARY, id.low=, page=
  224.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_session' to file `./KartRiderRushPlus3/t_user_session.exp` ( indexes)
  225.  xtrabackup:     name=PRIMARY, id.low=, page=
  226.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_bingo' to file `./KartRiderRushPlus3/t_conf_bingo.exp` ( indexes)
  227.  xtrabackup:     name=PRIMARY, id.low=, page=
  228.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_item_count' to file `./KartRiderRushPlus3/t_user_item_count.exp` ( indexes)
  229.  xtrabackup:     name=PRIMARY, id.low=, page=
  230.  xtrabackup:     name=user_idx_item_idx, id.low=, page=
  231.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_const' to file `./KartRiderRushPlus3/t_conf_const.exp` ( indexes)
  232.  xtrabackup:     name=PRIMARY, id.low=, page=
  233.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_lucci_log' to file `./KartRiderRushPlus3/t_user_lucci_log.exp` ( indexes)
  234.  xtrabackup:     name=PRIMARY, id.low=, page=
  235.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_challenge' to file `./KartRiderRushPlus3/t_user_challenge.exp` ( indexes)
  236.  xtrabackup:     name=PRIMARY, id.low=, page=
  237.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_mark' to file `./KartRiderRushPlus3/t_user_mark.exp` ( indexes)
  238.  xtrabackup:     name=PRIMARY, id.low=, page=
  239.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_apple_charge_error_log' to file `./KartRiderRushPlus3/t_apple_charge_error_log.exp` ( indexes)
  240.  xtrabackup:     name=PRIMARY, id.low=, page=
  241.  xtrabackup:     name=user_idx, id.low=, page=
  242.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_kart_level' to file `./KartRiderRushPlus3/t_conf_kart_level.exp` ( indexes)
  243.  xtrabackup:     name=PRIMARY, id.low=, page=
  244.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_game_item' to file `./KartRiderRushPlus3/t_user_game_item.exp` ( indexes)
  245.  xtrabackup:     name=PRIMARY, id.low=, page=
  246.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_kart_system_level' to file `./KartRiderRushPlus3/t_conf_kart_system_level.exp` ( indexes)
  247.  xtrabackup:     name=PRIMARY, id.low=, page=
  248.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_trace_log_m' to file `./KartRiderRushPlus3/t_trace_log_m.exp` ( indexes)
  249.  xtrabackup:     name=PRIMARY, id.low=, page=
  250.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_apple_charge_notify_log' to file `./KartRiderRushPlus3/t_apple_charge_notify_log.exp` ( indexes)
  251.  xtrabackup:     name=PRIMARY, id.low=, page=
  252.  xtrabackup:     name=user_idx, id.low=, page=
  253.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_mission' to file `./KartRiderRushPlus3/t_conf_mission.exp` ( indexes)
  254.  xtrabackup:     name=PRIMARY, id.low=, page=
  255.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_world_pve_point' to file `./KartRiderRushPlus3/t_conf_world_pve_point.exp` ( indexes)
  256.  xtrabackup:     name=PRIMARY, id.low=, page=
  257.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_gm_broadcast' to file `./KartRiderRushPlus3/t_gm_broadcast.exp` ( indexes)
  258.  xtrabackup:     name=PRIMARY, id.low=, page=
  259.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_pve_clearing' to file `./KartRiderRushPlus3/t_conf_pve_clearing.exp` ( indexes)
  260.  xtrabackup:     name=PRIMARY, id.low=, page=
  261.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_cup_rank_award_log' to file `./KartRiderRushPlus3/t_cup_rank_award_log.exp` ( indexes)
  262.  xtrabackup:     name=PRIMARY, id.low=, page=
  263.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_item_upgrade' to file `./KartRiderRushPlus3/t_conf_item_upgrade.exp` ( indexes)
  264.  xtrabackup:     name=PRIMARY, id.low=, page=
  265.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_world_pve' to file `./KartRiderRushPlus3/t_conf_world_pve.exp` ( indexes)
  266.  xtrabackup:     name=PRIMARY, id.low=, page=
  267.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_bingo_treasure' to file `./KartRiderRushPlus3/t_conf_bingo_treasure.exp` ( indexes)
  268.  xtrabackup:     name=PRIMARY, id.low=, page=
  269.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_buy_oil_money_log' to file `./KartRiderRushPlus3/t_buy_oil_money_log.exp` ( indexes)
  270.  xtrabackup:     name=PRIMARY, id.low=, page=
  271.  xtrabackup: export metadata of table 'KartRiderRushPlus3/questionnaire_info' to file `./KartRiderRushPlus3/questionnaire_info.exp` ( indexes)
  272.  xtrabackup:     name=PRIMARY, id.low=, page=
  273.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_pve_log' to file `./KartRiderRushPlus3/t_user_pve_log.exp` ( indexes)
  274.  xtrabackup:     name=PRIMARY, id.low=, page=
  275.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_decomposition' to file `./KartRiderRushPlus3/t_conf_decomposition.exp` ( indexes)
  276.  xtrabackup:     name=PRIMARY, id.low=, page=
  277.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_status_log_m' to file `./KartRiderRushPlus3/t_status_log_m.exp` ( indexes)
  278.  xtrabackup:     name=PRIMARY, id.low=, page=
  279.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_login_info_log' to file `./KartRiderRushPlus3/t_login_info_log.exp` ( indexes)
  280.  xtrabackup:     name=PRIMARY, id.low=, page=
  281.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_composition' to file `./KartRiderRushPlus3/t_conf_composition.exp` ( indexes)
  282.  xtrabackup:     name=PRIMARY, id.low=, page=
  283.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_speed_force' to file `./KartRiderRushPlus3/t_conf_speed_force.exp` ( indexes)
  284.  xtrabackup:     name=GEN_CLUST_INDEX, id.low=, page=
  285.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_skill_treasure' to file `./KartRiderRushPlus3/t_conf_skill_treasure.exp` ( indexes)
  286.  xtrabackup:     name=PRIMARY, id.low=, page=
  287.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_match_record_log' to file `./KartRiderRushPlus3/t_match_record_log.exp` ( indexes)
  288.  xtrabackup:     name=PRIMARY, id.low=, page=
  289.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_achievement_schedule' to file `./KartRiderRushPlus3/t_user_achievement_schedule.exp` ( indexes)
  290.  xtrabackup:     name=PRIMARY, id.low=, page=
  291.  xtrabackup:     name=user_idx_achievement_group_id, id.low=, page=
  292.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user' to file `./KartRiderRushPlus3/t_user.exp` ( indexes)
  293.  xtrabackup:     name=PRIMARY, id.low=, page=
  294.  xtrabackup:     name=id, id.low=, page=
  295.  xtrabackup:     name=key_name, id.low=, page=
  296.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_achievement' to file `./KartRiderRushPlus3/t_conf_achievement.exp` ( indexes)
  297.  xtrabackup:     name=PRIMARY, id.low=, page=
  298.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_pve' to file `./KartRiderRushPlus3/t_conf_pve.exp` ( indexes)
  299.  xtrabackup:     name=PRIMARY, id.low=, page=
  300.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_oil_money' to file `./KartRiderRushPlus3/t_conf_oil_money.exp` ( indexes)
  301.  xtrabackup:     name=PRIMARY, id.low=, page=
  302.  xtrabackup: export metadata of table 'KartRiderRushPlus3/user_extend' to file `./KartRiderRushPlus3/user_extend.exp` ( indexes)
  303.  xtrabackup:     name=PRIMARY, id.low=, page=
  304.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_questionnaire' to file `./KartRiderRushPlus3/t_conf_questionnaire.exp` ( indexes)
  305.  xtrabackup:     name=PRIMARY, id.low=, page=
  306.  xtrabackup: export metadata of table 'KartRiderRushPlus3/face_img' to file `./KartRiderRushPlus3/face_img.exp` ( indexes)
  307.  xtrabackup:     name=PRIMARY, id.low=, page=
  308.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_mall' to file `./KartRiderRushPlus3/t_conf_mall.exp` ( indexes)
  309.  xtrabackup:     name=PRIMARY, id.low=, page=
  310.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_pve_ai' to file `./KartRiderRushPlus3/t_conf_pve_ai.exp` ( indexes)
  311.  xtrabackup:     name=PRIMARY, id.low=, page=
  312.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_world_pve' to file `./KartRiderRushPlus3/t_user_world_pve.exp` ( indexes)
  313.  xtrabackup:     name=PRIMARY, id.low=, page=
  314.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_shop' to file `./KartRiderRushPlus3/t_conf_shop.exp` ( indexes)
  315.  xtrabackup:     name=PRIMARY, id.low=, page=
  316.  xtrabackup: export metadata of table 'KartRiderRushPlus3/status_log' to file `./KartRiderRushPlus3/status_log.exp` ( indexes)
  317.  xtrabackup:     name=PRIMARY, id.low=, page=
  318.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_hot_time' to file `./KartRiderRushPlus3/t_conf_hot_time.exp` ( indexes)
  319.  xtrabackup:     name=PRIMARY, id.low=, page=
  320.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_pve_award' to file `./KartRiderRushPlus3/t_conf_pve_award.exp` ( indexes)
  321.  xtrabackup:     name=PRIMARY, id.low=, page=
  322.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_mail_box' to file `./KartRiderRushPlus3/t_mail_box.exp` ( indexes)
  323.  xtrabackup:     name=PRIMARY, id.low=, page=
  324.  xtrabackup:     name=key_user_idx, id.low=, page=
  325.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_device' to file `./KartRiderRushPlus3/t_user_device.exp` ( indexes)
  326.  xtrabackup:     name=PRIMARY, id.low=, page=
  327.  xtrabackup:     name=IX_user_device_user_idx, id.low=, page=
  328.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_item_log' to file `./KartRiderRushPlus3/t_user_item_log.exp` ( indexes)
  329.  xtrabackup:     name=PRIMARY, id.low=, page=
  330.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_admin_user_ping_log' to file `./KartRiderRushPlus3/t_admin_user_ping_log.exp` ( indexes)
  331.  xtrabackup:     name=PRIMARY, id.low=, page=
  332.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_point_log' to file `./KartRiderRushPlus3/t_user_point_log.exp` ( indexes)
  333.  xtrabackup:     name=PRIMARY, id.low=, page=
  334.  xtrabackup:     name=UN_t_user_point_log_stat_date_user_idx, id.low=, page=
  335.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_user_level' to file `./KartRiderRushPlus3/t_conf_user_level.exp` ( indexes)
  336.  xtrabackup:     name=PRIMARY, id.low=, page=
  337.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_item_skill_upgrade_log' to file `./KartRiderRushPlus3/t_item_skill_upgrade_log.exp` ( indexes)
  338.  xtrabackup:     name=PRIMARY, id.low=, page=
  339.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_treasure' to file `./KartRiderRushPlus3/t_conf_treasure.exp` ( indexes)
  340.  xtrabackup:     name=PRIMARY, id.low=, page=
  341.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_rp_item' to file `./KartRiderRushPlus3/t_conf_rp_item.exp` ( indexes)
  342.  xtrabackup:     name=PRIMARY, id.low=, page=
  343.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_kart_ranking' to file `./KartRiderRushPlus3/t_user_kart_ranking.exp` ( indexes)
  344.  xtrabackup:     name=PRIMARY, id.low=, page=
  345.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_composition_log' to file `./KartRiderRushPlus3/t_composition_log.exp` ( indexes)
  346.  xtrabackup:     name=PRIMARY, id.low=, page=
  347.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_vip' to file `./KartRiderRushPlus3/t_conf_vip.exp` ( indexes)
  348.  xtrabackup:     name=PRIMARY, id.low=, page=
  349.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_prohibit_str' to file `./KartRiderRushPlus3/t_conf_prohibit_str.exp` ( indexes)
  350.  xtrabackup:     name=PRIMARY, id.low=, page=
  351.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_pve_point' to file `./KartRiderRushPlus3/t_conf_pve_point.exp` ( indexes)
  352.  xtrabackup:     name=PRIMARY, id.low=, page=
  353.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_skill' to file `./KartRiderRushPlus3/t_conf_skill.exp` ( indexes)
  354.  xtrabackup:     name=PRIMARY, id.low=, page=
  355.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_notice' to file `./KartRiderRushPlus3/t_conf_notice.exp` ( indexes)
  356.  xtrabackup:     name=PRIMARY, id.low=, page=
  357.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_mall' to file `./KartRiderRushPlus3/t_user_mall.exp` ( indexes)
  358.  xtrabackup:     name=PRIMARY, id.low=, page=
  359.  xtrabackup:     name=user_idx_item_idx, id.low=, page=
  360.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_charge' to file `./KartRiderRushPlus3/t_user_charge.exp` ( indexes)
  361.  xtrabackup:     name=PRIMARY, id.low=, page=
  362.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_admin_section_record' to file `./KartRiderRushPlus3/t_admin_section_record.exp` ( indexes)
  363.  xtrabackup:     name=PRIMARY, id.low=, page=
  364.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_order' to file `./KartRiderRushPlus3/t_order.exp` ( indexes)
  365.  xtrabackup:     name=PRIMARY, id.low=, page=
  366.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_game_item_probability' to file `./KartRiderRushPlus3/t_conf_game_item_probability.exp` ( indexes)
  367.  xtrabackup:     name=PRIMARY, id.low=, page=
  368.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_sport' to file `./KartRiderRushPlus3/t_conf_sport.exp` ( indexes)
  369.  xtrabackup:     name=PRIMARY, id.low=, page=
  370.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_game_item_treasure_log' to file `./KartRiderRushPlus3/t_game_item_treasure_log.exp` ( indexes)
  371.  xtrabackup:     name=PRIMARY, id.low=, page=
  372.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_point' to file `./KartRiderRushPlus3/t_user_point.exp` ( indexes)
  373.  xtrabackup:     name=PRIMARY, id.low=, page=
  374.  xtrabackup:     name=IX_t_user_point_point_last_update_time, id.low=, page=
  375.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_login_reward' to file `./KartRiderRushPlus3/t_conf_login_reward.exp` ( indexes)
  376.  xtrabackup:     name=PRIMARY, id.low=, page=
  377.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_mall_package' to file `./KartRiderRushPlus3/t_conf_mall_package.exp` ( indexes)
  378.  xtrabackup:     name=PRIMARY, id.low=, page=
  379.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_order_notify_log' to file `./KartRiderRushPlus3/t_order_notify_log.exp` ( indexes)
  380.  xtrabackup:     name=PRIMARY, id.low=, page=
  381.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_item_count_log' to file `./KartRiderRushPlus3/t_user_item_count_log.exp` ( indexes)
  382.  xtrabackup:     name=PRIMARY, id.low=, page=
  383.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_egg' to file `./KartRiderRushPlus3/t_user_egg.exp` ( indexes)
  384.  xtrabackup:     name=PRIMARY, id.low=, page=
  385.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_item_upgrade_log' to file `./KartRiderRushPlus3/t_item_upgrade_log.exp` ( indexes)
  386.  xtrabackup:     name=PRIMARY, id.low=, page=
  387.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_pve_detail' to file `./KartRiderRushPlus3/t_user_pve_detail.exp` ( indexes)
  388.  xtrabackup:     name=PRIMARY, id.low=, page=
  389.  xtrabackup:     name=key_user_idx, id.low=, page=
  390.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_guide' to file `./KartRiderRushPlus3/t_conf_guide.exp` ( indexes)
  391.  xtrabackup:     name=PRIMARY, id.low=, page=
  392.  xtrabackup: export metadata of table 'KartRiderRushPlus3/prohibit_str' to file `./KartRiderRushPlus3/prohibit_str.exp` ( indexes)
  393.  xtrabackup:     name=GEN_CLUST_INDEX, id.low=, page=
  394.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_decomposition_log' to file `./KartRiderRushPlus3/t_decomposition_log.exp` ( indexes)
  395.  xtrabackup:     name=PRIMARY, id.low=, page=
  396.  xtrabackup: export metadata of table 'KartRiderRushPlus3/temp_kart_ranking_params' to file `./KartRiderRushPlus3/temp_kart_ranking_params.exp` ( indexes)
  397.  xtrabackup:     name=PRIMARY, id.low=, page=
  398.  xtrabackup:     name=item_idx item_level item_control_level, id.low=, page=
  399.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_track_definition' to file `./KartRiderRushPlus3/t_conf_track_definition.exp` ( indexes)
  400.  xtrabackup:     name=PRIMARY, id.low=, page=
  401.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_kart_system_group' to file `./KartRiderRushPlus3/t_conf_kart_system_group.exp` ( indexes)
  402.  xtrabackup:     name=PRIMARY, id.low=, page=
  403.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_silver_log' to file `./KartRiderRushPlus3/t_user_silver_log.exp` ( indexes)
  404.  xtrabackup:     name=PRIMARY, id.low=, page=
  405.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_kart_definition' to file `./KartRiderRushPlus3/t_conf_kart_definition.exp` ( indexes)
  406.  xtrabackup:     name=PRIMARY, id.low=, page=
  407.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_tsi_transaction_sync_error' to file `./KartRiderRushPlus3/t_tsi_transaction_sync_error.exp` ( indexes)
  408.  xtrabackup:     name=PRIMARY, id.low=, page=
  409.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_buy_shop_log' to file `./KartRiderRushPlus3/t_buy_shop_log.exp` ( indexes)
  410.  xtrabackup:     name=PRIMARY, id.low=, page=
  411.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_skill_random' to file `./KartRiderRushPlus3/t_conf_skill_random.exp` ( indexes)
  412.  xtrabackup:     name=PRIMARY, id.low=, page=
  413.  xtrabackup: export metadata of table 'KartRiderRushPlus3/user_login_daily' to file `./KartRiderRushPlus3/user_login_daily.exp` ( indexes)
  414.  xtrabackup:     name=PRIMARY, id.low=, page=
  415.  xtrabackup:     name=user_idx, id.low=, page=
  416.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_match_item' to file `./KartRiderRushPlus3/t_conf_match_item.exp` ( indexes)
  417.  xtrabackup:     name=GEN_CLUST_INDEX, id.low=, page=
  418.  xtrabackup: export metadata of table 'KartRiderRushPlus3/cdk' to file `./KartRiderRushPlus3/cdk.exp` ( indexes)
  419.  xtrabackup:     name=PRIMARY, id.low=, page=
  420.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_prohibit_str_old' to file `./KartRiderRushPlus3/t_conf_prohibit_str_old.exp` ( indexes)
  421.  xtrabackup:     name=GEN_CLUST_INDEX, id.low=, page=
  422.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_egg' to file `./KartRiderRushPlus3/t_conf_egg.exp` ( indexes)
  423.  xtrabackup:     name=PRIMARY, id.low=, page=
  424.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_attribute_point' to file `./KartRiderRushPlus3/t_conf_attribute_point.exp` ( indexes)
  425.  xtrabackup:     name=PRIMARY, id.low=, page=
  426.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_manager_status_log' to file `./KartRiderRushPlus3/t_manager_status_log.exp` ( indexes)
  427.  xtrabackup:     name=PRIMARY, id.low=, page=
  428.  xtrabackup: export metadata of table 'KartRiderRushPlus3/users_buy_oil_money_info' to file `./KartRiderRushPlus3/users_buy_oil_money_info.exp` ( indexes)
  429.  xtrabackup:     name=PRIMARY, id.low=, page=
  430.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_pvp' to file `./KartRiderRushPlus3/t_user_pvp.exp` ( indexes)
  431.  xtrabackup:     name=PRIMARY, id.low=, page=
  432.  xtrabackup:     name=pvp_point, id.low=, page=
  433.  xtrabackup:     name=pvp_point_team, id.low=, page=
  434.  xtrabackup:     name=pvp_point_speed, id.low=, page=
  435.  xtrabackup:     name=temp_pvp_point_total, id.low=, page=
  436.  xtrabackup:     name=pvp_point_total, id.low=, page=
  437.  xtrabackup: export metadata of table 'KartRiderRushPlus3/test' to file `./KartRiderRushPlus3/test.exp` ( indexes)
  438.  xtrabackup:     name=PRIMARY, id.low=, page=
  439.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_sport' to file `./KartRiderRushPlus3/t_user_sport.exp` ( indexes)
  440.  xtrabackup:     name=PRIMARY, id.low=, page=
  441.  xtrabackup:     name=user_idx sport_idx, id.low=, page=
  442.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_pve' to file `./KartRiderRushPlus3/t_user_pve.exp` ( indexes)
  443.  xtrabackup:     name=PRIMARY, id.low=, page=
  444.  xtrabackup:     name=key_user_idx, id.low=, page=
  445.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_mail' to file `./KartRiderRushPlus3/t_conf_mail.exp` ( indexes)
  446.  xtrabackup:     name=PRIMARY, id.low=, page=
  447.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_item' to file `./KartRiderRushPlus3/t_conf_item.exp` ( indexes)
  448.  xtrabackup:     name=PRIMARY, id.low=, page=
  449.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_item' to file `./KartRiderRushPlus3/t_user_item.exp` ( indexes)
  450.  xtrabackup:     name=PRIMARY, id.low=, page=
  451.  xtrabackup:     name=key_user_idx, id.low=, page=
  452.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_match_room_log' to file `./KartRiderRushPlus3/t_match_room_log.exp` ( indexes)
  453.  xtrabackup:     name=PRIMARY, id.low=, page=
  454.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_mission' to file `./KartRiderRushPlus3/t_user_mission.exp` ( indexes)
  455.  xtrabackup:     name=PRIMARY, id.low=, page=
  456.  xtrabackup:     name=idx_user_id, id.low=, page=
  457.  xtrabackup:     name=key_user_idx, id.low=, page=
  458.  xtrabackup: export metadata of table 'KartRiderRushPlus3/user_login_continuous' to file `./KartRiderRushPlus3/user_login_continuous.exp` ( indexes)
  459.  xtrabackup:     name=PRIMARY, id.low=, page=
  460.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_achievement' to file `./KartRiderRushPlus3/t_user_achievement.exp` ( indexes)
  461.  xtrabackup:     name=PRIMARY, id.low=, page=
  462.  xtrabackup:     name=user_idx_achievement_idx, id.low=, page=
  463.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_treasure_in_item' to file `./KartRiderRushPlus3/t_conf_treasure_in_item.exp` ( indexes)
  464.  xtrabackup:     name=PRIMARY, id.low=, page=
  465.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_friend_info' to file `./KartRiderRushPlus3/t_friend_info.exp` ( indexes)
  466.  xtrabackup:     name=PRIMARY, id.low=, page=
  467.  xtrabackup:     name=user_idx, id.low=, page=
  468.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_vip' to file `./KartRiderRushPlus3/t_user_vip.exp` ( indexes)
  469.  xtrabackup:     name=PRIMARY, id.low=, page=
  470.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_face' to file `./KartRiderRushPlus3/t_conf_face.exp` ( indexes)
  471.  xtrabackup:     name=PRIMARY, id.low=, page=
  472.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_match_room_session' to file `./KartRiderRushPlus3/t_match_room_session.exp` ( indexes)
  473.  xtrabackup:     name=PRIMARY, id.low=, page=
  474.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_conf_item_fall_address' to file `./KartRiderRushPlus3/t_conf_item_fall_address.exp` ( indexes)
  475.  xtrabackup:     name=PRIMARY, id.low=, page=
  476.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_match_player_log' to file `./KartRiderRushPlus3/t_match_player_log.exp` ( indexes)
  477.  xtrabackup:     name=PRIMARY, id.low=, page=
  478.  xtrabackup: export metadata of table 'KartRiderRushPlus3/users_cdk' to file `./KartRiderRushPlus3/users_cdk.exp` ( indexes)
  479.  xtrabackup:     name=PRIMARY, id.low=, page=
  480.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_pve_ranking' to file `./KartRiderRushPlus3/t_user_pve_ranking.exp` ( indexes)
  481.  xtrabackup:     name=PRIMARY, id.low=, page=
  482.  xtrabackup:     name=idx, id.low=, page=
  483.  xtrabackup: export metadata of table 'KartRiderRushPlus3/t_user_item_strengthen_log' to file `./KartRiderRushPlus3/t_user_item_strengthen_log.exp` ( indexes)
  484.  xtrabackup:     name=PRIMARY, id.low=, page=
  485.  xtrabackup: Last MySQL binlog file position , file name mysql-bin.
  486.  
  487.  xtrabackup: starting shutdown with innodb_fast_shutdown =
  488.  InnoDB: FTS optimize thread exiting.
  489.  InnoDB: Starting shutdown...
  490.  InnoDB: Shutdown completed; log sequence number
  491.  xtrabackup: using the following InnoDB configuration for recovery:
  492.  xtrabackup:   innodb_data_home_dir = ./
  493.  xtrabackup:   innodb_data_file_path = ibdata1:10M:autoextend
  494.  xtrabackup:   innodb_log_group_home_dir = ./
  495.  xtrabackup:   innodb_log_files_in_group =
  496.  xtrabackup:   innodb_log_file_size =
  497.  InnoDB: Using atomics to ref count buffer pool pages
  498.  InnoDB: The InnoDB memory heap is disabled
  499.  InnoDB: Mutexes and rw_locks use GCC atomic builtins
  500.  InnoDB: Memory barrier is not used
  501.  InnoDB: Compressed tables use zlib 1.2.
  502.  InnoDB: Using CPU crc32 instructions
  503.  InnoDB: Initializing buffer pool, size = 100.0M
  504.  InnoDB: Completed initialization of buffer pool
  505.  InnoDB: Setting log file ./ib_logfile101 size to  MB
  506.  InnoDB: Progress in MB:
  507.  InnoDB: Setting log file ./ib_logfile1 size to  MB
  508.  InnoDB: Progress in MB:
  509.  InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
  510.  InnoDB: New log files created, LSN=
  511.  InnoDB: Highest supported file format is Barracuda.
  512.  InnoDB:  rollback segment(s) are active.
  513.  InnoDB: Waiting for purge to start
  514.  InnoDB: 5.6. started; log sequence number
  515.  xtrabackup: starting shutdown with innodb_fast_shutdown =
  516.  InnoDB: FTS optimize thread exiting.
  517.  InnoDB: Starting shutdown...
  518.  InnoDB: Shutdown completed; log sequence number
  519.   :: completed OK!

这时，在全备目录下数据库目录中多生成了.cfg和.exp两个文件，如下：

  1. root > ll
  2. -rw-r--r-- 1 root root        490 Nov 11 16:04 users_cdk.cfg
  3. -rw-r--r-- 1 root root      16384 Nov 11 16:04 users_cdk.exp
  4. -rw-rw----  root root        Jul  : users_cdk.frm
  5. -rw-rw----  root root       Jul  : users_cdk.ibd

2、还原指定的t_user_session表数据：

  • 需要在目标库中手工建好与源数据库一致的表结构：（省）
  • discard t_user_session表空间：
  1. mysql> ALTER TABLE t_user_session  DISCARD TABLESPACE;
  2. Query OK,  rows affected (0.01 sec)
  • 从备份目录复制.cfg .ibd文件到目标服务器数据库目录
  1. [root@1.1.1.1]# cp t_user_session.ibd t_user_session.cfg /data/mysql/data/test/
  2. [root@1.1.1.1]#
  • 进入到MySQL之后Import表空间
  1. mysql> ALTER TABLE t_user_session import TABLESPACE;
  2. ERROR 1815 (HY000): Internal error: Cannot reset LSNs in table '"test"."t_user_session"' : Tablespace not found
  3. --该错误是由于数据文件所属权限问题，需要改为mysql用户，比如：
  4. -rw-r--r--1 root  root         Nov  : t_user_session.cfg
  5. -rw-rw---- mysql mysql       Nov  : t_user_session.frm
  6. -rw-r----- root  root   Nov  : t_user_session.ibd
  7. --再次导入表空间
  8. mysql> ALTER TABLE t_user_session import TABLESPACE;
  9. Query OK,  rows affected ( min 22.51 sec)

这时数据就还原完成了，比mysqldump抽取大文件快多了吧。

  1. mysql> select *  from t_user_session limit ;
  2. +------------------+----------+---------------------+---------------------+-------------+----------------------+
  3. | user_session_idx | user_idx | login_time          | logout_time         | logout_type | client_ip            |
  4. +------------------+----------+---------------------+---------------------+-------------+----------------------+
  5. |                 |         | -- :: | -- :: | LOGOUT      | *******************  |
  6. |                 |         | -- :: | -- :: | LOGOUT      | *******************  |
  7. |                 |         | -- :: | -- :: | LOGOUT      | *******************  |
  8. |                 |         | -- :: | -- :: | LOGOUT      | ******************** |
  9. |                 |         | -- :: | -- :: | LOGOUT      | ******************** |
  10. |                 |         | -- :: | -- :: | LOGOUT      | ******************** |
  11. |                 |         | -- :: | -- :: | LOGOUT      | ******************** |
  12. |                 |         | -- :: | -- :: | LOGOUT      | ******************** |
  13. |                 |         | -- :: | -- :: | LOGOUT      | ******************** |
  14. |                |         | -- :: | -- :: | LOGOUT      | ******************** |
  15. +------------------+----------+---------------------+---------------------+-------------+----------------------+
  16.  rows in set (0.00 sec)

【注意点】:

  • 在复制备份文件的时候一定要复制后缀cfg文件,否则在Import的时候就会报Warning.例如如下的信息:

+---------+------+-------------------------------------------------------------------------------------------------------------------------------------------+
| Warning | 1810 | InnoDB: IO Read error: (2, No such file or directory)
Error opening './test/t.cfg', will attempt to import without schema
verification    |
+---------+------+-------------------------------------------------------------------------------------------------------------------------------------------+
cfg文件的用处主要是在MySQL5.6执行"Flush Table xxx
Export;"之后使.ibd文件保持一致性,同时这个文件会生成一个.cfg文件,在做Import的时候会对导入过程进行校验,但是在
MySQL5.6.8版本之后也不是必须要有.cfg文件.如果真没有,在导入的时候有可能就会报出上面的错误,所以为了安全还是复制它.

  • 如果表有外键在Discard的时候执行如下命令:set FOREIGN_KEY_CHECKS=0; 在Import表之后执行以下命令恢复外键检查：set FOREIGN_KEY_CHECKS=1;
  • 从备份目录复制.cfg .ibd文件到目标服务器数据库目录后，别忘了查看文件所属权限，否则报如下错误：ERROR 1815 (HY000): Internal error: Cannot reset LSNs in table '"test"."t_user_session"' : Tablespace not found

四、相关备份脚本

下面提供两个shell写的备份脚本，是转网友的，个人觉得写的挺全的，给大家参考：

1、全备shell脚本

  1.  #!/bin/bash
  2.  user='root'
  3.  passwd='root'
  4.  database=test
  5.  my_config='/etc/my.cnf'
  6.  backup_dir='/data/backup/fullbackup'
  7.  log=$database-$(date +%Y%m%d%H%M).log
  8.  str=$database-$(date +%Y%m%d%H%M).tar.gz
  9.  
  10.  echo "Start to backup at $(date +%Y%m%d%H%M)" >> /data/backup/fullbackup/$log
  11.  if [ ! -d "$backup_dir" ];then
  12.  mkdir -p $backup_dir
  13.  fi
  14.  /data/mysql/bin/innobackupex --defaults-file=$my_config --user=$user --password=$passwd --database=$database --stream=tar $backup_dir >$backup_dir/$log | gzip >$backup_dir/
  15.  
  16.  $str
  17.  if [ $? -eq  ];then
  18.  echo "Backup is finish! at $(date +%Y%m%d%H%M)"  >> /data/backup/fullbackup/$log
  19.  exit
  20.  else
  21.  echo "Backup is Fail! at $(date +%Y%m%d%H%M)"  >> /data/backup/fullbackup/$log
  22.  exit
  23.  fi

2、全备加增备

  1.  #!/bin/bash
  2.  CONFIG_FILE="/etc/my.cnf"
  3.  BACKUP_USER="backup"
  4.  BACKUP_PASSWD="123A456"
  5.  MYSQL_PORT=""
  6.  MYSQL_HOST="127.0.0.1"
  7.  BACKUP_BASE="/home/xtr_backup"
  8.  XTR_BACKUPLOG="/tmp/xtr_mysql_backup.log"
  9.  DATE_DIR=`date +%Y-%m-%d`
  10.  SUNDAY_DATE=`date -d "Last sunday" +%Y-%m-%d`
  11.  DATE_WEEK=`date +%w`
  12.  DATE_TIME=`date +%Y-%m-%d-%H-%M-%S`
  13.  
  14.  ####################################################
  15.  #全量备份函数
  16.  ####################################################
  17.  function Xtr_full_backup ()
  18.  {
  19.           if [ -d "${BACKUP_BASE}/full/${DATE_DIR}" ]
  20.                then
  21.                     rm -rf "${BACKUP_BASE}/full/${DATE_DIR}"
  22.           fi
  23.           if [ ! -d "${BACKUP_BASE}/full" ]
  24.                then
  25.                     mkdir -p "${BACKUP_BASE}/full"
  26.           fi
  27.           innobackupex --defaults-file=${CONFIG_FILE} --user=${BACKUP_USER} --password=${BACKUP_PASSWD} --port=${MYSQL_PORT} --host=${MYSQL_HOST} --no-lock --no-timestamp
  28.  
  29.  "${BACKUP_BASE}/full/${DATE_DIR}" >"/tmp/$$full_backup.log"
  30.           STATS_FULL_LOG=`awk '/innobackupex: completed OK\!/ {print $NF}' "/tmp/$$full_backup.log"`
  31.           if [ "$STATS_FULL_LOG" != "OK!" ]
  32.                then
  33.                     echo "行号LINENO; 脚本名称(basename $0); 函数名称FUNCNAME; 时间DATE_TIME; Innobackupex Full Backup Is Fail">>"$XTR_BACKUPLOG"
  34.                     exit
  35.                else
  36.                     echo "行号LINENO; 脚本名称(basename $0); 函数名称FUNCNAME; 时间DATE_TIME; Innobackupex Full Backup Is Ok">>"$XTR_BACKUPLOG"
  37.                     rm -rf "/tmp/$$full_backup.log"
  38.           fi
  39.  }
  40.  
  41.  ####################################################
  42.  #增量备份函数
  43.  ####################################################
  44.  function Xtr_inc_backup ()
  45.  {
  46.           if [ -d "${BACKUP_BASE}/inc/${SUNDAY_DATE}/${DATE_DIR}" ]
  47.                then
  48.                     rm -rf "${BACKUP_BASE}/inc/${SUNDAY_DATE}/${DATE_DIR}"
  49.           fi
  50.           if [ ! -d "${BACKUP_BASE}/inc/${SUNDAY_DATE}" ]
  51.                then
  52.                     mkdir -p "${BACKUP_BASE}/inc/${SUNDAY_DATE}"
  53.           fi
  54.           if [ ! -d "${BACKUP_BASE}/full/${SUNDAY_DATE}" ]
  55.                then
  56.                     echo "行号LINENO; 脚本名称(basename $0); 函数名称:$FUNCNAME; 时间:$DATE_TIME; Innobackupex Full Dir ${BACKUP_BASE}/full/$SUNDAY_DATE No
  57.  
  58.  Exit">>"$XTR_BACKUPLOG"
  59.                     exit
  60.           fi
  61.           innobackupex --defaults-file=${CONFIG_FILE} --user=${BACKUP_USER} --password=${BACKUP_PASSWD} --port=${MYSQL_PORT} --host=${MYSQL_HOST} --no-timestamp --parallel=
  62.  
  63.  --incremental --incremental-basedir="${BACKUP_BASE}/full/${SUNDAY_DATE}" "${BACKUP_BASE}/inc/${SUNDAY_DATE}/${DATE_DIR}" >"/tmp/$$inc_backup.log"
  64.           STATS_INC_LOG=`awk '/innobackupex: completed OK\!/ {print $NF}' "/tmp/$$inc_backup.log"`
  65.           if [ "$STATS_INC_LOG" != "OK!" ]
  66.                then
  67.                     echo "行号:$LINENO; 脚本名称:$(basename $0); 函数名称:$FUNCNAME; 时间:$DATE_TIME; Innobackupex Inc Backup Is Fail">>"$XTR_BACKUPLOG"
  68.                     exit
  69.                else
  70.                     echo "行号:$LINENO; 脚本名称:$(basename $0); 函数名称:$FUNCNAME; 时间:$DATE_TIME; Innobackupex Inc Backup Is Ok">>"$XTR_BACKUPLOG"
  71.                     rm -rf "/tmp/$$inc_backup.log"
  72.           fi
  73.  }
  74.  
  75.  ####################################################
  76.  #主体备份函数
  77.  ####################################################
  78.  function Main ()
  79.  {
  80.           if [ "${DATE_WEEK}" -eq  ]
  81.                then
  82.                     Xtr_full_backup
  83.                else
  84.                     Xtr_inc_backup
  85.           fi
  86.           exit
  87.  }
  88.  
  89.  ####################################################
  90.  #开始备份
  91.  ####################################################
  92.  Main

mysql innobackupex备份实施的更多相关文章

  1. mysql innobackupex备份工具

    先简单介绍一下这个工具:innobackupexinnobackupex比xtarbackup有更强的功能,它整合了xtrabackup和其他的一些功能,他不但可以全量备份/恢复,还可以基于时间的增量 ...

  2. mysql innobackupex 备份及恢复

    ----------------------------------全量备份恢复-------------------------------------1.生成一个完整的备份 innobackupe ...

  3. Xtrabackup原理及使用innobackupex进行MySQL数据库备份恢复

    Xtrabackup是由percona提供的mysql数据库备份工具,据官方介绍,这也是世界上惟一一款开源的能够对innodb和xtradb数据库进行热备的工具. Xtrabackup中主要包含两个工 ...

  4. Mysql备份系列（3）--innobackupex备份mysql大数据(全量+增量）操作记录

    在日常的linux运维工作中,大数据量备份与还原,始终是个难点.关于mysql的备份和恢复,比较传统的是用mysqldump工具,今天这里推荐另一个备份工具innobackupex.innobacku ...

  5. MySQL innobackupex全量备份恢复

    转自 http://blog.itpub.net/27099995/viewspace-1295099/ 先简单介绍一下这个工具:innobackupexinnobackupex比xtarbackup ...

  6. mysql之 innobackupex备份+binlog日志的完全恢复【转】

    前言: MySQL的完全恢复,我们可以借助于完整的 备份+binlog 来将数据库恢复到故障点. 备份可以是热备与逻辑备份(mysqldump),只要备份与binlog是完整的,都可以实现完全恢复. ...

  7. innobackupex做MySQL增量备份及恢复【转】

    创建备份用户 mysql> grant process,reload,lock tables,replication client on *.* to 'backup'@'localhost' ...

  8. innobackupex 备份数据搭建 MySQL Slave

    简介: 数据量比较大时,使用 innobackupex 备份数据新增 MySQL Slave 节点. 安装 innobackupex 工具,我这里写过一次:http://www.cnblogs.com ...

  9. mysql多种备份方式比较及实现

    Mysql备份 MySQL的备份和还原: 备份:存放为副本-->数据备份 RAID1,RAID10:保证硬件损坏而不会业务中止,不能保证逻辑上的损害 例如:DROP TABLE mydb.tb1 ...

随机推荐

  1. 转：HTTP ---HTTP头的编码问题（Content-Disposition）

    最近在做项目时遇到了一个 case :需要实现一个强制在浏览器中的下载功能(即强制让浏览器弹出下载对话框),并且文件名必须保持和用户之前上传时相同(可能包含非 ASCII 字符). 前一个需求很容易实 ...

  2. maven＋eclipse＋mac＋tomcat 多模块发布

    之前项目中有用到过maven,但是没运行过web的maven,所以这里记录一下. 项目的结构: ---master  //parent ---web-project // ---client-proj ...

  3. Swift迎来了1.0 GM 版(2014.09.09)

    2014年6月2日,swift开发团队将swift语言公之于众.而2014年9月9日迎来了swift的第二个里程碑,swift1.0版本号(GM),这意味着无论你的应用有一部分功能是用swift写的, ...

  4. 【数据挖掘】分类之Naïve Bayes（转载）

    [数据挖掘]分类之Naïve Bayes 1.算法简介 朴素贝叶斯(Naive Bayes)是监督学习的一种常用算法,易于实现,没有迭代,并有坚实的数学理论(即贝叶斯定理)作为支撑. 本文以拼写检查作 ...

  5. X264学习1：简介

    H.264是视频编码标准. X264是它的开源实现,是视频编码器. 目录 [隐藏]  1 编码器特性 2 输入输出文件类型 2.1 输入 2.2 输出 3 preset和tune系统 3.1 --pr ...

  6. oracle10g卸载问题

    oracle10g卸载是一个比较麻烦的事,一般要完全卸载有以下几个步骤: 实现方法:1.开始->设置->控制面板->管理工具->服务停止所有Oracle服务:2.开始-> ...

  7. chattr

    chattr 功能:设置文件隐藏属性常用参数:+    增加某个特殊权限,其他原本存在的参数不动-     删除某个特殊权限,其他原本存在的参数不动=    设置一定,且仅有后面接的参数 i   文件 ...

  8. 如何通过Git命令行把代码提交到github上

    1.http://www.cnblogs.com/leesf456/p/5169765.html   参考博客 背景:最近入手了mac,看见mac上的大神都是在用git命令行推代码,我很羡慕有木有,好 ...

  9. swoole创建TCP服务端和客户端

    服务端: server.php <?php //创建Server对象,监听 127.0.0.1:9501端口    $serv = new swoole_server("127.0.0 ...

  10. Struts2+hibernate+spring 配置事物

    今天自信看了看hibernate的事物配置问题,转载了其他人的日志,仅用来学习. struts+hibernate+spring事务配置 (2009-01-14 21:49:47) 转载▼ 标签: i ...