Setting Up Binary Log File Position Based Replication shell>  mysql < fulldb.dump b. If you created a snapshot using the raw data files, extract the data files into your replica’s data directory. For example: 2. Configure the replica with the replication coordinates from the source. This tells the replica the binary log file and position within the file where replication needs to start. Also, configure the replica with the login credentials and host name of the source. For more information on the  CHANGE REPLICATION SOURCE TO  |  CHANGE MASTER TO  statement required, see Section 17.1.2.7, “Setting the Source Configuration on the Replica” . 3. Start the replication threads by issuing a  START REPLICA | SLAVE  statement. You may need to set permissions and ownership on the files so that the replica server can access and modify them. Then start the replica server, ensuring that replication does not start by using the --skip-slave-start  option, or from MySQL 8.0.24, the  skip_slave_start  system variable. shell>  tar xvf dbdump.tar After you have performed this procedure, the replica connects to the source and replicates any updates that have occurred on the source since the snapshot was taken. Error messages are issued to the replica’s error log if it is not able to replicate for any reason. The replica uses information logged in its connection metadata repository and applier metadata repository to keep track of how much of the source’s binary log it has processed. From MySQL 8.0, by default, these repositories are tables named  slave_master_info  and  slave_relay_log_info  in the  mysql database. Do  not  remove or edit these tables unless you know exactly what you are doing and fully understand the implications. Even in that case, it is preferred that you use the  CHANGE REPLICATION SOURCE TO  |  CHANGE MASTER TO  statement to change replication parameters. The replica uses the values specified in the statement to update the replication metadata repositories automatically. See Section 17.2.4, “Relay Log and Replication Metadata Repositories” , for more information. The contents of the replica’s connection metadata repository override some of the server options specified on the command line or in  my.cnf . See Section 17.1.6, “Replication and Binary Logging Options and Variables” , for more details. A single snapshot of the source suffices for multiple replicas. To set up additional replicas, use the same source snapshot and follow the replica portion of the procedure just described. To set up the replica to communicate with the source for replication, configure the replica with the necessary connection information. To do this, on the replica, execute the  CHANGE REPLICATION SOURCE TO  statement (from MySQL 8.0.23) or  CHANGE MASTER TO  statement (before MySQL 8.0.23), replacing the option values with the actual values relevant to your system: 17.1.2.7 Setting the Source Configuration on the Replica Note mysql>  CHANGE MASTER TO -> MASTER_HOST=’ source_host_name ’, -> MASTER_USER=’ replication_user_name ’, -> MASTER_PASSWORD=’ replication_password ’, -> MASTER_LOG_FILE=’ recorded_log_file_name ’, -> MASTER_LOG_POS= recorded_log_position ; Or from MySQL 8.0.23: mysql>  CHANGE REPLICATION SOURCE TO -> SOURCE_HOST=’ source_host_name ’, -> SOURCE_USER=’ replication_user_name ’, 3447