I've got a master-slave replication setup for a suite of applications.
One of those applications is a forum, which writes directly to the master. The rest just read from the slave. The forum database is huge (~10GB) which causes some issues re: backups and data transfers (even a mysqlhotcopy takes 20 minutes).
I want to run an upgrade of that forum software (ie. on the master) but during the upgrade, keep the slave from replicating (so the apps that hang off that can continue to function sans interruption).
My plan is something like:
- Take a mysqlhotcopy backup of the master
- Disable replication on the slave
- Run the upgrade on the master
- Re-enable replication on the slave
- Profit.
However, if it all goes pear-shaped, my backup plan is to restore the master from the mysqlhotcopy I took before starting the process.
If I do so - are there any issues related to replication I need to be aware of? If I restore from the mysqlhotcopy, will I need to clear out the mysql binary log to prevent the writes that happened to the master (which I'm logically overwriting from the backup) from occurring on the slave?