Setting Up Binary Log File Position Based Replication This method can also be used if you are setting up new servers but have an existing dump of the databases from a different server that you want to load into your replication configuration. By loading the data into a new source, the data is automatically replicated to the replicas. If you are setting up a new replication environment using the data from a different existing database server to create a new source, run the dump file generated from that server on the new source. The database updates are automatically propagated to the replicas: When setting up replication with existing data, transfer the snapshot from the source to the replica before starting replication. The process for importing data to the replica depends on how you created the snapshot of data on the source. To deploy multiple instances of MySQL, you can use InnoDB Cluster which enables you to easily administer a group of MySQL server instances in MySQL Shell. InnoDB Cluster wraps MySQL Group Replication in a programmatic environment that enables you easily deploy a cluster of MySQL instances to achieve high availability. In addition, InnoDB Cluster interfaces seamlessly with MySQL Router, which enables your applications to connect to the cluster without writing your own failover process. For similar use cases that do not require high availability, however, you can use InnoDB ReplicaSet. Installation instructions for MySQL Shell can be found here. If the replication source server or existing replica that you are copying to create the new replica has any scheduled events, ensure that these are disabled on the new replica before you start it. If an event runs on the new replica that has already run on the source, the duplicated operation causes an error. The Event Scheduler is controlled by the  event_scheduler  system variable, which defaults to  ON  from MySQL 8.0, so events that are active on the original server run by default when the new replica starts up. To stop all events from running on the new replica, set the  event_scheduler  system variable to  OFF  or  DISABLED  on the new replica. Alternatively, you can use the  ALTER EVENT  statement to set individual events to DISABLE  or  DISABLE ON SLAVE  to prevent them from running on the new replica. You can list the events on a server using the  SHOW  statement or the Information Schema  EVENTS  table. For more information, see Section 17.5.1.16, “Replication of Invoked Features” . As an alternative to creating a new replica in this way, MySQL Server’s clone plugin can be used to transfer all the data and replication settings from an existing replica to a clone. For instructions to use this method, see Section 5.6.7.6, “Cloning for Replication” . Follow this procedure to set up replication with existing data: 3446 a. If you used  mysqldump , 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. Then import the dump file: 1. If you used MySQL Server’s clone plugin to create a clone from an existing replica (see Section 5.6.7.6, “Cloning for Replication” ), the data is already transferred. Otherwise, import the data to the replica using one of the following methods. Setting Up Replication with Existing Data Note Tip shell>  mysql -h source < fulldb.dump