On 4/12/06, Tim Lucia <[EMAIL PROTECTED]> wrote: > Would you not lock tables on the slave? The idea of catching it up implies > this is way it is done. Catching up means once replication can proceed once > the tables are unlocked (on the slave). > > At least that is the way I read it...
On the slave I perform a slave stop, (optional) lock tables, mysqldump, slave start. Since the slave is a dedicated backup instance, and is never connected to directly by applications, the backup is entirely transparent to database users. My suggestion is for the purpose of simplifying such a setup such that it can be performed from a single MySQL instance. Tez -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
