Re: binlog file deleted accidentally
If your database is not critical I would just shut it down briefly for the transition. You could set up an rsync to copy the binary logs to the new location while MySQL is still running so that after shutdown it would only have to finish up the last bit to catch up.
As for doing it with MySQL still running, I am not positive how MySQL would handle that since it has at least the most current log open. Your best bet would be to do another "FLUSH TABLES WITH READ LOCK" to prevent any new binlog entries from being created while you were switching it over to the new location, but I cannot say for sure if that would work or not. So you'd have to do some more research on that.
--
Scott Nemes
MySQL DBA
http://www.linkedin.com/in/scottnemes
http://www.twitter.com/ScottNemes
Subject
Written By
Posted
Re: binlog file deleted accidentally
August 16, 2012 06:38PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.