We've written about replication slaves lagging behind masters before, but one of the other side effects of the binary log being serialized, is that it also limits the effectiveness of using it for incremental backup. Let me make up some numbers for the purposes of this example:
- We have 2 Servers in a Master-Slave topology.
- The database size is 100 GB (same tables on each).
- The slave machine barely keeps up with the master (at 90% capacity during peak, 75% during offpeak)
- The peak window is 12 hours, the offpeak window is 12 hours.
Provided that the backup method was raw data files, it shouldn't take much more than 30 minutes to restore 100GB (50MB/s), but to replay one day of binary logs it would take an additional 20 hours ((12 * …
[Read more]