當前位置：首頁 > 运维知识 > 数据库 >内容正文

数据库

MySQL数据库恢复(使用mysqlbinlog命令)

發布時間：2025/3/15 数据库 12 豆豆

生活随笔收集整理的這篇文章主要介紹了 MySQL数据库恢复(使用mysqlbinlog命令) 小編覺得挺不錯的,現在分享給大家,幫大家做個參考.

1：開啟binlog日志記錄?
修改mysql配置文件mysql.ini，在[mysqld]節點下添加?

復制代碼代碼如下:
# log-bin?
log-bin = E:/log/logbin.log?

路徑中不要包含中文和空格。重啟mysql服務。通過命令行停止和啟動mysql服務?

復制代碼代碼如下:
c:\>net stop mysql;?
c:\>net start mysql;?

進入命令行進入mysql并查看二進制日志是否已經啟動?
Sql代碼?

復制代碼代碼如下:
mysql>show variables like 'log_%';?

日志成功開啟后，會在E:/log/目錄下創建logbin.index和logbin.000001兩個文件。logbin.000001就是數據庫的備份文件，以后就可以通過此文件對數據庫進行恢復操作。?

2：查看備份的二進制文件?
Sql代碼?

復制代碼代碼如下:
c:\mysql\bin\>mysqlbinlog e:/log/logbin.000001?

日后記錄的操作多了，命令行方式基本就用不上了。可以使用將日志導出文件的方式來查看日志內容?
2.1 導出?
Xml代碼?

復制代碼代碼如下:
c:\mysql\bin\>mysqlbinlog e:/log/logbin.000001 > e:/log/log.txt?

">": 導入到文件中; ">>": 追加到文件中?
如果有多個日志文件?
Sql代碼?

復制代碼代碼如下:
c:\mysql\bin\> mysqlbinlog e:/log/logbin.000001 > e:/log/log.sql?
c:\mysql\bin\> mysqlbinlog e:/log/logbin.000002 >> e:/log/log.sq?

2.2 按指定位置導出：?
Sql代碼?

復制代碼代碼如下:
c:\mysql\bin\>mysqlbinlog --start-position=185 --stop-position=338 e:/log/logbin.000001 > e:/log/log3.txt?

2.3 按指定時間導出：?
Xml代碼?

復制代碼代碼如下:
c:\mysql\bin\>mysqlbinlog --start-datetime="2010-01-07 11:25:56" --stop-datetime="2010-01-07 13:23:50" e:/log/logbin.000001 > e:/log/log_by_date22.txt?

3：從備份恢復數據庫?
做了一次更新操作，之后日志的內容如下：?
Sql代碼?

復制代碼代碼如下:
/*!40019 SET @@session.max_insert_delayed_threads=0*/;?
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;?
DELIMITER /*!*/;?
# at 4?
#110107 13:23:50 server id 1 end_log_pos 106 Start: binlog v 4, server v 5.1.53-community-log created 110107 13:23:50 at startup?
# Warning: this binlog is either in use or was not closed properly.?
ROLLBACK/*!*/;?
BINLOG '?
ZqMmTQ8BAAAAZgAAAGoAAAABAAQANS4xLjUzLWNvbW11bml0eS1sb2cAAAAAAAAAAAAAAAAAAAAA?
AAAAAAAAAAAAAAAAAABmoyZNEzgNAAgAEgAEBAQEEgAAUwAEGggAAAAICAgC?
'/*!*/;?
# at 106?
#110107 13:26:58 server id 1 end_log_pos 185 Query thread_id=44 exec_time=1 error_code=0?
SET TIMESTAMP=1294378018/*!*/;?
SET @@session.pseudo_thread_id=44/*!*/;?
SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=1, @@session.unique_checks=1, @@session.autocommit=1/*!*/;?
SET @@session.sql_mode=1344274432/*!*/;?
SET @@session.auto_increment_increment=1, @@session.auto_increment_offset=1/*!*/;?
/*!\C utf8 *//*!*/;?
SET @@session.character_set_client=33,@@session.collation_connection=33,@@session.collation_server=33/*!*/;?
SET @@session.lc_time_names=0/*!*/;?
SET @@session.collation_database=DEFAULT/*!*/;?
BEGIN?
/*!*/;?
# at 185?
#110107 13:26:58 server id 1 end_log_pos 338 Query thread_id=44 exec_time=1 error_code=0?
use ncl-interactive/*!*/;?
SET TIMESTAMP=1294378018/*!*/;?
UPDATE `t_system_id` SET `id_value`='3000' WHERE (`table_name`='t_working_day')?
/*!*/;?
# at 338?
#110107 13:26:58 server id 1 end_log_pos 365 Xid = 8016?
COMMIT/*!*/;?
DELIMITER ;?
DELIMITER /*!*/;?
DELIMITER ;?
# End of log file?
ROLLBACK /* added by mysqlbinlog */;?
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;?
/*!40019 SET @@session.max_insert_delayed_threads=0*/;?
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;?
DELIMITER /*!*/;?
# at 4?
#110107 13:23:50 server id 1 end_log_pos 106 Start: binlog v 4, server v 5.1.53-community-log created 110107 13:23:50 at startup?
# Warning: this binlog is either in use or was not closed properly.?
ROLLBACK/*!*/;?
BINLOG '?
ZqMmTQ8BAAAAZgAAAGoAAAABAAQANS4xLjUzLWNvbW11bml0eS1sb2cAAAAAAAAAAAAAAAAAAAAA?
AAAAAAAAAAAAAAAAAABmoyZNEzgNAAgAEgAEBAQEEgAAUwAEGggAAAAICAgC?
'/*!*/;?
# at 106?
#110107 13:26:58 server id 1 end_log_pos 185 Query thread_id=44 exec_time=1 error_code=0?
SET TIMESTAMP=1294378018/*!*/;?
SET @@session.pseudo_thread_id=44/*!*/;?
SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=1, @@session.unique_checks=1, @@session.autocommit=1/*!*/;?
SET @@session.sql_mode=1344274432/*!*/;?
SET @@session.auto_increment_increment=1, @@session.auto_increment_offset=1/*!*/;?
/*!\C utf8 *//*!*/;?
SET @@session.character_set_client=33,@@session.collation_connection=33,@@session.collation_server=33/*!*/;?
SET @@session.lc_time_names=0/*!*/;?
SET @@session.collation_database=DEFAULT/*!*/;?
BEGIN?
/*!*/;?
# at 185?
#110107 13:26:58 server id 1 end_log_pos 338 Query thread_id=44 exec_time=1 error_code=0?
use ncl-interactive/*!*/;?
SET TIMESTAMP=1294378018/*!*/;?
UPDATE `t_system_id` SET `id_value`='3000' WHERE (`table_name`='t_working_day')?
/*!*/;?
# at 338?
#110107 13:26:58 server id 1 end_log_pos 365 Xid = 8016?
COMMIT/*!*/;?
DELIMITER ;?
DELIMITER /*!*/;?
DELIMITER ;?
# End of log file?
ROLLBACK /* added by mysqlbinlog */;?
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;?

3.1 恢復：?
Sql代碼?

復制代碼代碼如下:
c:\mysql\bin\>mysqlbinlog e:/log/logbin.000001 | mysql -u root -p?

3.2 按指定位置恢復：?
Sql代碼?

復制代碼代碼如下:
c:\mysql\bin\>mysqlbinlog --start-position=185 --stop-position=338 e:/log/logbin.000001 | mysql -u root -p?

3.3 按指定時間恢復：?
Xml代碼?

復制代碼代碼如下:
c:\mysql\bin\>mysqlbinlog --start-datetime="2010-01-07 11:25:56" --stop-datetime="2010-01-07 13:23:50" e:/log/logbin.000001 | mysql -u root -p?

3.4 通過導出的腳本文件恢復?
Sql代碼?

復制代碼代碼如下:
c:\mysql\bin\>mysql -e "source e:/log/log.sql"?

4.其他常用操作?
4.1 查看所有日志文件?

Sql代碼?

復制代碼代碼如下:
mysql>show master logs;?

4.2 當前使用的binlog文件?
Sql代碼?

復制代碼代碼如下:
mysql>show binlog events \g;?

4.3 產生一個新的binlog日志文件?
Sql代碼?

復制代碼代碼如下:
mysql>flush logs;?

4.4 刪除所有二進制日志，并從新開始記錄（注意：reset master命令會刪除所有的二進制日志）?
Sql代碼?

復制代碼代碼如下:
mysql > flush logs;?
mysql > reset master;?

4.5 快速備份數據到sql文件?

Sql代碼?

復制代碼代碼如下:
c:\mysql\bin>mysqldump -u root -p --opt --quick interactive > e:/log/mysqldump.sql?

為了方便查看，把從腳本恢復的命令在寫一次?
Sql代碼?

復制代碼代碼如下:
c:\mysql\bin\>mysql -e "source e:/log/mysqldump.sql"?

轉載于:https://www.cnblogs.com/xiaoleiel/p/8316714.html

總結

以上是生活随笔為你收集整理的MySQL数据库恢复(使用mysqlbinlog命令)的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。

上一篇：保存图片验证码到redis数据库
下一篇： python_fullstack基础(十