Synchronizing Data and Supporting Replication - Mastering phpMyAdmin 3.4 for Effective MySQL Management - page 234

The first paragraph confirms that this server is not configured as a master in a
replication process. We want to achieve this configuration, but first we need to think
about the kind of replication we want. Should all databases be replicated, except for
some of them? Or do we want the opposite? A convenient drop-down list offers us
these choices:
• Replicate all databases; Ignore:
• Ignore all databases; Replicate:
The first choice (which is the default) implies that, in general, all databases are
replicated; we don't even have to enumerate them in the configuration file. In this
case, the databases selector is used to specify which database we want to exclude
from the replication process. Let us pick up the mysql database and see what
happens in our JavaScript-enabled browser:
We notice that a line appeared, stating binlog_ignore_db=mysql . This is a MySQL
server instruction (not a SQL statement) that tells the server to ignore sending
transactions about this database to the binary log. Let us examine the meaning of
the other lines. The server-id is a unique ID generated by phpMyAdmin; each
server that participates in replication must have a unique server ID. Therefore, we
either track the server IDs by hand, ensuring their uniqueness, or we simply use the
number randomly generated by phpMyAdmin. We also see the log-bin and log-
error instructions; in fact, binary logging is mandatory in order for any replication
to occur.