Re: MYSQL Backup on SLAVE
Posted by:
Rick James
Date: December 23, 2012 10:35AM
You paid for MEB; they should answer your questions.
I don't know what "BACKUP-AND-APPLY-LOG" does, but it may include some of the following...
Daily backup of a Slave gives you a daily point-in-time backup. This is useful only if you lose both the Master and the Slave.
Keeping _all_ the binlogs lets you recreate a Slave from scratch. This is usually very impractical, so I won't consider it as an option.
If you lose the Slave, you need to stop the Master (or otherwise stop all write operations) while taking a full dump. This full dump will give you an point-in-time snapshot for rebuilding the Slave (inclucing binlog position -- for subsequent CHANGE MASTER). After you restart the Master, and while you are rebuilding the Slave, things will be written to the binlog. This is not problem. The Slave will "catchup" after the CHANGE MASTER.
If you lose the Master, you will realize that you should have set up "dual master" so that it would be quicker to promote the Slave to be the new Master. (If there is some reason for not leaving it as the Master going forward, then so state; we can discuss the pros and cons.)
If you do chose to rebuild the Master from the Slave, stop the slave, copy everything (except server-id, binlog/replicate-do/ignore, read-only, etc), start the slave, start the master, do CHANGE MASTER (if necessary), etc.
MEB may be doing some of these steps for you.