Chris.Leeworthy@stripped wrote:
>
>
> Hi Andy,
>
> On your first point, MySQL itself will not stop you from inserting or
> updating records on tables in the slave database, it's something you will
> need to protect yourself against. One of my colleagues discovered this to
> his cost when he accidentaly inserted records on the slave instead of the
> master.
>
I'm suprised it isn't mentioned more often by the tools in the maatkit
are absolutely fantastic and make repairing from that kind of damage
very achievable. I haven't seen how they work on very large databases,
but at least they will have a go at figuring out what happened and
generate some clues to recover
For those who don't know what I am talking about there is a very clever
tool which attempts to figure out the difference between two db replicas
and generates a set of sql which brings the databases back into sync -
it's designed to fix broken replication sync and so it generates sql
which should fix the differences (you can then examine it and decide if
it helps or not...)
Much easier than tearing down the database to resync when a failure
occurs! Can also repair damage where someone updates a slave server for
example!
Ed W
