High Performance MySQL

Chapter 7. Replication

MySQL use often grows organically. In the corporate world, a single application developer may build the company’s next killer app on top of MySQL. This initial success with MySQL development typically breeds more projects and more success. As the amount of data you manage using MySQL grows, you’ll certainly appreciate its ability to handle large amounts of data efficiently. You may even find that MySQL has become the de facto standard backend storage for your applications.

At the same time, you may also begin to wish for an easy way to copy all the data from one MySQL server to another. Maybe you need to share data with a remote office in your organization, or you might just like to have a “hot spare” available in case your server dies. Fortunately, MySQL has a built-in replication system. You can easily configure a second server as a slave of your master, ensuring that it has an exact copy of all your data.

In this chapter, we’ll examine all aspects of MySQL replication. We begin with an overview of how replication works, the problems it solves, and the problems it doesn’t solve. We then move on to the ins and outs of configuring replication. After that we’ll consider the various architectures you can construct using various numbers of masters and slaves. We’ll continue with a discussion of administrative issues, including maintenance, security, useful tools, and common problems. Finally, we’ll look ahead to some planned changes and improvements for MySQL’s ...