Oracle 5.0 Reference Manual page 1451

Chapter 16. Replication
Table of Contents
16.1. Replication Configuration ................................................................................................ 1432
16.1.1. How to Set Up Replication ................................................................................... 1433
16.1.2. Replication and Binary Logging Options and Variables ........................................... 1441
16.1.3. Common Replication Administration Tasks ............................................................ 1473
16.2. Replication Implementation .............................................................................................. 1475
16.2.1. Replication Implementation Details ........................................................................ 1476
16.2.2. Replication Relay and Status Logs ....................................................................... 1478
16.2.3. How Servers Evaluate Replication Filtering Rules .................................................. 1480
16.3. Replication Solutions ....................................................................................................... 1486
16.3.1. Using Replication for Backups .............................................................................. 1487
16.3.2. Using Replication with Different Master and Slave Storage Engines ........................ 1488
16.3.3. Using Replication for Scale-Out ............................................................................ 1489
16.3.4. Replicating Different Databases to Different Slaves ................................................ 1490
16.3.5. Improving Replication Performance ....................................................................... 1492
16.3.6. Switching Masters During Failover ........................................................................ 1493
16.3.7. Setting Up Replication Using SSL ......................................................................... 1495
16.4. Replication Notes and Tips ............................................................................................. 1497
16.4.1. Replication Features and Issues ........................................................................... 1497
16.4.2. Replication Compatibility Between MySQL Versions .............................................. 1508
16.4.3. Upgrading a Replication Setup ............................................................................. 1509
16.4.4. Troubleshooting Replication .................................................................................. 1510
16.4.5. How to Report Replication Bugs or Problems ........................................................ 1511
Replication enables data from one MySQL database server (the master) to be replicated to one
or more MySQL database servers (the slaves). Replication is asynchronous - slaves need not be
connected permanently to receive updates from the master. This means that updates can occur over
long-distance connections and even over temporary or intermittent connections such as a dial-up
service. Depending on the configuration, you can replicate all databases, selected databases, or even
selected tables within a database.
For answers to some questions often asked by those who are new to MySQL Replication, see
Section B.13, "MySQL 5.0 FAQ:
The target uses for replication in MySQL include:
• Scale-out solutions - spreading the load among multiple slaves to improve performance. In this
environment, all writes and updates must take place on the master server. Reads, however, may
take place on one or more slaves. This model can improve the performance of writes (since the
master is dedicated to updates), while dramatically increasing read speed across an increasing
number of slaves.
• Data security - because data is replicated to the slave, and the slave can pause the replication
process, it is possible to run backup services on the slave without corrupting the corresponding
master data.
• Analytics - live data can be created on the master, while the analysis of the information can take
place on the slave without affecting the performance of the master.
• Long-distance data distribution - if a branch office would like to work with a copy of your main data,
you can use replication to create a local copy of the data for their use without requiring permanent
access to the master.
Replication".
1431