Clone a Replication Slave From a Live Master using Global Transaction IDs (GTID) and mysqldump
Last updated on MARCH 26, 2018
Applies to:MySQL Server - Version 5.6 and later
Information in this document applies to any platform.
To clone a replication slave from a live master with existing data, extra steps must be taken to ensure that the data is copied as a consistent snapshot, and that the correct GTID status is transferred to the slave.
The requirements to achieve this are described in the manual here, but it does not fully detail the steps from start to finish:
This document explains the step-by-step process required to clone a master server while it is live and still receiving transactions, the servers need not be made read only.
If any of the steps do not behave as expected, please see the Error Log file which may contain useful information. To locate the error log, see <Note 1478045.1>.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms