MySQL 二进制文件恢复

先不说话先来一段代码块

 mysql> show variables like 'autocommit';

 +---------------+-------+

 | Variable_name | Value |

 +---------------+-------+

 | autocommit    | ON    |

 +---------------+-------+

 1 row in set (0.00 sec)

 mysql> set autocommit=0;

 Query OK, 0 rows affected (0.00 sec)

 mysql> show variables like 'autocommit';

 +---------------+-------+

 | Variable_name | Value |

 +---------------+-------+

 | autocommit    | OFF   |

 +---------------+-------+

 1 row in set (0.00 sec)

 mysql> show master status;

 +------------------+----------+--------------+------------------+-------------------+

 | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

 +------------------+----------+--------------+------------------+-------------------+

 | mysql-bin.000034 |      120 |              |                  |                   |

 +------------------+----------+--------------+------------------+-------------------+

 1 row in set (0.00 sec)

 #第二个

 mysql> create database luna;

 Query OK, 1 row affected (0.00 sec)

 mysql> show master status;

 +------------------+----------+--------------+------------------+-------------------+

 | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

 +------------------+----------+--------------+------------------+-------------------+

 | mysql-bin.000034 |      214 |              |                  |                   |

 +------------------+----------+--------------+------------------+-------------------+

 1 row in set (0.00 sec)

 mysql> use luna;

 Database changed

 mysql> create table t1(id int);

 Query OK, 0 rows affected (0.08 sec)

 mysql> show master status;

 +------------------+----------+--------------+------------------+-------------------+

 | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

 +------------------+----------+--------------+------------------+-------------------+

 | mysql-bin.000034 |      311 |              |                  |                   |

 +------------------+----------+--------------+------------------+-------------------+

 1 row in set (0.00 sec)

 mysql> insert into t1 values(1);

 Query OK, 1 row affected (0.00 sec)

 mysql> show master status;

 +------------------+----------+--------------+------------------+-------------------+

 | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

 +------------------+----------+--------------+------------------+-------------------+

 | mysql-bin.000034 |      311 |              |                  |                   |

 +------------------+----------+--------------+------------------+-------------------+

 1 row in set (0.00 sec)

 mysql> commit;

 Query OK, 0 rows affected (0.33 sec)

 mysql> show master status;

 +------------------+----------+--------------+------------------+-------------------+

 | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

 +------------------+----------+--------------+------------------+-------------------+

 | mysql-bin.000034 |      499 |              |                  |                   |

 +------------------+----------+--------------+------------------+-------------------+

 1 row in set (0.00 sec)

 #update

 mysql> update t1 set id=11 where id=1;

 Query OK, 1 row affected (0.00 sec)

 Rows matched: 1  Changed: 1  Warnings: 0

 mysql> show master status;

 +------------------+----------+--------------+------------------+-------------------+

 | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

 +------------------+----------+--------------+------------------+-------------------+

 | mysql-bin.000034 |      857 |              |                  |                   |

 +------------------+----------+--------------+------------------+-------------------+

 1 row in set (0.00 sec)

 mysql> show master status;

 +------------------+----------+--------------+------------------+-------------------+

 | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

 +------------------+----------+--------------+------------------+-------------------+

 | mysql-bin.000034 |     1051 |              |                  |                   |

 +------------------+----------+--------------+------------------+-------------------+

 1 row in set (0.00 sec)

 #delete

 mysql> delete from t1 where id=2;

 Query OK, 1 row affected (0.00 sec)

 mysql> show master status;

 +------------------+----------+--------------+------------------+-------------------+

 | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

 +------------------+----------+--------------+------------------+-------------------+

 | mysql-bin.000034 |     1051 |              |                  |                   |

 +------------------+----------+--------------+------------------+-------------------+

 1 row in set (0.00 sec)

 mysql> commit;

 Query OK, 0 rows affected (0.01 sec)

 mysql> show master status;

 +------------------+----------+--------------+------------------+-------------------+

 | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

 +------------------+----------+--------------+------------------+-------------------+

 | mysql-bin.000034 |     1239 |              |                  |                   |

 +------------------+----------+--------------+------------------+-------------------+

 1 row in set (0.00 sec)

 #drop

 mysql> select * from t1;

 +------+

 | id   |

 +------+

 |   11 |

 |    3 |

 |    4 |

 +------+

 3 rows in set (0.00 sec)

 mysql> update t1 set id=44 where id=4;

 Query OK, 1 row affected (0.00 sec)

 Rows matched: 1  Changed: 1  Warnings: 0

 mysql> drop table t1;

 Query OK, 0 rows affected (0.04 sec)

 mysql> drop database luna;

 Query OK, 0 rows affected (0.08 sec)

 mysql> show master status;

 +------------------+----------+--------------+------------------+-------------------+

 | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

 +------------------+----------+--------------+------------------+-------------------+

 | mysql-bin.000034 |     1633 |              |                  |                   |

 +------------------+----------+--------------+------------------+-------------------+

 1 row in set (0.00 sec)

 #工具查看

 mysql> show binlog events in 'mysql-bin.000034';

 #在命令行查看

 [root@db01-sa mysql]# mysqlbinlog --base64-output=decode-rows -vvv /data/mysql/mysql-bin.000034

 /*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=1*/;

 /*!40019 SET @@session.max_insert_delayed_threads=0*/;

 /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;

 DELIMITER /*!*/;

 # at 4

 #180627 17:49:07 server id 6  end_log_pos 120 CRC32 0x75f5723b     Start: binlog v 4, server v 5.6.38-log created 180627 17:49:07 at startup

 # Warning: this binlog is either in use or was not closed properly.

 ROLLBACK/*!*/;

 # at 120

 #180627 18:21:12 server id 6  end_log_pos 214 CRC32 0x0a1b14fc     Query    thread_id=2    exec_time=0    error_code=0

 SET TIMESTAMP=1530094872/*!*/;

 SET @@session.pseudo_thread_id=2/*!*/;

 SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=0, @@session.unique_checks=1, @@session.autocommit=1/*!*/;

 SET @@session.sql_mode=1075838976/*!*/;

 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/*!*/;

 create database luna

 /*!*/;

 # at 214

 #180627 18:22:16 server id 6  end_log_pos 311 CRC32 0x9fe876dc     Query    thread_id=2    exec_time=0    error_code=0

 use `luna`/*!*/;

 SET TIMESTAMP=1530094936/*!*/;

 create table t1(id int)

 /*!*/;

 # at 311

 #180627 18:23:02 server id 6  end_log_pos 383 CRC32 0xa66c8e7d     Query    thread_id=2    exec_time=0    error_code=0

 SET TIMESTAMP=1530094982/*!*/;

 BEGIN

 /*!*/;

 # at 383

 #180627 18:23:02 server id 6  end_log_pos 428 CRC32 0xf0097518     Table_map: `luna`.`t1` mapped to number 70

 # at 428

 #180627 18:23:02 server id 6  end_log_pos 468 CRC32 0x2b1aa647     Write_rows: table id 70 flags: STMT_END_F

 ### INSERT INTO `luna`.`t1`

 ### SET

 ###   @1=1 /* INT meta=0 nullable=1 is_null=0 */

 # at 468

 #180627 18:23:28 server id 6  end_log_pos 499 CRC32 0x62719421     Xid = 37

 COMMIT/*!*/;

 # at 499

 #180627 18:25:06 server id 6  end_log_pos 571 CRC32 0x84c9efe6     Query    thread_id=2    exec_time=0    error_code=0

 SET TIMESTAMP=1530095106/*!*/;

 BEGIN

 /*!*/;

 # at 571

 #180627 18:25:06 server id 6  end_log_pos 616 CRC32 0x74d151e2     Table_map: `luna`.`t1` mapped to number 70

 # at 616

 #180627 18:25:06 server id 6  end_log_pos 656 CRC32 0xd10d7120     Write_rows: table id 70 flags: STMT_END_F

 ### INSERT INTO `luna`.`t1`

 ### SET

 ###   @1=2 /* INT meta=0 nullable=1 is_null=0 */

 # at 656

 #180627 18:27:16 server id 6  end_log_pos 701 CRC32 0x7895e39d     Table_map: `luna`.`t1` mapped to number 70

 # at 701

 #180627 18:27:16 server id 6  end_log_pos 741 CRC32 0x5acc32fe     Write_rows: table id 70 flags: STMT_END_F

 ### INSERT INTO `luna`.`t1`

 ### SET

 ###   @1=3 /* INT meta=0 nullable=1 is_null=0 */

 # at 741

 #180627 18:27:30 server id 6  end_log_pos 786 CRC32 0xb4ed9f5a     Table_map: `luna`.`t1` mapped to number 70

 # at 786

 #180627 18:27:30 server id 6  end_log_pos 826 CRC32 0x819e8db3     Write_rows: table id 70 flags: STMT_END_F

 ### INSERT INTO `luna`.`t1`

 ### SET

 ###   @1=4 /* INT meta=0 nullable=1 is_null=0 */

 # at 826

 #180627 18:27:58 server id 6  end_log_pos 857 CRC32 0x452e1f31     Xid = 41

 COMMIT/*!*/;

 # at 857

 #180627 18:29:56 server id 6  end_log_pos 929 CRC32 0x5e68dff7     Query    thread_id=2    exec_time=0    error_code=0

 SET TIMESTAMP=1530095396/*!*/;

 BEGIN

 /*!*/;

 # at 929

 #180627 18:29:56 server id 6  end_log_pos 974 CRC32 0xf4e4e2bf     Table_map: `luna`.`t1` mapped to number 70

 # at 974

 #180627 18:29:56 server id 6  end_log_pos 1020 CRC32 0x2d809738     Update_rows: table id 70 flags: STMT_END_F

 ### UPDATE `luna`.`t1`

 ### WHERE

 ###   @1=1 /* INT meta=0 nullable=1 is_null=0 */

 ### SET

 ###   @1=11 /* INT meta=0 nullable=1 is_null=0 */

 # at 1020

 #180627 18:30:25 server id 6  end_log_pos 1051 CRC32 0x08029580     Xid = 52

 COMMIT/*!*/;

 # at 1051

 #180627 18:31:25 server id 6  end_log_pos 1123 CRC32 0xcf1b6980     Query    thread_id=2    exec_time=0  error_code=0

 SET TIMESTAMP=1530095485/*!*/;

 BEGIN

 /*!*/;

 # at 1123

 #180627 18:31:25 server id 6  end_log_pos 1168 CRC32 0x7729069b     Table_map: `luna`.`t1` mapped to number 70

 # at 1168

 #180627 18:31:25 server id 6  end_log_pos 1208 CRC32 0x04cb5496     Delete_rows: table id 70 flags: STMT_END_F

 ### DELETE FROM `luna`.`t1`

 ### WHERE

 ###   @1=2 /* INT meta=0 nullable=1 is_null=0 */

 # at 1208

 #180627 18:31:36 server id 6  end_log_pos 1239 CRC32 0x27093f44     Xid = 56

 COMMIT/*!*/;

 # at 1239

 #180627 18:33:45 server id 6  end_log_pos 1311 CRC32 0x8be80fc2     Query    thread_id=2    exec_time=0  error_code=0

 SET TIMESTAMP=1530095625/*!*/;

 BEGIN

 /*!*/;

 # at 1311

 #180627 18:33:45 server id 6  end_log_pos 1356 CRC32 0x77578bf1     Table_map: `luna`.`t1` mapped to number 70

 # at 1356

 #180627 18:33:45 server id 6  end_log_pos 1402 CRC32 0x9c7bf8df     Update_rows: table id 70 flags: STMT_END_F

 ### UPDATE `luna`.`t1`

 ### WHERE

 ###   @1=4 /* INT meta=0 nullable=1 is_null=0 */

 ### SET

 ###   @1=44 /* INT meta=0 nullable=1 is_null=0 */

 # at 1402

 #180627 18:34:17 server id 6  end_log_pos 1433 CRC32 0x354e0150     Xid = 60

 COMMIT/*!*/;

 # at 1433

 #180627 18:34:17 server id 6  end_log_pos 1548 CRC32 0x52b3dc50     Query    thread_id=2    exec_time=0  error_code=0

 SET TIMESTAMP=1530095657/*!*/;

 DROP TABLE `t1` /* generated by server */

 /*!*/;

 # at 1548

 #180627 18:34:26 server id 6  end_log_pos 1633 CRC32 0x2e40af97     Query    thread_id=2    exec_time=0  error_code=0

 SET TIMESTAMP=1530095666/*!*/;

 drop database luna

 /*!*/;

 DELIMITER ;

 # End of log file

 ROLLBACK /* added by mysqlbinlog */;

 /*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;

 /*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=0*/;

 #截取

 [root@db01-sa mysql]# mysqlbinlog --start-position=120 --stop-position=857 /data/mysql/mysql-bin.000034 >/tmp/luna2.sql

 WARNING: The range of printed events ends with a row event or a table map event that does not have the STMT_END_F flag

 set. This might be because the last statement was not fully written to the log, or because you are using a

 --stop-position or --stop-datetime that refers to an event in the middle of a statement. The event(s) from

 the partial statement have not been written to output.

 警告:打印事件的范围以行或表映射事件结束,没有设置了STMT_END_F标志。这可能是因为过去的声明没有完全写入日志,或者因为您使

 用的是——停止位置,stop-datetime指一个事件在一份声明中。部分语句中的事件尚未写入输出。

 #产生以上报错就是因为截取的时候 一定要注意begin  begin是一个语句的开始 一定要从begin之前开始截断

 之前的语句mysqlbinlog --start-position=120 --stop-position=974 /data/mysql/mysql-bin.000034 >/tmp/luna.sql 当中的974要改成857

  mysql> set sql_log_bin=0;

 Query OK, 0 rows affected (0.00 sec)

 mysql> source /tmp/luna.sql;

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected, 1 warning (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Charset changed

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 1 row affected (0.00 sec)

 Database changed

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.36 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.01 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.01 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.03 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.01 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 Query OK, 0 rows affected (0.00 sec)

 mysql> show database;

 ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'database' at line 1

 mysql> show databases;

 +--------------------+

 | Database           |

 +--------------------+

 | information_schema |

 | binlog             |

 | luna               |

 | mysql              |

 | nod01              |

 | oldboy             |

 | performance_schema |

 | test               |

 | world              |

 +--------------------+

 9 rows in set (0.00 sec)

 mysql> use luna

 Database changed

 mysql>

 mysql>

 mysql> show table;

 ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1

 mysql> show tables;

 +----------------+

 | Tables_in_luna |

 +----------------+

 | t1             |

 +----------------+

 1 row in set (0.00 sec)

 mysql> select * from t1;

 +------+

 | id   |

 +------+

 |    1 |

 |    2 |

 |    3 |

 |    4 |

 +------+

 4 rows in set (0.00 sec)

 mysql> show master status;

 +------------------+----------+--------------+------------------+-------------------+

 | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

 +------------------+----------+--------------+------------------+-------------------+

 | mysql-bin.000034 |     1633 |              |                  |                   |

 +------------------+----------+--------------+------------------+-------------------+

 1 row in set (0.00 sec)

MySQL binlog的补充

Mysql的binlog日志作用是用来记录mysql内部增删改查等对mysql数据库有更新的内容的记录（对数据库的改动），对数据库的查询select或show等不会被binlog日志记录;主要用于数据库的主从复制以及增量恢复。

mysql的binlog日志必须打开log-bin功能才能生存binlog日志

-rw-rw---- 1 mysql mysql 669 8月 10 21:29 mysql-bin.000001

-rw-rw---- 1 mysql mysql 126 8月 10 22:06 mysql-bin.000002

-rw-rw---- 1 mysql mysql 11799 8月 15 18:17 mysql-bin.000003

2、Mysqlbinlog解析工具

　　Mysqlbinlog功能是将Mysql的binlog日志转换成Mysql语句，默认情况下binlog日志是二进制文件，无法直接查看。

　　Mysqlbinlog参数

参数	描述
-d	指定库的binlog
-r	相当于重定向到指定文件
--start-position--stop-position	按照指定位置精确解析binlog日志（精确），如不接--stop-positiion则一直到binlog日志结尾
--start-datetime--stop-datetime	按照指定时间解析binlog日志（模糊，不准确），如不接--stop-datetime则一直到binlog日志结尾

备注：myslqlbinlog分库导出binlog，如使用-d参数，更新数据时必须使用use database。

例：解析ceshi数据库的binlog日志并写入my.sql文件

#mysqlbinlog -d ceshi mysql-bin.000003 -r my.sql

使用位置精确解析binlog日志

#mysqlbinlog mysql-bin.000003 --start-position=100 --stop-position=200 -r my.sql

3、MySQL binlog的三种工作模式

　　（1）Row level

　　日志中会记录每一行数据被修改的情况，然后在slave端对相同的数据进行修改。

　　优点：能清楚的记录每一行数据修改的细节

　　缺点：数据量太大

　　（2）Statement level（默认）

　　每一条被修改数据的sql都会记录到master的bin-log中，slave在复制的时候sql进程会解析成和原来master端执行过的相同的sql再次执行

　　优点：解决了 Row level下的缺点，不需要记录每一行的数据变化，减少bin-log日志量，节约磁盘IO，提高新能

　　缺点：容易出现主从复制不一致

　　（3）Mixed（混合模式）

　　结合了Row level和Statement level的优点

4、MySQL企业binlog模式的选择

互联网公司使用MySQL的功能较少（不用存储过程、触发器、函数），选择默认的Statement level
用到MySQL的特殊功能（存储过程、触发器、函数）则选择Mixed模式
用到MySQL的特殊功能（存储过程、触发器、函数），又希望数据最大化一直则选择Row模式

5、设置MySQL binlog模式

　　查看MySQLbinlog模式

mysql>show global variables like "binlog%";

+-----------------------------------------+-----------+

| Variable_name | Value |

+-----------------------------------------+-----------+

| binlog_cache_size | 1048576 |

| binlog_direct_non_transactional_updates | OFF |

| binlog_format | STATEMENT | #系统默认为STATEMENT模式

| binlog_stmt_cache_size | 32768 |

+-----------------------------------------+-----------+

4 rows in set (0.00 sec)　

MySQL中设置binlog模式

mysql>set global binlog_format='ROW';　

配置文件中设置binlog模式

#vim my.cnf

[mysqld]

binlog_format='ROW' #放在mysqld模块下面

user = mysql

port = 3306

socket = /data/3306/mysql.sock

6、配置完成后需要重启mysql服务

Row模式下解析binlog日志

#mysqlbinlog --base64-output="decode-rows" -v mysql-bin.000001

以上内容转自：https://www.cnblogs.com/xhyan/p/6530861.html

MySQL 二进制文件恢复的更多相关文章

MySQL 二进制文件恢复数据基础版本
先来一段自行体会 #---------------------------------------------------------------------------------- #模拟通过b ...
[svc]mysql备份恢复及常用命令
如何实现mysql读写分离 1.通过程序实现读写分类(性能效率最佳) php和java都可以通过设置多个连接文件轻松实现对db的读写分离,即当select时,就去连读库的连接文件,当update,i ...
MySql数据库恢复(*frm)文件
mysql数据库恢复(*frm)文件 WorkBench 在使用虚拟服务器时,服务器提供商一般不会像我们使用本地数据库一样:使用导入导出(这样的文件后缀是*.sql).大部分时候提供的是一个文件夹,里 ...
MySQL 备份恢复（导入导出）单个 innodb表
MySQL 备份恢复单个innodb表呢,对于这种恢复我们我们很多朋友都不怎么了解了,下面一起来看一篇关于MySQL 备份恢复单个innodb表的教程在实际环境中,时不时需要备份恢复单个或多个表(注 ...
Mysql备份恢复方案解析
1.全量备份和增量备份 1.1全量备份就是对现有的数据进行全部备份,之前做的备份均可舍弃,以最新的全备为基点. a.全备所有数据库 Innodb引擎: [root@leader mysql]#mys ...
基于Redo Log和Undo Log的MySQL崩溃恢复流程
在之前的文章「简单了解InnoDB底层原理」聊了一下MySQL的Buffer Pool.这里再简单提一嘴,Buffer Pool是MySQL内存结构中十分核心的一个组成,你可以先把它想象成一个黑盒子. ...
mysql二进制文件操作语法(mysql binary log operate statements)
开启 binary logs 功能在 mysql 配置文件中配置 log-bin,重启 mysql my.cnf (on Linux/unix) or my.ini (on Windows) 例子: ...
mysql binlog恢复
MySQL Binary Log也就是常说的bin-log, ,是mysql执行改动产生的二进制日志文件,其主要作用有两个: * 数据回复 * 主从数据库.用于slave端执行增删改,保持与maste ...
MySQL数据库恢复(使用mysqlbinlog命令)
binlog是通过记录二进制文件方式来备份数据,然后在从二进制文件将数据恢复到某一时段或某一操作点. 1:开启binlog日志记录修改mysql配置文件mysql.ini,在[mysqld]节点下添 ...

随机推荐

L1-002 打印沙漏
所谓“沙漏形状”,是指每行输出奇数个符号:各行符号中心对齐:相邻两行符号数差2:符号数先从大到小顺序递减到1,再从小到大顺序递增:首尾符号数相等. 给定任意N个符号,不一定能正好组成一个沙漏.要求打印 ...
用MyEclipse JPA创建项目（四）
MyEclipse 3.15 Style——在线购买低至75折!火爆开抢>> [MyEclipse最新版下载] 本教程介绍了MyEclipse中的一些基于PA的功能. 阅读本教程时,了解J ...
免费申请一年版Eset NOD32 Antivirus激活码（无限制）- 已失效
You will receive a 1-year license of the antivirus software Eset NOD32 (version 6), including all up ...
<转>字符编码
转: 字符编码笔记:ASCII,Unicode和UTF-8 作者: 阮一峰日期: 2007年10月28日今天中午,我突然想搞清楚Unicode和UTF-8之间的关系,于是就开始在网上查资料. ...
逆向路由器固件之解包 Part1
这个系列的文章以逆向路由器固件的方式来挖掘路由器中存在的漏洞. 本篇文章主要以介绍解包固件工具为主.文中演示用的固件可以在这里下载.由于针对设备的攻击越来越多,很多厂商把不提供固件下载作为一种安全策略 ...
NBUT 1220 SPY 2010辽宁省赛
Time limit 1000 ms Memory limit 131072 kB The National Intelligence Council of X Nation receives a ...
nib must contain exactly one top level object which must be a UICollectionReusableView instance
多了一个
利用Fierce2查询子域名
http://pnig0s1992.blog.51cto.com/393390/368428 安装方法引用Mickey的: 1.Mickey@pentestbox:/pentest/enumerati ...
smarty学习——高级知识
1.Objects 对象 smarty允许通过模板访问PHP对象.有两种方式来访问它们.一种是注册对象到模板,然后通过类似于用户自定义函数的形式来访问它. 另一种方法给模板分配对象,然后通过访问其它赋 ...
jenkins进阶-集成钉钉机器人(6)
最早做Jenkins发布完成以后通过邮件发送信息通知相关的联系人,发现邮件会受限于大家接收的设置,导致不能及时的看到相关的发布内容,公司使用钉钉做为公司内部的通讯工具,所以想通过Jenkins发布完成 ...

MySQL 二进制文件恢复

MySQL 二进制文件恢复的更多相关文章

随机推荐

热门专题