"Ian P. Christian" <[EMAIL PROTECTED]> wrote: > In theory, I should be able to find out where the slave was up to in the > old logs, extract them manually and replay them on the slave, and then > reset the slave to use the new logs - however i'm not sure how reliable > that's going to be - or even how to go about doing it yet.
Assuming your slave is not usable by client programs now anyway and you don't mind it being unusable for a while longer, you can restart the slaving from scratch: 1. take a full mysqldump of the master, --with-master-data --flush-logs 2. drop your databases on the slave, stop slaving, and restore the dump 3. restart slaving on the slave using the master data in from the dump (see the mysql docs on how to set up replication if you need more detail) -- Cos -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
