一次基于innobackupex备份及binlog的单表恢复操作-白红宇

一次基于innobackupex备份及binlog的单表恢复操作

阅读量：5082 次

发布时间：2019-06-13

本文共 14739 字，大约阅读时间需要 49 分钟。

【环境介绍】

系统环境：Red Hat Enterprise Linux Server release 7.0 (Maipo) + Server version: 5.7.18-log MySQL Community Server (GPL)

　　　　　+innobackupex version 2.4.12 Linux (x86_64)+binlog2sql

【背景描述】

当用户进行误操作时，需要使用innobackupex的备份及binlog进行恢复操作。

【实施步骤】

创建测试表：

mysql> use test;

mysql> CREATE TABLE `tb1` (

-> `id` int(11) NOT NULL AUTO_INCREMENT,

-> `name` char(10) DEFAULT NULL,

-> PRIMARY KEY (`id`)

-> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

mysql> insert into tb1 (name) values ('aa'),('bb'),('cc'),('dd');

mysql> select * from tb1;

+----+------+

| id | name |

+----+------+

| 1 | aa |

| 2 | bb |

| 3 | cc |

| 4 | dd |

+----+------+

4 rows in set (0.10 sec)

备份:

innobackupex --defaults-file=/etc/my.cnf --user=root --password=mysql -S /mysqldata/mysql01_1/mysql01_1.sock /root/backup/full

增量添加数据，此部分数据需要从binlog进行恢复

mysql> insert into tb1 (name) values ('aa2'),('bb2'),('cc2'),('dd2');

Query OK, 4 rows affected (0.12 sec)

Records: 4 Duplicates: 0 Warnings: 0

mysql> select * from tb1;

+----+------+

| id | name |

+----+------+

| 1 | aa |

| 2 | bb |

| 3 | cc |

| 4 | dd |

| 5 | aa2 |

| 6 | bb2 |

| 7 | cc2 |

| 8 | dd2 |

+----+------+

8 rows in set (0.00 sec)

模拟误操作：

mysql> drop table tb1;

Query OK, 0 rows affected (0.29 sec)

mysql> show tables;

+----------------+

| Tables_in_test |

+----------------+

| orders_range |

| rang_test |

| range_datetime |

| test1 |

| test2 |

| test3 |

+----------------+

6 rows in set (0.00 sec)

【进行恢复操作步骤】

只需要apply-log即可

innobackupex --defaults-file=/etc/my.cnf --apply-log /root/backup/full/2018-12-15_12-12-51

如果有多个增量备份，需要把全部的增量备份合并到全备中

innobackupex --defaults-file=/etc/my.cnf --user=root --password=mysql -S /mysqldata/mysql01_1/mysql01_1.sock --apply-log --redo-only /root/backup/full/2018-12-15_23-22-13/

innobackupex --defaults-file=/etc/my.cnf --user=root --password=mysql -S /mysqldata/mysql01_1/mysql01_1.sock --apply-log /root/backup/full/2018-12-15_23-22-13/ --incremental-dir=/root/backup/full/inc/2018-12-15_23-25-47/

innobackupex --defaults-file=/etc/my.cnf --user=root --password=mysql -S /mysqldata/mysql01_1/mysql01_1.sock --apply-log /root/backup/full/2018-12-15_23-22-13/

使用mysqlfrm工具查看表结构

[root@mysqldb2 test]# mysqlfrm --diagnostic /root/backup/full/2018-12-15_12-12-51/test/tb1.frm

# WARNING: Cannot generate character set or collation names without the --server option.

# CAUTION: The diagnostic mode is a best-effort parse of the .frm file. As such, it may not identify all of the components of the table correctly. This is especially true for damaged files. It will also not read the default values for the columns and the resulting statement may not be syntactically correct.

# Reading .frm file for /root/backup/full/2018-12-15_12-12-51/test/tb1.frm:

# The .frm file is a TABLE.

# CREATE TABLE Statement:

CREATE TABLE `test`.`tb1` (

`id` int(11) NOT NULL AUTO_INCREMENT,

`name` char(30) DEFAULT NULL,

PRIMARY KEY `PRIMARY` (`id`)

) ENGINE=InnoDB;

#...done.

在测试库中，重新创建该表结构

mysql> CREATE TABLE `test`.`tb1` (

-> `id` int(11) NOT NULL AUTO_INCREMENT,

-> `name` char(30) DEFAULT NULL,

-> PRIMARY KEY `PRIMARY` (`id`)

-> ) ENGINE=InnoDB;

Query OK, 0 rows affected (0.18 sec)

锁定目标表，防止数据写入，如果是麻烦恢复业务，可创建一个备份表

mysql> lock tables tb1 write;

Query OK, 0 rows affected (0.00 sec)

将表discard tablespace

mysql> alter table tb1 discard tablespace;

Query OK, 0 rows affected (0.13 sec)

将备份的表数据文件拷贝到数据库中，并且修改权限

[root@mysqldb2 test]# cp /root/backup/full/2018-12-15_12-12-51/test/{tb1.ibd,b1.cfg} /mysqldata/mysql01_1/test

[root@mysqldb2 test]# chown -R mysql:mysql /mysqldata/mysql01_1/test/tb1.ibd

[root@mysqldb2 test]# ls -trl /mysqldata/mysql01_1/test/tb1.*

-rw-r----- 1 mysql mysql 8586 12月 15 12:20 /mysqldata/mysql01_1/test/tb1.frm

-rw-r----- 1 mysql mysql 98304 12月 15 12:23 /mysqldata/mysql01_1/test/tb1.ibd

[root@mysqldb2 test]#

将表import tablespace，此时会报错，这个错误可以忽略

mysql> alter table tb1 import tablespace;

Query OK, 0 rows affected, 1 warning (0.10 sec)

mysql> show warnings;

+---------+------+------------------------------------------------------------------------------------------------------------------------------------------+

| Level | Code | Message |

+---------+------+------------------------------------------------------------------------------------------------------------------------------------------+

| Warning | 1810 | InnoDB: IO Read error: (2, No such file or directory) Error opening './test/tb1.cfg', will attempt to import without schema verification |

+---------+------+------------------------------------------------------------------------------------------------------------------------------------------+

1 row in set (0.00 sec)

查看数据，此时已经恢复到备份的时间点的数据

mysql> select * from tb1;

+----+------+

| id | name |

+----+------+

| 1 | aa |

| 2 | bb |

| 3 | cc |

| 4 | dd |

+----+------+

4 rows in set (0.00 sec)

mysql> unlock tables;

Query OK, 0 rows affected (0.08 sec)

使用mysqlbinlog从binlog查看drop表的时间点，可以看到时间点为19418

[root@mysqldb2 logs]# mysqlbinlog -v --base64-output=DECODE-ROWS /mysql/mysql57/logs/binlog011.000002 | grep -C 10 -i "DROP"

# at 19330

#181215 12:15:24 server id 21 end_log_pos 19357 Xid = 811

COMMIT/*!*/;

# at 19357

#181215 12:15:57 server id 21 end_log_pos 19418 GTID last_committed=36 sequence_number=37

SET @@SESSION.GTID_NEXT= '4ee31762-fe82-11e8-9aea-000c29c913a2:37'/*!*/;

# at 19418

#181215 12:15:57 server id 21 end_log_pos 19530 Query thread_id=66 exec_time=1 error_code=0

SET TIMESTAMP=1544847357/*!*/;

DROP TABLE `tb1` /* generated by server */

/*!*/;

# at 19530

#181215 12:20:55 server id 21 end_log_pos 19591 GTID last_committed=37 sequence_number=38

SET @@SESSION.GTID_NEXT= '4ee31762-fe82-11e8-9aea-000c29c913a2:38'/*!*/;

# at 19591

#181215 12:20:55 server id 21 end_log_pos 19807 Query thread_id=66 exec_time=0 error_code=0

SET TIMESTAMP=1544847655/*!*/;

CREATE TABLE `test`.`tb1` (

`id` int(11) NOT NULL AUTO_INCREMENT,

`name` char(30) DEFAULT NULL,

[root@mysqldb2 logs]#

使用binlog2sql.py开源工具进行binlog恢复操作，可以具体制定数据库，表名，insert为正常插入操作类型

[root@mysqldb2 logs]# python /root/binlog2sql-master/binlog2sql/binlog2sql.py -uroot -pmysql -dtest -ttb1 -P33061 --start-position=19008 --stop-position=19418 --start-file='binlog011.000002' > recovery_tb1.sql

[root@mysqldb2 logs]# less recovery_tb1.sql

[root@mysqldb2 logs]# cat recovery_tb1.sql

INSERT INTO `test`.`tb1`(`id`, `name`) VALUES (5, 'aa2'); #start 19069 end 19330 time 2018-12-15 12:15:24

INSERT INTO `test`.`tb1`(`id`, `name`) VALUES (6, 'bb2'); #start 19069 end 19330 time 2018-12-15 12:15:24

INSERT INTO `test`.`tb1`(`id`, `name`) VALUES (7, 'cc2'); #start 19069 end 19330 time 2018-12-15 12:15:24

INSERT INTO `test`.`tb1`(`id`, `name`) VALUES (8, 'dd2'); #start 19069 end 19330 time 2018-12-15 12:15:24

[root@mysqldb2 logs]#

该工具还支持闪回模式：-B参数即可

[root@mysqldb2 logs]# python /root/binlog2sql-master/binlog2sql/binlog2sql.py -uroot -pmysql -dtest -ttb1 -P33061 --start-position=19008 --stop-position=19418 --start-file='binlog011.000002' -B

DELETE FROM `test`.`tb1` WHERE `id`=8 AND `name`='dd2' LIMIT 1; #start 19069 end 19330 time 2018-12-15 12:15:24

DELETE FROM `test`.`tb1` WHERE `id`=7 AND `name`='cc2' LIMIT 1; #start 19069 end 19330 time 2018-12-15 12:15:24

DELETE FROM `test`.`tb1` WHERE `id`=6 AND `name`='bb2' LIMIT 1; #start 19069 end 19330 time 2018-12-15 12:15:24

DELETE FROM `test`.`tb1` WHERE `id`=5 AND `name`='aa2' LIMIT 1; #start 19069 end 19330 time 2018-12-15 12:15:24

[root@mysqldb2 logs]#

查看原全备恢复操作数据

mysql> select * from tb1;

+----+------+

| id | name |

+----+------+

| 1 | aa |

| 2 | bb |

| 3 | cc |

| 4 | dd |

+----+------+

4 rows in set (0.00 sec)

进行binlog增量恢复操作

mysql> source /mysql/mysql57/logs/recovery_tb1.sql

Query OK, 1 row affected (0.05 sec)

Query OK, 1 row affected (0.04 sec)

Query OK, 1 row affected (0.01 sec)

Query OK, 1 row affected (0.00 sec)

查看表数据，已经从binlog中恢复

mysql> select * from tb1;

+----+------+

| id | name |

+----+------+

| 1 | aa |

| 2 | bb |

| 3 | cc |

| 4 | dd |

| 5 | aa2 |

| 6 | bb2 |

| 7 | cc2 |

| 8 | dd2 |

+----+------+

8 rows in set (0.00 sec)

至此已经恢复完成，

恢复完成后记得优化表analyze table test.tb1;optimize local table test.tb1;

alter table test.tb1 engine=InnoDB;

binlog2sql工具安装

https://github.com/danfengcao/binlog2sql

binlog2sql安装：

yum -y install epel-release

yum -y install git

[root@mysqldb2 binlog2sql-master]# wget https://bootstrap.pypa.io/get-pip.py

--2018-12-15 12:45:30-- https://bootstrap.pypa.io/get-pip.py

正在解析主机 bootstrap.pypa.io (bootstrap.pypa.io)... 151.101.0.175, 151.101.64.175, 151.101.128.175, ...

正在连接 bootstrap.pypa.io (bootstrap.pypa.io)|151.101.0.175|:443... 已连接。

已发出 HTTP 请求，正在等待回应... 200 OK

长度：1661676 (1.6M) [text/x-python]

正在保存至: “get-pip.py”

100%[===================================================================================================================================================>] 1,661,676 992KB/s 用时 1.6s

2018-12-15 12:45:38 (992 KB/s) - 已保存 “get-pip.py” [1661676/1661676])

[root@mysqldb2 binlog2sql-master]# ls

binlog2sql example get-pip.py LICENSE README.md requirements.txt tests

[root@mysqldb2 binlog2sql-master]# python get-pip.py

Collecting pip

/tmp/tmpS0wyK9/pip.zip/pip/_vendor/urllib3/util/ssl_.py:369: SNIMissingWarning: An HTTPS request has been made, but the SNI (Server Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings

/tmp/tmpS0wyK9/pip.zip/pip/_vendor/urllib3/util/ssl_.py:160: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings

Downloading https://files.pythonhosted.org/packages/c2/d7/90f34cb0d83a6c5631cf71dfe64cc1054598c843a92b400e55675cc2ac37/pip-18.1-py2.py3-none-any.whl (1.3MB)

100% |████████████████████████████████| 1.3MB 105kB/s

Collecting wheel

Downloading https://files.pythonhosted.org/packages/ff/47/1dfa4795e24fd6f93d5d58602dd716c3f101cfd5a77cd9acbe519b44a0a9/wheel-0.32.3-py2.py3-none-any.whl

Installing collected packages: pip, wheel

Successfully installed pip-18.1 wheel-0.32.3

[root@mysqldb2 binlog2sql-master]#

[root@mysqldb2 binlog2sql-master]# pip install -r requirements.txt

Collecting PyMySQL==0.7.11 (from -r requirements.txt (line 1))

/usr/lib/python2.7/site-packages/pip/_vendor/urllib3/util/ssl_.py:369: SNIMissingWarning: An HTTPS request has been made, but the SNI (Server Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings

SNIMissingWarning

/usr/lib/python2.7/site-packages/pip/_vendor/urllib3/util/ssl_.py:160: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings

InsecurePlatformWarning

Downloading https://files.pythonhosted.org/packages/c6/42/c54c280d8418039bd2f61284f99cb6d9e0eae80383fc72ceb6eac67855fe/PyMySQL-0.7.11-py2.py3-none-any.whl (78kB)

100% |████████████████████████████████| 81kB 106kB/s

Collecting wheel==0.29.0 (from -r requirements.txt (line 2))

Downloading https://files.pythonhosted.org/packages/8a/e9/8468cd68b582b06ef554be0b96b59f59779627131aad48f8a5bce4b13450/wheel-0.29.0-py2.py3-none-any.whl (66kB)

100% |████████████████████████████████| 71kB 288kB/s

Collecting mysql-replication==0.13 (from -r requirements.txt (line 3))

Downloading https://files.pythonhosted.org/packages/dd/23/384047702e694139e9fe75a8ba7ad007e8942fd119ebadabc32ce19f70f2/mysql-replication-0.13.tar.gz

Building wheels for collected packages: mysql-replication

Running setup.py bdist_wheel for mysql-replication ... done

Stored in directory: /root/.cache/pip/wheels/91/33/05/32b16ccadd4fc566ff38af96afdeb5d57d49c2f1eff0402164

Successfully built mysql-replication

Installing collected packages: PyMySQL, wheel, mysql-replication

Found existing installation: wheel 0.32.3

Uninstalling wheel-0.32.3:

Successfully uninstalled wheel-0.32.3

Successfully installed PyMySQL-0.7.11 mysql-replication-0.13 wheel-0.29.0

[root@mysqldb2 binlog2sql-master]#

binlog2sql进行恢复需要连接数据库，MyFlash使用更加方便：

https://github.com/Meituan-Dianping/MyFlash

### 一、简介

MyFlash是由美团点评公司技术工程部开发维护的一个回滚DML操作的工具。该工具通过解析v4版本的binlog，完成回滚操作。相对已有的回滚工具，其增加了更多的过滤选项，让回滚更加容易。

**该工具已经在美团点评内部使用**

### 二、详细说明

1. [安装](./doc/INSTALL.md)

2. [使用](./doc/how_to_use.md)

3. [测试用例](./doc/TestCase.md)

### 三、限制

1. binlog格式必须为row,且binlog_row_image=full

2. 仅支持5.6与5.7

3. 只能回滚DML（增、删、改）

### 四、FAQ

1. 实现的原理是什么？

- 答：参考文章http://url.cn/5yVTfLY

2. 支持gtid吗？

- 答：支持。请参考 [使用](./doc/how_to_use.md)

3. 在开启gtid的MySQL server上，应用flashback报错，错误为：ERROR 1782 (HY000) at line 16: @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON. ?

- 答：在导入时加入--skip-gtids

mysqlbinlog --skip-gtids <flashbacklog> | mysql -uxxx -pxxx

4. 如果回滚后的binlog日志尺寸超过20M，在导入时，很耗时。如何处理?

- 答：参考 [使用](./doc/how_to_use.md) ,搜索maxSplitSize。使用该参数可以对文件进行切片