After you stop the slave and start mysqldump,
execute the below on slave db.
show slave status\G.
Note down the Master_Log_File and Exec_Master_Log_Pos. This will be the
point from which you need to do the recovery.
regards
anandkl
On 9/25/07, Eric Frazier [EMAIL PROTECTED] wrote:
Boyd
Boyd Hemphill wrote:
I have executed a strategy for backup where I stop a slave and do a mysqldump
with --master-data. Both master and slave are 4.1.20
My assumption was that the log coordinates in the dump file would provide me with the place to replay the log for a point in time recovery.
I have executed a strategy for backup where I stop a slave and do a mysqldump
with --master-data. Both master and slave are 4.1.20
My assumption was that the log coordinates in the dump file would provide me
with the place to replay the log for a point in time recovery.
What I learned today
Thanks a bunch for the suggested workaround. This method was exactly
what I was looking for.
Thanks again.
CL
At 01:33 AM 6/20/2007, Ananda Kumar wrote:
One possible way is to spool the contents of bin-log into a file.
mysqlbinlog oca-bin.000554 binlog_sql.sql.
This will give you all the
Guys,
I'm attempting to reapply a number of bin-log files in a effort to
restore all changes that was made to a database. I'm performing the
following command, but continue to get a foreign key constraint error
message when doing so. Has anyone ever ran into this issue, and if
so, what is a
One possible way is to spool the contents of bin-log into a file.
mysqlbinlog oca-bin.000554 binlog_sql.sql.
This will give you all the data present in oca-bin.000554. Then you can set
the
foreign key check to 0 at the session level and then apply the
binlog_sql.sql.
Comment our everything
using the old update logs I could look inside them and use the contents to
help debug dynamic SQL statements.
How do I do the same with the binary log?
I have tried
mysqlbinlog hostname.001
but get
ERROR: Could not read entry at offset 5 : Error in log format or
read error
The
