Setting Up Binary Log File Position Based Replication •Implement replication-specific security measures on the sources and replicas as appropriate for your system. See Section 17.3, “Replication Security” . •To set up replication for a fresh installation of a source and replicas that contain no data, see Setting Up Replication with New Source and Replicas. •To set up replication of a new source using the data from an existing MySQL server, see Setting Up Replication with Existing Data. •To add replicas to an existing replication environment, see Section 17.1.2.8, “Adding Replicas to a Replication Environment” . Note Certain steps within the setup process require the  SUPER  privilege. If you do not have this privilege, it might not be possible to enable replication. After configuring the basic options, select your scenario: Before administering MySQL replication servers, read this entire chapter and try all statements mentioned in Section 13.4.1, “SQL Statements for Controlling Source Servers” , and Section 13.4.2, “SQL Statements for Controlling Replica Servers” . Also familiarize yourself with the replication startup options described in Section 17.1.6, “Replication and Binary Logging Options and Variables” . To configure a source to use binary log file position based replication, you must ensure that binary logging is enabled, and establish a unique server ID. Each server within a replication topology must be configured with a unique server ID, which you can specify using the  server_id  system variable. This server ID is used to identify individual servers within the replication topology, and must be a positive integer between 1 and (2$^{32}$) − 1. The default  server_id value from MySQL 8.0 is 1. You can change the  server_id  value dynamically by issuing a statement like this: 17.1.2.1 Setting the Replication Source Configuration SET GLOBAL server_id = 2; How you organize and select the server IDs is your choice, so long as each server ID is different from every other server ID in use by any other server in the replication topology. Note that if a value of 0 (which was the default in earlier releases) was set previously for the server ID, you must restart the server to initialize the source with your new nonzero server ID. Otherwise, a server restart is not needed when you change the server ID, unless you make other configuration changes that require it. Binary logging is required on the source because the binary log is the basis for replicating changes from the source to its replicas. Binary logging is enabled by default (the  log_bin  system variable is set to ON). The  --log-bin  option tells the server what base name to use for binary log files. It is recommended that you specify this option to give the binary log files a non-default base name, so that if the host name changes, you can easily continue to use the same binary log file names (see Section B.3.7, “Known Issues in MySQL” ). If binary logging was previously disabled on the source using the  --skip-log-bin  option, you must restart the server without this option to enable it. The following options also have an impact on the source: •For the greatest possible durability and consistency in a replication setup using  InnoDB  with transactions, you should use Note 3439