詳解MySQL誤操作后怎樣進(jìn)行數(shù)據(jù)恢復(fù)
一、開啟binlog。
首先查看binlog是否開啟
mysql> show variables like "log_bin"; +---------------+-------+ |Variable_name | Value +---------------+-------+ | log_bin OFF +---------------+-------+ 1 row in set (0.00 sec)
值為OFF,需開啟,開啟binlog方式如下:
#vim /etc/my.cnf
在[mysqld]中加入
log-bin = mysql-bin log-bin = /usr/local/mysql/log/mysql-bin.log
重啟mysql服務(wù)
#service mysqld stop #service mysqld start
二、模擬數(shù)據(jù)寫入
建庫(kù)
create database backup;
建表
CREATE TABLE `number` ( `id` int(11) NOT NULL AUTO_INCREMENT COMMENT '編號(hào)', `updatetime` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
寫入數(shù)據(jù)
程序2-1
#coding:utf8
#python2.7
import MySQLdb
import time
def connect_mysql(db_host="192.168.11.169",user="martin",passwd="martin",db="backup",charset="utf8"):
conn = MySQLdb.connect(host=db_host,user=user,passwd=passwd,db=db,charset=charset)
conn.autocommit(True)
return conn.cursor()
#數(shù)據(jù)插入
for i in range(0,10):
#time=time.strftime("%Y-%m-%d %H:%M:%S")
sql = 'insert into number(updatetime) values(%s)'
values = [(time.strftime("%Y-%m-%d %H:%M:%S"))]
db1 = connect_mysql()
print db1.executemany(sql,values)
查詢數(shù)據(jù)
mysql> select * from number; +-------+------------------------+ | id | updatetime +--------------------------------+ | 1 | 2016-06-29 23:27:15 | | 2 | 2016-06-29 23:27:15 | | 3 | 2016-06-29 23:27:15 | | 4 | 2016-06-29 23:27:15 | | 5 | 2016-06-29 23:27:15 | | 6 | 2016-06-29 23:27:15 | | 7 | 2016-06-29 23:27:15 | | 8 | 2016-06-29 23:27:15 | | 9 | 2016-06-29 23:27:15 | | 10 | 2016-06-29 23:27:15 | +-------+------------------------+ 10 rows in set (0.00 sec)
三、全量備份
mysqldump -uroot -p -F --master-data=2 backup |gzip> /martin/data/backup_$(date +%F).sql.gz
注:加-F能刷新binlog,方便恢復(fù)時(shí)操作。
四、模擬寫入增量數(shù)據(jù)
繼續(xù)執(zhí)行程序2-1。
查詢數(shù)據(jù)
mysql> select * from number; +----+---------------------------+ | id | updatetime | +----+---------------------------+ | 1 | 2016-06-29 23:27:15 | | 2 | 2016-06-29 23:27:15 | | 3 | 2016-06-29 23:27:15 | | 4 | 2016-06-29 23:27:15 | | 5 | 2016-06-29 23:27:15 | | 6 | 2016-06-29 23:27:15 | | 7 | 2016-06-29 23:27:15 | | 8 | 2016-06-29 23:27:15 | | 9 | 2016-06-29 23:27:15 | | 10 | 2016-06-29 23:27:15 | | 11 | 2016-06-29 23:31:03 | | 12 | 2016-06-29 23:31:03 | | 13 | 2016-06-29 23:31:03 | | 14 | 2016-06-29 23:31:03 | | 15 | 2016-06-29 23:31:03 | | 16 | 2016-06-29 23:31:03 | | 17 | 2016-06-29 23:31:03 | | 18 | 2016-06-29 23:31:03 | | 19 | 2016-06-29 23:31:03 | | 20 | 2016-06-29 23:31:03 | +-------+---------------------+ 20 rows in set (0.00 sec)
五、增量備份
保留mysql-bin.000002及之后的binlog即可。
六、模擬誤操作
delete from number;
七、再次寫入增量數(shù)據(jù)
執(zhí)行程序2-1
select * from bumber;
+------+------------------------+ | id | updatetime | +------+------------------------+ | 21 | 2016-06-29 23:41:06 | | 22 | 2016-06-29 23:41:06 | | 23 | 2016-06-29 23:41:06 | | 24 | 2016-06-29 23:41:06 | | 25 | 2016-06-29 23:41:06 | | 26 | 2016-06-29 23:41:06 | | 27 | 2016-06-29 23:41:06 | | 28 | 2016-06-29 23:41:06 | | 29 | 2016-06-29 23:41:06 | | 30 | 2016-06-29 23:41:06 | +------+------------------------+ 10 rows in set (0.00 sec)
八、恢復(fù)
此時(shí)發(fā)現(xiàn)之前的delete操作為誤操作,急需恢復(fù),恢復(fù)過程如下
給該表加上讀鎖
lock table number read;
將全量備份的數(shù)據(jù)導(dǎo)入
#cd /martin/data/ #gzip -d number_2016-06-29.sql.gz #grep -i "change" *.sql -- CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000002', MASTER_LOG_POS=107;
刷新日志
#mysqladmin -uroot -p'martin' flush-logs #cd /usr/local/mysql/log #ls|grep mysql-bin|grep -v index mysql-bin.000001 mysql-bin.000002 mysql-bin.000003
可確定mysql-bin.000002為增量數(shù)據(jù)binlog
導(dǎo)入全量備份
#cd /martin/data/ #mysql -uroot -p backup < number_2016-06-29.sql #cp /usr/local/mysql/log/mysql-bin.000002 /martin/data/ #mysqlbinlog mysql-bin.000002 >bin.sql #vim bin.sql
在bin.sql找到之前的delete語(yǔ)句,刪除
mysql -uroot -p <bin.sql
九、確認(rèn)已恢復(fù)數(shù)據(jù)
登錄mysql
#mysql -uroot -p'martin' backup select * from number;
+----+---------------------+ | id | updatetime | +----+---------------------+ | 1 | 2016-06-29 23:27:15 | | 2 | 2016-06-29 23:27:15 | | 3 | 2016-06-29 23:27:15 | | 4 | 2016-06-29 23:27:15 | | 5 | 2016-06-29 23:27:15 | | 6 | 2016-06-29 23:27:15 | | 7 | 2016-06-29 23:27:15 | | 8 | 2016-06-29 23:27:15 | | 9 | 2016-06-29 23:27:15 | | 10 | 2016-06-29 23:27:15 | | 11 | 2016-06-29 23:31:03 | | 12 | 2016-06-29 23:31:03 | | 13 | 2016-06-29 23:31:03 | | 14 | 2016-06-29 23:31:03 | | 15 | 2016-06-29 23:31:03 | | 16 | 2016-06-29 23:31:03 | | 17 | 2016-06-29 23:31:03 | | 18 | 2016-06-29 23:31:03 | | 19 | 2016-06-29 23:31:03 | | 20 | 2016-06-29 23:31:03 | | 21 | 2016-06-29 23:41:06 | | 22 | 2016-06-29 23:41:06 | | 23 | 2016-06-29 23:41:06 | | 24 | 2016-06-29 23:41:06 | | 25 | 2016-06-29 23:41:06 | | 26 | 2016-06-29 23:41:06 | | 27 | 2016-06-29 23:41:06 | | 28 | 2016-06-29 23:41:06 | | 29 | 2016-06-29 23:41:06 | | 30 | 2016-06-29 23:41:06 | +----+---------------------+ 30 rows in set (0.00 sec)
恢復(fù)完成!以上就是本文的全部?jī)?nèi)容,在操作數(shù)據(jù)庫(kù)時(shí)候要多加小心盡量避免誤操作,如果萬(wàn)一遇到了,希望本文能夠幫助大家。
相關(guān)文章
MySQL中查詢?nèi)罩九c慢查詢?nèi)罩镜幕緦W(xué)習(xí)教程
這篇文章主要介紹了MySQL中查詢?nèi)罩九c慢查詢?nèi)罩镜幕緦W(xué)習(xí)教程,文中還提到了MySQL自帶的Mysqldumpslow日志分析工具的使用,需要的朋友可以參考下2015-12-12
QT連接Mysql數(shù)據(jù)庫(kù)的詳細(xì)教程(親測(cè)成功版)
被Qt連接數(shù)據(jù)庫(kù)折磨了三天之后終于連接成功了,記錄一下希望對(duì)看到的人有所幫助,下面這篇文章主要給大家介紹了關(guān)于QT連接Mysql數(shù)據(jù)庫(kù)的詳細(xì)教程,文中通過圖文介紹的非常詳細(xì),需要的朋友可以參考下2023-05-05
允許遠(yuǎn)程訪問MySQL的實(shí)現(xiàn)方式
這篇文章主要介紹了允許遠(yuǎn)程訪問MySQL的實(shí)現(xiàn)方式,具有很好的參考價(jià)值,希望對(duì)大家有所幫助,如有錯(cuò)誤或未考慮完全的地方,望不吝賜教2024-01-01
mac 裝5.6版本mysql 設(shè)置密碼的簡(jiǎn)易方法
這篇文章主要介紹了mac 裝5.6版本mysql 設(shè)置密碼的簡(jiǎn)易方法,非常不錯(cuò),具有參考借鑒價(jià)值,需要的朋友可以參考下2018-05-05
MYSQL數(shù)字函數(shù)詳解及實(shí)戰(zhàn)記錄(數(shù)字函數(shù)大全,內(nèi)含示例)
數(shù)學(xué)運(yùn)算函數(shù)可以實(shí)現(xiàn)常見的數(shù)學(xué)運(yùn)算,這篇文章主要給大家介紹了關(guān)于MYSQL數(shù)字函數(shù)詳解及實(shí)戰(zhàn)的相關(guān)資料,文中通過代碼介紹的非常詳細(xì),需要的朋友可以參考下2024-01-01
mysql數(shù)據(jù)庫(kù)row_number函數(shù)舉例介紹
在MySQL中ROW_NUMBER()是一種用來(lái)生成行號(hào)的功能函數(shù),通常情況下它用于對(duì)查詢結(jié)果進(jìn)行編號(hào),以便方便地查看每行的位置,下面這篇文章主要給大家介紹了關(guān)于mysql數(shù)據(jù)庫(kù)row_number函數(shù)舉例介紹的相關(guān)資料,需要的朋友可以參考下2024-02-02

