Having to refresh from the master should be avoided. If one slave is ok,
...
I stop the slave, tar+zip the mysql directories to local disk, start slave.
Then copy backup to new slave, unpack, start mysql, wait for replication to
catchup.
BTW, this is a reason for having at least 2 slaves.
> Normally I > would just fix whatever issue I had then refresh the slave > using a mysqldump > with --master-data to get me back up and running but in this > setup, not > having a replication slave for any length of time would be a very bad > thing. >
--
MySQL Replication Mailing List
For list archives:
http://lists.mysql.com/replication
To unsubscribe:
http://lists.mysql.com/replication?unsub=lists@pantek.com
Received on Thu Sep 27 20:30:14 2007
This archive was generated by hypermail 2.1.8
: Sun Oct 07 2007 - 10:14:24 EDT
|