通过全备+主从同步恢复被drop的库或表

MySQL 中drop 等高危误操作后恢复方法

实验目的:

本次实验以恢复drop操作为例,使用不同方法进行误操作的数据恢复.

方法:
利用master同步(本文)]
伪master+Binlog+同步
利用binlog改为realy-log在临时slave更新
没有备份怎么恢复被drop的表(利用undrop-for-innodb)

1.环境
mysql 5.7.23-log
master db210(192.168.99.210)
slave db212(192.168.99.212)
空闲服务器:db211(192.168.99.211)
压力:在做本次实验过程用,使用sysbench同时做读写模拟压力(28thread+10*100000行)

2.本实验的前置条件:

在drop前至少有一次全量备份
从全备到drop操作时间点有全程binlog,并且binlog format='row'

如果没有以上两个备份怎么办?见《无备份的误操作恢复方法》

3.模拟误操作

root@localhost [wenyz]>select count(*) from t2;

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

| count(*) |

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

|  163818 |

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

1 row in set (0.12 sec)

root@localhost [wenyz]>drop table t2;

Query OK, 0 rows affected (0.02 sec)

root@localhost [wenyz]>show master status;

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

| File            | Position  | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set                              |

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

| mysql-bin.000020 | 136445791 |              |                  | 9e912d2b-92f6-11e8-9747-0050568be82c:1-9872111 |

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

1 row in set (0.00 sec)

root@localhost [wenyz]>flush logs;

Query OK, 0 rows affected (1.41 sec)

4.在实验不同方法之前先完成以下步骤:

复制全备份和所有binlog文件到空闲服务器:db211上
以全备恢复到一个临时新实例(临时slave).

5.找到误操作的位置(GTID或binlog pos)



通过查找怀疑的binlog:

[root@db210_19:11:07 /data/57mysql/mysql3506/logs]

#ll

total 75564544

-rw-r----- 1 mysql mysql       177 Jul 29 14:14 mysql-bin.000001

...

-rw-r----- 1 mysql mysql  39336996 Jul 29 19:12 mysql-bin.000020

-rw-r----- 1 mysql mysql     13340 Jul 29 19:12 mysql-bin.index

[root@db210_19:12:48 /data/57mysql/mysql3506/logs] 

binlog文件导出命令:

#mysqlbinlog -v --base64-output=auto /data/57mysql/mysql3506/logs/mysql-bin.000020 >/data/backup/20.sql

binlog文件导出后查找:DROP TABLE `t2`:

在mysql-bin.000020中找到对应位置:

# at 97871478

#180731 19:33:29 server id 1853506  end_log_pos 97871543 CRC32 0x8cd4354d       GTID    last_committed=205567   sequence_number=205570  rbr_only=no     original_committed_timestamp=0  immediate_commit_timestamp=0    transaction_length=0

# original_commit_timestamp=0 (1970-01-01 08:00:00.000000 CST)

# immediate_commit_timestamp=0 (1970-01-01 08:00:00.000000 CST)

/*!80001 SET @@session.original_commit_timestamp=0*//*!*/;

SET @@SESSION.GTID_NEXT= '9e912d2b-92f6-11e8-9747-0050568be82c:9791090'/*!*/;

# at 97871543

#180731 19:33:29 server id 1853506  end_log_pos 97871660 CRC32 0x974a86d8       Query   thread_id=35    exec_time=0     error_code=0

use `wenyz`/*!*/;

SET TIMESTAMP=1533036809/*!*/;

/*!\C utf8 *//*!*/;

SET @@session.character_set_client=33,@@session.collation_connection=33,@@session.collation_server=33/*!*/;

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

/*!*/;

# at 97871660

#180731 19:33:29 server id 1853506  end_log_pos 97871725 CRC32 0xb85257d6       GTID    last_committed=205567   sequence_number=205571  rbr_only=yes    original_committed_timestamp=0  immediate_commit_timestamp=0    transaction_length=0

/*!50718 SET TRANSACTION ISOLATION LEVEL READ COMMITTED*//*!*/;

