MySQL数据库恢复(使用mysqlbinlog命令)
网络编程 2021-07-05 15:27www.168986.cn编程入门
binlog是通过记录二进制文件方式来备份数据，然后在从二进制文件将数据恢复到某一时段或某一操作点。
1开启binlog日志记录
修改mysql配置文件mysql.ini，在[mysqld]节点下添加
# log-bin
log-bin = E:/log/logbin.log
路径中不要包含中文和空格。重启mysql服务。通过命令行停止和启动mysql服务
c:\> s mysql;
c:\> 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 --s-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" --s-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-munity-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.automit=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-munity-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.automit=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 --s-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" --s-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"
修改mysql配置文件mysql.ini，在[mysqld]节点下添加
代码如下:
# log-bin
log-bin = E:/log/logbin.log
路径中不要包含中文和空格。重启mysql服务。通过命令行停止和启动mysql服务
代码如下:
c:\> s mysql;
c:\> 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 --s-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" --s-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-munity-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.automit=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-munity-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.automit=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 --s-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" --s-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"
编程语言
- 宿迁百度关键词排名指南：实现精准营销的关键
- 四川SEO优化怎么做网络推广
- 立昂技术备案老域名收购：如何为您的业务赋能
- 安徽百度关键词seo贵不贵，一般需要多少钱
- 吉林百度快照排名怎么做电话营销
- 多伦新手做SEO怎么做
- 甘肃优化关键词排名推广怎么做论坛营销
- 沙雅SEO网站推广：提升您的在线可见性
- 四川SEO优化如何提升销售额和销售量
- 聂荣网站排名优化：提升网站可见性的全方位指
- 涞水SEO：提升地方企业在线可见性的策略
- 辽宁百度seo排名怎样做网站排名
- 临湘哪有关键词排名优化：提升网站可见度的关
- 黑龙江百度网站优化有没有优惠
- 凉城优化关键词排名推广：提升您的网络可见性
- 萝北整站优化：提升您网站流量和排名的全面指