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

PREVIOUS POST
NEXT POST

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.

PREVIOUS POST
NEXT POST

Comments

  1. marc castrovinci says

    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.

  2. says

    Miguel, –

    I think code blocks not working is an AdBlock (and alike) issue so if you disable it, should work with any browser, but when AdBlock is on, they do not work.

  3. Jens Dietze says

    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.
    Regards,
    Jens

  4. Miklos Szel says

    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.

    cheers,
    Miklos

Leave a Reply

Your email address will not be published. Required fields are marked *