經過全備+relaylog同步恢復被drop的庫或表
MySQL 中drop 等高危誤操做後恢復方法
實驗目的:html
- 本次實驗以恢復drop操做爲例,使用不一樣方法進行誤操做的數據恢復.
方法:mysql
- 利用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)
- 臨時slave:db211(192.168.99.211)
- 壓力:在作本次實驗過程用,使用sysbench同時作讀寫模擬壓力(28thread+10*100000行)
2.本實驗的前置條件:sql
- 在drop前至少有一次全量備份
- 從全備到drop操做時間點有全程binlog,而且binlog format='row'
若是沒有以上兩個備份怎麼辦?見《無備份的誤操做恢復方法》
3.模擬誤操做bash
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文件到空閒服務器:db212上
- 以全備恢復到一個臨時新實例.
5.找到誤操做的位置(GTID或binlog pos)session
經過查找懷疑的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
方法三:利用binlog直接更名爲realy-log直接回放SQL到指定點：code
- 恢復全備到臨時實例中(略),並在關閉狀態下。
root@localhost [(none)]>shutdown; Query OK, 0 rows affected (0.00 sec) [1]- Done /usr/local/mysql57/bin/mysqld --defaults-file=/data/57mysql/mysql3506/my3506.cnf [root@db211_16:40:49 /data/57mysql/mysql3506/logs]
- 複製備份binlog文件,將文件重命名爲relay-bin.0000*格式,並製做relay-bin.index
#cd data/ [root@db211_16:40:58 /data/57mysql/mysql3506/data] #ll total 409652 -rw-r----- 1 mysql mysql 56 Aug 1 16:36 auto.cnf -rw-r----- 1 mysql mysql 8585 Aug 1 16:40 error.log -rw-r----- 1 mysql mysql 364 Aug 1 16:40 ib_buffer_pool -rw-r----- 1 mysql mysql 104857600 Aug 1 16:40 ibdata1 -rw-r----- 1 mysql mysql 104857600 Aug 1 16:40 ib_logfile0 -rw-r----- 1 mysql mysql 104857600 Aug 1 16:36 ib_logfile1 -rw-r----- 1 mysql mysql 104857600 Aug 1 16:36 ib_logfile2 drwxr-x--- 2 mysql mysql 4096 Aug 1 16:36 mysql drwxr-x--- 2 mysql mysql 8192 Aug 1 16:36 performance_schema -rw-r----- 1 mysql mysql 380 Aug 1 16:38 slow.log drwxr-x--- 2 mysql mysql 8192 Aug 1 16:36 sys [root@db211_16:40:59 /data/57mysql/mysql3506/data] #cp /data/backup/3506binlogs/* . [root@db211_16:41:30 /data/57mysql/mysql3506/data] #rename mysql-bin relay-bin mysql-bin.0000* //重命名成relay-bin.0000* [root@db211_16:45:50 /data/57mysql/mysql3506/data] #ll total 3283784 -rw-r----- 1 mysql mysql 56 Aug 1 16:36 auto.cnf -rw-r----- 1 mysql mysql 8585 Aug 1 16:40 error.log -rw-r----- 1 mysql mysql 364 Aug 1 16:40 ib_buffer_pool -rw-r----- 1 mysql mysql 104857600 Aug 1 16:40 ibdata1 -rw-r----- 1 mysql mysql 104857600 Aug 1 16:40 ib_logfile0 -rw-r----- 1 mysql mysql 104857600 Aug 1 16:36 ib_logfile1 -rw-r----- 1 mysql mysql 104857600 Aug 1 16:36 ib_logfile2 drwxr-x--- 2 mysql mysql 4096 Aug 1 16:36 mysql drwxr-x--- 2 mysql mysql 8192 Aug 1 16:36 performance_schema -rw-r----- 1 root root 268435555 Aug 1 16:41 relay-bin.000010 -rw-r----- 1 root root 268442595 Aug 1 16:41 relay-bin.000011 -rw-r----- 1 root root 268442419 Aug 1 16:41 relay-bin.000012 -rw-r----- 1 root root 268437857 Aug 1 16:41 relay-bin.000013 -rw-r----- 1 root root 268438414 Aug 1 16:41 relay-bin.000014 -rw-r----- 1 root root 268437131 Aug 1 16:41 relay-bin.000015 -rw-r----- 1 root root 268436889 Aug 1 16:41 relay-bin.000016 -rw-r----- 1 root root 268437011 Aug 1 16:41 relay-bin.000017 -rw-r----- 1 root root 268441823 Aug 1 16:41 relay-bin.000018 -rw-r----- 1 root root 268439288 Aug 1 16:41 relay-bin.000019 -rw-r----- 1 root root 258700685 Aug 1 16:41 relay-bin.000020 -rw-r----- 1 mysql mysql 380 Aug 1 16:38 slow.log drwxr-x--- 2 mysql mysql 8192 Aug 1 16:36 sys [root@db211_16:45:52 /data/57mysql/mysql3506/data] #ls ./relay-bin.0000*>relay-bin.index //create relay-bin.index [root@db211_16:46:24 /data/57mysql/mysql3506/data] #cat relay-bin.index ./relay-bin.000010 ./relay-bin.000011 ./relay-bin.000012 ./relay-bin.000013 ./relay-bin.000014 ./relay-bin.000015 ./relay-bin.000016 ./relay-bin.000017 ./relay-bin.000018 ./relay-bin.000019 ./relay-bin.000020 [root@db211_16:46:31 /data/57mysql/mysql3506/data] #chown mysql:mysql relay-bin.* //修改relay-bin權限爲mysql:mysql [root@db211_16:47:10 /data/57mysql/mysql3506/data] #ll total 3283788 -rw-r----- 1 mysql mysql 56 Aug 1 16:36 auto.cnf -rw-r----- 1 mysql mysql 8585 Aug 1 16:40 error.log -rw-r----- 1 mysql mysql 364 Aug 1 16:40 ib_buffer_pool -rw-r----- 1 mysql mysql 104857600 Aug 1 16:40 ibdata1 -rw-r----- 1 mysql mysql 104857600 Aug 1 16:40 ib_logfile0 -rw-r----- 1 mysql mysql 104857600 Aug 1 16:36 ib_logfile1 -rw-r----- 1 mysql mysql 104857600 Aug 1 16:36 ib_logfile2 drwxr-x--- 2 mysql mysql 4096 Aug 1 16:36 mysql drwxr-x--- 2 mysql mysql 8192 Aug 1 16:36 performance_schema -rw-r----- 1 mysql mysql 268435555 Aug 1 16:41 relay-bin.000010 -rw-r----- 1 mysql mysql 268442595 Aug 1 16:41 relay-bin.000011 -rw-r----- 1 mysql mysql 268442419 Aug 1 16:41 relay-bin.000012 -rw-r----- 1 mysql mysql 268437857 Aug 1 16:41 relay-bin.000013 -rw-r----- 1 mysql mysql 268438414 Aug 1 16:41 relay-bin.000014 -rw-r----- 1 mysql mysql 268437131 Aug 1 16:41 relay-bin.000015 -rw-r----- 1 mysql mysql 268436889 Aug 1 16:41 relay-bin.000016 -rw-r----- 1 mysql mysql 268437011 Aug 1 16:41 relay-bin.000017 -rw-r----- 1 mysql mysql 268441823 Aug 1 16:41 relay-bin.000018 -rw-r----- 1 mysql mysql 268439288 Aug 1 16:41 relay-bin.000019 -rw-r----- 1 mysql mysql 258700685 Aug 1 16:41 relay-bin.000020 -rw-r--r-- 1 mysql mysql 209 Aug 1 16:46 relay-bin.index -rw-r----- 1 mysql mysql 380 Aug 1 16:38 slow.log drwxr-x--- 2 mysql mysql 8192 Aug 1 16:36 sys [root@db211_16:47:13 /data/57mysql/mysql3506/data]
若是relay-bin的目錄中有relay-log.info文件,必定得刪掉該文件.orm
啓動mysqld 設置相關參數server
[root@db210_00:29:29 /data/57mysql/mysql3507/logs] #/usr/local/mysql57/bin/mysqld --defaults-file=/data/57mysql/mysql3507/my3506.cnf& [2] 19942 [root@db210_00:29:35 /data/57mysql/mysql3507/logs] #mysql -S /tmp/mysql3507.sock -pxxxx mysql: [Warning] Using a password on the command line interface can be insecure. Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 Server version: 5.7.23-log MySQL Community Server (GPL) Copyright (c) 2000, 2018, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. root@localhost [(none)]>reset master; root@localhost [(none)]>change master to relay_log_file='relay-bin.000014',relay_log_pos=251246776,master_host='xxx'; root@localhost [(none)]>start slave sql_thread until sql_before_gtids='9e912d2b-92f6-11e8-9747-0050568be82c:9791090';
- 等待sql_thread 停在9791089時就能夠查看恢復數據了.
root@localhost [(none)]>show slave status\G;
*************************** 1. row ***************************
Slave_IO_State:
Master_Host: xxx
Master_User:
Master_Port: 3306
Connect_Retry: 60
Master_Log_File:
Read_Master_Log_Pos: 4
Relay_Log_File: relay-bin.000020
Relay_Log_Pos: 97871478
Relay_Master_Log_File: mysql-bin.000020
Slave_IO_Running: No
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: 258700839
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: 0
Master_UUID:
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:
Executed_Gtid_Set: 9e912d2b-92f6-11e8-9747-0050568be82c:1-9791089
Auto_Position: 0
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)]>select count(*) from wenyz.t2;
+----------+
| count(*) |
+----------+
| 163818 |
+----------+
1 row in set (0.11 sec)
root@localhost [(none)]>
- 至此數據已經回來了.導入master的工做就不在重複,參照方法一中.
相關文章
- 1. 經過全備+主從同步恢復被drop的庫或表
- 2. 經過全備+binlog_server同步恢復被drop的庫或表
- 3. mysql數據誤刪除的恢復，drop表或庫的恢復
- 4. MySQL異常恢復-drop表恢復
- 5. oracle drop 表後 恢復
- 6. ApexSQL Recover 恢復一個被drop的表的數據
- 7. 沒有備份怎麼恢復被drop的表(利用undrop-for-innodb)
- 8. 如何恢復DROP的存儲過程
- 9. 使用DBRECOVER FOR MYSQL恢復被drop的MySQL數據庫
- 10. MySQL relaylog + SQL_Thread 增量恢復binlog
- 更多相關文章...
- • MySQL數據庫恢復（LOAD DATA） - MySQL教程
- • MySQL刪除存儲過程（DROP PROCEDURE） - MySQL教程
- • Tomcat學習筆記（史上最全tomcat學習筆記）
- • 爲了進字節跳動，我精選了29道Java經典算法題，帶詳細講解
相關標籤/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
歡迎關注本站公眾號,獲取更多信息
相關文章
- 1. 經過全備+主從同步恢復被drop的庫或表
- 2. 經過全備+binlog_server同步恢復被drop的庫或表
- 3. mysql數據誤刪除的恢復，drop表或庫的恢復
- 4. MySQL異常恢復-drop表恢復
- 5. oracle drop 表後 恢復
- 6. ApexSQL Recover 恢復一個被drop的表的數據
- 7. 沒有備份怎麼恢復被drop的表(利用undrop-for-innodb)
- 8. 如何恢復DROP的存儲過程
- 9. 使用DBRECOVER FOR MYSQL恢復被drop的MySQL數據庫
- 10. MySQL relaylog + SQL_Thread 增量恢復binlog