Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
There are times when a table / database is dropped unintentionally.
I have to check the date-time of the start position from the binary when the backup was taken.
I do also have to check the date-time of the position where the “drop” statement is found. I do run the mysqlbinlog statement with those parameters.
I can not use start-position and stop-position parameters because the binaries are spread across different files. Is there any better way to handle such human mistakes?
every time you take a backup, you should be using FLUSH TABLES WITH READ LOCK to force all of the tables in to a consistent state, followed by FLUSH LOGS to close the current binary log. then, when you apply the backup, all you have to do is replay one binary log.