# percona xtrabackup 2.2.4 innobackup update

**URL:** <https://forums.percona.com/t/percona-xtrabackup-2-2-4-innobackup-update/3806>\
**Category:** Percona XtraBackup\
**Created:** [October 8, 2014, 4:42am UTC](https://forums.percona.com/t/percona-xtrabackup-2-2-4-innobackup-update/3806 "2014-10-08T04:42:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![giantmangu888](https://avatars.discourse-cdn.com/v4/letter/g/4491bb/32.png) [@giantmangu888](https://forums.percona.com/u/giantmangu888)\
**Post date:** [October 8, 2014, 4:42am UTC](https://forums.percona.com/t/percona-xtrabackup-2-2-4-innobackup-update/3806/1 "2014-10-08T04:42:33Z")

</div>

when I backup mysql5.6.19 on slave with percona-xtrabackup 2.2.4，I find that innobackupex executes the command：  
FLUSH ENGINE LOGS  
this command will be record to slave binlog，which leads to inconsistency between master and slave

NOw,I have update the innobackupex file ,as follows:  
change the line :  
mysql\_query(%mysql, “FLUSH ENGINE LOGS”);  
to  
mysql\_query(%mysql, “set sql\_log\_bin=OFF”);  
mysql\_query(%mysql, “FLUSH ENGINE LOGS”);  
mysql\_query(%mysql, “set sql\_log\_bin=ON”);

I have test it,and now do not record “FLUSH ENGINE LOGS” to slave binlog

that 'all

---

<div class="post-metadata">

**Author:** ![sqlcat](https://avatars.discourse-cdn.com/v4/letter/s/c67d28/32.png) [@sqlcat](https://forums.percona.com/u/sqlcat)\
**Post date:** [October 9, 2014, 3:42am UTC](https://forums.percona.com/t/percona-xtrabackup-2-2-4-innobackup-update/3806/2 "2014-10-09T03:42:30Z")

</div>

why not use (FLUSH ENGINE LOGS)

---

<div class="post-metadata">

**Author:** ![giantmangu888](https://avatars.discourse-cdn.com/v4/letter/g/4491bb/32.png) [@giantmangu888](https://forums.percona.com/u/giantmangu888)\
**Post date:** [October 9, 2014, 10:20pm UTC](https://forums.percona.com/t/percona-xtrabackup-2-2-4-innobackup-update/3806/3 "2014-10-09T22:20:39Z")

</div>

These methods have the same [COLOR=#2B2B2B]