# Xtrabackup: flush tables replicated after upgrade to 5.7.41

**URL:** <https://forums.percona.com/t/xtrabackup-flush-tables-replicated-after-upgrade-to-5-7-41/25343>\
**Category:** Percona XtraBackup\
**Created:** [September 21, 2023, 12:03pm UTC](https://forums.percona.com/t/xtrabackup-flush-tables-replicated-after-upgrade-to-5-7-41/25343 "2023-09-21T12:03:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sid.dabster](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sid.dabster/32/12863_2.png) [@sid.dabster](https://forums.percona.com/u/sid.dabster)\
**Post date:** [September 21, 2023, 12:03pm UTC](https://forums.percona.com/t/xtrabackup-flush-tables-replicated-after-upgrade-to-5-7-41/25343/1 "2023-09-21T12:03:20Z")

</div>

Hello,  
After upgrading from 5.7.22 to 5.7.41 we have huge problems with locks during backup  
i our multi-source setup. (Active - Passive)

Backup is run on the replica/Passive fine but then the “flush tables” statements make our source/active  
replica totally lock up.

Is there any way to tell xtrabackup to write the flush log statements with\_no\_binlog ?

Edit: Xtrabackup 2.4.28  
Mysql Community edition: 5.7.41

---

<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:** [September 21, 2023, 8:32pm UTC](https://forums.percona.com/t/xtrabackup-flush-tables-replicated-after-upgrade-to-5-7-41/25343/2 "2023-09-21T20:32:19Z")

</div>

Hello @sid.dabster,  
Can you confirm that you did not have this issue with 5.7.22 and xtrabackup 2.4.28? I just spun up a 5.7.22 and executed `FLUSH TABLES;` followed by `SHOW BINLOG EVENTS` and I can see the flush in the binlog which indicates you should have had this issue even back on 5.7.22.