# original_commit_timestamp=0 (1970-01-01 08:00:00.000000 CST)

# immediate_commit_timestamp=0 (1970-01-01 08:00:00.000000 CST)

/*!80001 SET @@session.original_commit_timestamp=0*//*!*/;

SET @@SESSION.GTID_NEXT= '9e912d2b-92f6-11e8-9747-0050568be82c:9791091'/*!*/;

# at 97871725

6.恢复方法一：

构建主的从库,并通过:start slave sql_thread until sql_before_gtids='9e912d2b-92f6-11e8-9747-0050568be82c:9791090' 试设置SQL回放位置停在drop操作前一个事务.
Executed_Gtid_Set应该停在: 9e912d2b-92f6-11e8-9747-0050568be82c:1-9791089

change master to master_host='db210',master_port=3506,master_user='wyz',master_password='xxxx',master_auto_position=1;

root@localhost [(none)]>start slave io_thread ;

Query OK, 0 rows affected (0.01 sec)

root@localhost [(none)]>show slave status\G;

*************************** 1. row ***************************

               Slave_IO_State: Queueing master event to the relay log

                  Master_Host: db210

                  Master_User: wyz

                  Master_Port: 3506

                Connect_Retry: 60

              Master_Log_File: mysql-bin.000015

          Read_Master_Log_Pos: 10476294

               Relay_Log_File: relay-bin.000001

                Relay_Log_Pos: 4

        Relay_Master_Log_File:

             Slave_IO_Running: Yes

            Slave_SQL_Running: No

              Replicate_Do_DB:

          Replicate_Ignore_DB:

           Replicate_Do_Table:

       Replicate_Ignore_Table:

      Replicate_Wild_Do_Table:

  Replicate_Wild_Ignore_Table:

                   Last_Errno: 0

                   Last_Error:

                 Skip_Counter: 0

          Exec_Master_Log_Pos: 0

              Relay_Log_Space: 27669048

              Until_Condition: None

               Until_Log_File:

                Until_Log_Pos: 0

           Master_SSL_Allowed: No

           Master_SSL_CA_File:

           Master_SSL_CA_Path:

              Master_SSL_Cert:

            Master_SSL_Cipher:

               Master_SSL_Key:

        Seconds_Behind_Master: NULL

Master_SSL_Verify_Server_Cert: No

                Last_IO_Errno: 0

                Last_IO_Error:

               Last_SQL_Errno: 0

               Last_SQL_Error:

  Replicate_Ignore_Server_Ids:

             Master_Server_Id: 1853506

                  Master_UUID: 9e912d2b-92f6-11e8-9747-0050568be82c

             Master_Info_File: /data/57mysql/mysql3506/data/master.info

                    SQL_Delay: 0

          SQL_Remaining_Delay: NULL

      Slave_SQL_Running_State:

           Master_Retry_Count: 86400

                  Master_Bind:

      Last_IO_Error_Timestamp:

     Last_SQL_Error_Timestamp:

               Master_SSL_Crl:

           Master_SSL_Crlpath:

           Retrieved_Gtid_Set: 9e912d2b-92f6-11e8-9747-0050568be82c:6730274-6788383

            Executed_Gtid_Set: 9e912d2b-92f6-11e8-9747-0050568be82c:1-6730273

                Auto_Position: 1

         Replicate_Rewrite_DB:

                 Channel_Name:

           Master_TLS_Version:

1 row in set (0.00 sec)

ERROR:

No query specified

root@localhost [(none)]>

root@localhost [(none)]>start slave sql_thread until sql_before_gtids='9e912d2b-92f6-11e8-9747-0050568be82c:9791090';

Query OK, 0 rows affected (0.00 sec)

查看sql_thread 执行位置停在9791089

root@localhost [(none)]>show slave status\G;

