Hi I am using replication to do online backups for my tables. Now my next task is to automate cleaning up of binary log files from Master server. Assuming I have more than one slave running, and may be at the time of clean up one of the slave is down for backup, how can I be sure that my clean up procedure is not deleting a binary log file that may be needed by the slave that is currently down?
In the documentation it says to check the log files currently being used by all the slaves and then delete logs in master by using PURGE cmd and specify the earliest among all the ones being used by all slaves. But this is lot of work if I am running many instances, as i am using mysqld_multi to run numerous instances. Also in the documentation it says "If you are using replication, you should not delete old binary log files until you are sure that no slave will ever need to use them. One way to do this is to do mysqladmin flush-logs once a day and then remove any logs that are more than 3 days old" But I don't feel comfortable about 3 day old thing, that seems to be an estimate but I would prefer a way so that I can go ahead and delete the logs from Master and it will only delete the ones not being used by the slave servers including the ones currently down for backups. If anyone has any tips or suggestions on this matter, please let me know I would appreciate help... Thanks Desktop Support School of Computer Science Florida International Univeristy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
