The “mysqlbinlog” command reads the binary logs and outputs them in SQL format. As a result, you can use it to create a database dump and then modify that file by hand. For example, let’s say that everything since April 10th, 10AM server time needs to be restored (leaving out one statement). We would first use this command:<\/p>\n
mysqlbinlog –start-datetime=”2013-04-10 10:0:00″ \/var\/log\/mysql\/bin.123456 > output.sql<\/p>\n
to create the database dump. After this file is created, we can delete the offending statement that we would not want re-run. Alternately, if you know the specific binary log position, you can use the –start-position flag. Here are some articles on this process:<\/p>\n
http:\/\/dev.mysql.com\/doc\/refman\/5.1\/en\/point-in-time-recovery.html
\nhttp:\/\/dev.mysql.com\/doc\/refman\/5.5\/en\/point-in-time-recovery-times.html
\nhttp:\/\/dev.mysql.com\/doc\/refman\/5.1\/en\/point-in-time-recovery-positions.html<\/p>\n","protected":false},"excerpt":{"rendered":"
The “mysqlbinlog” command reads the binary logs and outputs them in SQL format. As a result, you can use it to create a database dump and then modify that file by hand. For example, let’s say that everything since April … Continue reading