Setting Up Binary Log File Position Based Replication requires extra steps to produce a perfect “point in time”  snapshot: the initial copy command could leave out cache information and logging updates, even if you have acquired a global read lock. How the storage engine responds to this depends on its crash recovery abilities. If you use  InnoDB  tables, you can use the  mysqlbackup  command from the MySQL Enterprise Backup component to produce a consistent snapshot. This command records the log name and offset corresponding to the snapshot to be used on the replica. MySQL Enterprise Backup is a commercial product that is included as part of a MySQL Enterprise subscription. See Section 30.2, “MySQL Enterprise Backup Overview”  for detailed information. This method also does not work reliably if the source and replica have different values for ft_stopword_file ,  ft_min_word_len , or  ft_max_word_len  and you are copying tables having full- text indexes. Assuming the above exceptions do not apply to your database, use the cold backup technique to obtain a reliable binary snapshot of  InnoDB  tables: do a slow shutdown of the MySQL Server, then copy the data files manually. To create a raw data snapshot of  MyISAM  tables when your MySQL data files exist on a single file system, you can use standard file copy tools such as  cp  or  copy , a remote copy tool such as  scp  or  rsync , an archiving tool such as  zip  or  tar , or a file system snapshot tool such as  dump . If you are replicating only certain databases, copy only those files that relate to those tables. For  InnoDB , all tables in all databases are stored in the system tablespace files, unless you have the  innodb_file_per_table  option enabled. The following files are not required for replication: •Files relating to the  mysql  database. •The replica’s connection metadata repository file  master.info , if used; the use of this file is now deprecated (see Section 17.2.4, “Relay Log and Replication Metadata Repositories” ). •The source’s binary log files, with the exception of the binary log index file if you are going to use this to locate the source binary log coordinates for the replica. •Any relay log files. 1. Acquire a read lock and get the source’s status. See Section 17.1.2.4, “Obtaining the Replication Source Binary Log Coordinates” . 2. In a separate session, shut down the source server: 3. Make a copy of the MySQL data files. The following examples show common ways to do this. You need to choose only one of them: 4. Restart the source server. shell>  tar cf  /tmp/db.tar ./data shell>  zip -r  /tmp/db.zip ./data shell>  rsync --recursive  ./data /tmp/dbdata shell>  mysqladmin shutdown If you are not using  InnoDB  tables, you can get a snapshot of the system from a source without shutting down the server as described in the following steps: 3444 Depending on whether you are using  InnoDB  tables or not, choose one of the following: If you are using  InnoDB  tables, and also to get the most consistent results with a raw data snapshot, shut down the source server during the process, as follows: