Shulou(Shulou.com)06/02 Report--

[background]

When maintaining mysql, you will always encounter examples of database recovery. It is relatively easy to recover the backup set. However, if you encounter an example of restoring to a point in time, after restoring a MySQL instance, you need to perform binlog to do an incremental recovery.

[method 1]

A common way is to parse binlog with mysqlbinlog and redirect the parsed content to the mysql command line for execution.

# start is the number after mysql-bin

Click (here) to collapse or open

I=startwhile [$I-lt end] domysqlbinlog mysql-bin.$i | mysql- h 127.0.0.1-P 4001-uroot > 0550.log 2 > & 1done can do this, and binlog in row mode can also be executed in this way. But this has several drawbacks.

1. What if the parsed binlog reports an error during execution? Is it enforced directly by adding-f?

two。 How to stop in the middle of the execution and keep running next time? For example, I want to adjust the parameters of MySQL (need to restart) and continue to run?

3. Can only be executed in a single thread. And mysqlbinlog parsing is performed through the pipeline, which has a relatively high performance overhead.

In view of the above shortcomings, here is another way to implement a large number of binlog.

[method 2]

We all know that the content of relay-log is the same as that of binlog, so can I execute binlog as a relay-log?

The answer is yes, it works all the time.

Detailed steps:

0. First make the instance normal shutdown

1. Upload binlog to the local disk of the mysql server and put it in a fixed directory, such as / home/mysql/restore_1031

two。 If it is the Mmurs architecture, you need to modify the master.info to write the following

Click (here) to collapse or open

Cat > $BINLOG_DIR/master.info

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.