EmergencyEMERGENCY? Get 24/7 Help Now!

How to create a new (or repair a broken) GTID based slave with Percona XtraBackup

 | May 9, 2013 |  Posted In: Insight for DBAs, MySQL, Percona XtraBackup


Percona XtraBackup 2.0.7 has been published with support for GTID based replication. As promised, here is the step-by-step guide on how to create a new GTID based slave (or repair a broken one) using XtraBackup. The process is pretty straightforward.

1- Take a backup from any server on the replication environment, master or slave:

In the destination folder there will be a file with the name xtrabackup_binlog_info:

Now it contains both, binary log coordinates and GTID information.

That information is also printed by innobackupex after backup is taken:

2- Apply the logs to the backup:

3- Move the backup to the destination server and put the content on the mysql’s datadir. Follow the usual restore procedure, for example remember to change the permissions to mysql:mysql.

4- Start the new slave from that GTID position:

5- Check the replication status:

We can see that the slave has retrieved a new transaction with number 5, so transactions from 1 to 5 are already on this slave.

That’s all, we have created a new slave in our GTID based replication environment.

Miguel Angel Nieto

Miguel joined Percona in October 2011. He has worked as a System Administrator for a Free Software consultant and in the supporting area of the biggest hosting company in Spain. His current focus is improving MySQL and helping the community of Free Software to grow.


  • Can’t wait til the production ready version of 5.6 comes out just for the GTIDs.

    On an unrelated note.. anyone notice that the code blocks don’t work in Chrome? Works fine in IE.

  • Hi Miguel,

    would it be possible to stream the backup to the slave and apply the logfiles there? The first part works but I’m not sure about the “apply-log”-part.

  • Jens:
    better late than never 🙂

    you can run –apply-log on the slave as innobackupex has nothing to do with the original redo-logs in this phase as it saves the changes in transaction logs to “xtrabackup_logfile” during the first run. In fact innobackupex with –apply-log calls the xtrabackup two times: first time to perform a crash recovery(using “xtrabackup_logfile”) and for the second time to generate the new translogs.


  • Don’t forget to run “reset master;”
    in case you get “ERROR 1840 (HY000): @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.” error

Leave a Reply