*************************** 1. row ***************************

               Slave_IO_State: Queueing master event to the relay log

                  Master_Host: db210

                  Master_User: wyz

                  Master_Port: 3506

                Connect_Retry: 60

              Master_Log_File: mysql-bin.000079

          Read_Master_Log_Pos: 15969193

               Relay_Log_File: relay-bin.000024

                Relay_Log_Pos: 97871691

        Relay_Master_Log_File: mysql-bin.000020

             Slave_IO_Running: Yes

            Slave_SQL_Running: No

              Replicate_Do_DB:

          Replicate_Ignore_DB:

           Replicate_Do_Table:

       Replicate_Ignore_Table:

      Replicate_Wild_Do_Table:

  Replicate_Wild_Ignore_Table:

                   Last_Errno: 0

                   Last_Error:

                 Skip_Counter: 0

          Exec_Master_Log_Pos: 97871478

              Relay_Log_Space: 15602695666

              Until_Condition: SQL_BEFORE_GTIDS

               Until_Log_File:

                Until_Log_Pos: 0

           Master_SSL_Allowed: No

           Master_SSL_CA_File:

           Master_SSL_CA_Path:

              Master_SSL_Cert:

            Master_SSL_Cipher:

               Master_SSL_Key:

        Seconds_Behind_Master: NULL

Master_SSL_Verify_Server_Cert: No

                Last_IO_Errno: 0

                Last_IO_Error:

               Last_SQL_Errno: 0

               Last_SQL_Error:

  Replicate_Ignore_Server_Ids:

             Master_Server_Id: 1853506

                  Master_UUID: 9e912d2b-92f6-11e8-9747-0050568be82c

             Master_Info_File: /data/57mysql/mysql3506/data/master.info

                    SQL_Delay: 0

          SQL_Remaining_Delay: NULL

      Slave_SQL_Running_State:

           Master_Retry_Count: 86400

                  Master_Bind:

      Last_IO_Error_Timestamp:

     Last_SQL_Error_Timestamp:

               Master_SSL_Crl:

           Master_SSL_Crlpath:

           Retrieved_Gtid_Set: 9e912d2b-92f6-11e8-9747-0050568be82c:6730274-42357224

            Executed_Gtid_Set: 9e912d2b-92f6-11e8-9747-0050568be82c:1-9791089

                Auto_Position: 1

         Replicate_Rewrite_DB:

                 Channel_Name:

           Master_TLS_Version:

1 row in set (0.00 sec)

ERROR:

No query specified

root@localhost [(none)]>

查看数据是否和drop相同:

root@localhost [(none)]>select count(*) from wenyz.t2;

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

| count(*) |

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

|   163818 |

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

1 row in set (0.10 sec)

root@localhost [(none)]>

将数据表导出

/usr/local/mysql57/bin/mysqldump -S /tmp/mysql3506.sock -pxxxx --master-data=2 --single-transaction wenyz t2 >/data/backup/t2.sql

将t2.sql传回master 并导入

[root@db211_20:49:35 /root]

#scp /data/backup/t2.sql db210:/data/backup/

t2.sql

[root@db211_20:50:10 /root]

#/usr/local/mysql57/bin/mysql -S /tmp/mysql3506.sock -pxxxx <t2.sql

mysql: [Warning] Using a password on the command line interface can be insecure.

[root@db210_21:01:36 /data/backup]

#fg

/usr/local/mysql57/bin/mysql --login-path=p3506	(wd: /tmp)

root@localhost [wenyz]>select count(*) from t2;

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

| count(*) |

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

|   163818 |

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

1 row in set (0.40 sec)

通过全备+主从同步恢复被drop的库或表的更多相关文章

通过全备+relaylog同步恢复被drop的库或表【转】
MySQL 中drop 等高危误操作后恢复方法实验目的: 本次实验以恢复drop操作为例,使用不同方法进行误操作的数据恢复. 方法: 利用master同步伪master+Binlog+同步利用b ...
通过全备+binlog_server同步恢复被drop的库或表
MySQL 中drop 等高危误操作后恢复方法实验目的: 本次实验以恢复drop操作为例,使用不同方法进行误操作的数据恢复. 方法: 利用master同步 :伪master+Binlog+同步(本文 ...
通过全备+relaylog同步恢复被drop的库或表
MySQL 中drop 等高危误操作后恢复方法实验目的: 本次实验以恢复drop操作为例,使用不同方法进行误操作的数据恢复. 方法: 利用master同步伪master+Binlog+同步利用b ...
监控MYSQL主从同步配置中监控从库运行状态的脚本
代码如下: #!/bin/bash #Check MySQL Slave's Runnning Status #Crontab time 00:10 MYSQLPORT=`netstat -na|gr ...
Mysql主从同步问题汇总
data-1-1主机是master,data-1-2是slave Last_IO_Errno: 1236 slave查看show slave status\G; 显示Last_IO_Errno: 12 ...
通过 XtraBackup 实现不停机不锁表搭建主从同步
简介 Xtrabackup是由 Percona 开发的一个开源软件,可实现对 InnoDB 的数据备份,支持在线热备份(备份时不影响数据读写).备份时,Xtrabackup 会将 Master 的 b ...
Mysql主从同步(1) - 概念和原理介绍以及主从/主主模式部署记录
Mysql复制概念Mysql内建的复制功能是构建大型高性能应用程序的基础, 将Mysql数据分布到多个系统上,这种分布机制是通过将Mysql某一台主机数据复制到其它主机(slaves)上,并重新执行一 ...
MySQL 主从同步失败，数据表修复
问题描述: 接到报警称一台 MySQL 从库同步失败.登录服务器查看错误日志信息如下: Last_Error: Error 'Incorrect key file for table './bfcc/ ...
MySQL数据库主从同步实战过程
Linux系统MySQL数据库主从同步实战过程安装环境说明系统环境: [root@~]# cat /etc/redhat-release CentOS release 6.5 (Final) ...

随机推荐

牛客练习赛小D的Lemon 解题报告
小D的Lemon 题意已知 \[ g(x)=\left\{\begin{matrix} 1&,x=1\\ \sum_{i=1}^qk_i&,otherwise \end{matrix ...
逆向---01.Nop、中文字符串搜索、保存修改后程序
基础知识:(Nop:删除跳转) gcc编译链接命令: gcc -o 生成文件名源文件名 gcc编译成汇编代码:gcc -o 生成文件名 -S 源文件名 VS查看汇编代码:(调试模式下,Ctrl+F ...
JAVA多线程之中断机制(如何处理中断？)
一,介绍这篇文章主要记录使用 interrupt() 方法中断线程,以及如何对InterruptedException进行处理.感觉对InterruptedException异常进行处理是一件谨慎且 ...
C# 推箱子游戏&对战游戏
推箱子游戏提纲,只有向右向上的操作,向左向下同理,后期需完善. namespace 推箱子 { class Program { static void Main(string[] args) { // ...
A1071. Speech Patterns
People often have a preference among synonyms of the same word. For example, some may prefer "t ...
（母函数 Catalan数大数乘法大数除法） Train Problem II hdu1023
Train Problem II Time Limit: 2000/1000 MS (Java/Others) Memory Limit: 65536/32768 K (Java/Others) ...
到浏览器顶部的获取js和jquery
获取当前窗口到页面顶端高度: js: document.documentElement.scrollTop JQ:$(document).scrollTop()或者$(window).scrollTo ...
深入分析HashMap
本文基于jdk1.8 HashMap特点: HashMap具体方法分析: put方法分析: 执行流程图: public V put(K key, V value) { return putVal(ha ...
CSS预处理器之less
less简单入门 w3cplus--Less讲解 vue中安装less npm install less less-loader --save 注意:在vue中引入less之后,用"> ...
JQuery弹出层，点击按钮后弹出遮罩层，有关闭按钮【转】
<!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <t ...

通过全备+主从同步恢复被drop的库或表

MySQL 中drop 等高危误操作后恢复方法

通过全备+主从同步恢复被drop的库或表的更多相关文章

随机推荐

热门专题