# Clone plugin replica to replica cloning

**URL:** <https://forums.percona.com/t/clone-plugin-replica-to-replica-cloning/39191>\
**Category:** MySQL & MariaDB\
**Tags:** mysql\
**Created:** [August 21, 2025, 3:51pm UTC](https://forums.percona.com/t/clone-plugin-replica-to-replica-cloning/39191 "2025-08-21T15:51:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jknight](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@jknight](https://forums.percona.com/u/jknight)\
**Post date:** [August 21, 2025, 3:51pm UTC](https://forums.percona.com/t/clone-plugin-replica-to-replica-cloning/39191/1 "2025-08-21T15:51:43Z")

</div>

I have tried using a replica as the source to create a new replica using the clone plugin. All goes well except the binlog\_file, binlog\_position from performance\_schema.clone\_status shows a different log and position than the the source replica. The source replica does show the correct log and position. Is this not possible to clone a new replica this way? My other thought is to stop replication on the source replica and get the log and position and hold replication until the clone finishes. But I am not sure this is the best way to handle this. Suggestions?

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [August 21, 2025, 6:28pm UTC](https://forums.percona.com/t/clone-plugin-replica-to-replica-cloning/39191/2 "2025-08-21T18:28:31Z")

</div>

Hey @jknight,

Ideally, you shouldn’t be concerning yourself with binlog filenames/positions, and instead rely on GTID. By using GTID, it doesn’t matter what the filename/pos are.

I’ve used the CLONE plugin before, but never to create a replica from a replica. From your description, it seems the plugin assumes the clone’d server (ie: the replica) is the actual source mysql, instead of the upstream source. I bet the binlog info you are seeing is that of the replica. What you end up with is A→B→C but what you really want is A→B and A→C.

You can still accomplish this. Let the clone process finish. Once B→C is up to date, stop replica on C, execute `change replication source to source_host=A` and start replication back up. It should pick up right were it left off thanks to GTIDs.

---

<div class="post-metadata">

**Author:** ![jknight](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@jknight](https://forums.percona.com/u/jknight)\
**Post date:** [August 21, 2025, 9:10pm UTC](https://forums.percona.com/t/clone-plugin-replica-to-replica-cloning/39191/3 "2025-08-21T21:10:55Z")

</div>

Yes the plan is to get to GTID, but this set up has been bandaided for a long time and I am tasked with getting them up-to-date. I appreciate you input.

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [August 21, 2025, 9:38pm UTC](https://forums.percona.com/t/clone-plugin-replica-to-replica-cloning/39191/4 "2025-08-21T21:38:18Z")

</div>

Use Percona Xtrabackup then to create your replica. It has a feature to collect the binary log coordinates from the replica’s source. Use `--safe-slave-backup`and `--slave-info` when you take the backup of the replica.

---

<div class="post-metadata">

**Author:** ![jknight](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@jknight](https://forums.percona.com/u/jknight)\
**Post date:** [August 21, 2025, 10:11pm UTC](https://forums.percona.com/t/clone-plugin-replica-to-replica-cloning/39191/5 "2025-08-21T22:11:38Z")

</div>

Matthewb, That is certainly an option. Thank you for your response