binlog它是通过记录二进制文件来备份数据，然后将数据从二进制文件恢复到一定的时间或操作点。
1：开启binlog日志记录
修改mysql配置文件mysql.ini，在[mysqld]节点下添加
#log-bin
log-bin=E:/log/logbin.log
不包括中文和空格。mysql服务。停止并启动命令行mysql服务
c:\>netstopmysql;
c:\>netstartmysql;
进入命令行mysql检查二进制日志是否已经启动
Sql代码
mysql>showvariableslike'log_%';
日志成功开启后，会E:/log创建/目录logbin.index和logbin.000001两个文件。logbin.00001是数据库的备份文件，以后可以通过这个文件恢复数据库。
2.查看备份二进制文件
Sql代码
c:\mysql\bin\>mysqlbinloge:/log/logbin.000001
以后记录的操作多了，命令行的方式基本没用。您可以使用导出日志文件来查看日志内容
2.1 导出
Xml代码
c:\mysql\bin\>mysqlbinloge:/log/logbin.000001>e:/log/log.txt
">": 导入文件； ">>": 添加到文件中
若有多个日志文件
Sql代码
c:\mysql\bin\>mysqlbinloge:/log/logbin.000001>e:/log/log.sql
c:\mysql\bin\>mysqlbinloge:/log/logbin.000002>>e:/log/log.sq
2.2 按指定位置导出：
Sql代码
c:\mysql\bin\>mysqlbinlog--start-position=185--stop-position=338e:/log/logbin.000001>e:/log/log3.txt
2.3 按指定时间导出：
Xml代码
c:\mysql\bin\>mysqlbinlog--start-datetime="2010-01-0711:25:56"--stop-datetime="2010-01-0713:23:50"e:/log/logbin.000001>e:/log/log_by_date22.txt
3：从备份恢复数据库
日志的内容如下：
Sql代码
/*!40019SET@@session.max_insert_delayed_threads=0*/;
/*!50003SET@OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER/*!*/;
#at4
#11010713:23:50serverid1end_log_pos106Start:binlogv4,serverv5.1.53-community-logcreated11010713:23:50atstartup
#Warning:thisbinlogiseitherinuseorwasnotclosedproperly.
ROLLBACK/*!*/;
BINLOG'
ZqMmTQ8BAAAAZgAAAGoAAAABAAQANS4xLjUzLWNvbW11bml0eS1sb2cAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAABmoyZNEzgNAAgAEgAEBAQEEgAAUwAEGggAAAAICAgC
'/*!*/;
#at106
#11010713:26:58serverid1end_log_pos185Querythread_id=44exec_time=1error_code=0
SETTIMESTAMP=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/*!*/;
/*!\Cutf8*//*!*/;
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
/*!*/;
#at185
#11010713:26:58serverid1end_log_pos338Querythread_id=44exec_time=1error_code=0
usencl-interactive/*!*/;
SETTIMESTAMP=1294378018/*!*/;
UPDATE`t_system_id`SET`id_value`='3000'WHERE(`table_name`='t_working_day')
/*!*/;
#at338
#11010713:26:58serverid1end_log_pos365Xid=8016
COMMIT/*!*/;
DELIMITER;
DELIMITER/*!*/;
DELIMITER;
#Endoflogfile
ROLLBACK/*addedbymysqlbinlog*/;
/*!50003SETCOMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
/*!40019SET@@session.max_insert_delayed_threads=0*/;
/*!50003SET@OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER/*!*/;
#at4
#11010713:23:50serverid1end_log_pos106Start:binlogv4,serverv5.1.53-community-logcreated11010713:23:50atstartup
#Warning:thisbinlogiseitherinuseorwasnotclosedpropery.
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"