# Waiting for table backup lock drop table if exists file\_search

**URL:** <https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657>\
**Category:** Uncategorized\
**Created:** [March 8, 2022, 11:08am UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657 "2022-03-08T11:08:00Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![danarashad](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@danarashad](https://forums.percona.com/u/danarashad)\
**Post date:** [March 8, 2022, 11:08am UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/1 "2022-03-08T11:08:00Z")

</div>

Does running a backup cause the database to lock. While running show processlist i am getting `Waiting for table backup lock drop table if exists file_search`. I am currently running a backup and inserting data using scripts. The jobs are failing with deadlock errors.

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [March 9, 2022, 1:09pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/2 "2022-03-09T13:09:53Z")

</div>

Hello, during a backup you should not run any DDL statements, as the backup requires a metadata lock at certain point. Check [Backup Locks — Percona Server 8.0 Documentation](https://www.percona.com/doc/percona-server/8.0/management/backup_locks.html) for more info

---

<div class="post-metadata">

**Author:** ![danarashad](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@danarashad](https://forums.percona.com/u/danarashad)\
**Post date:** [March 9, 2022, 2:08pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/4 "2022-03-09T14:08:20Z")

</div>

The link does not say innodb? Only `MyISAM, CSV, MEMORY, ARCHIVE, TokuDB, and MyRocks tables`. All of my tables are innodb, so I shouldn’t get the lock?

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [March 9, 2022, 2:11pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/5 "2022-03-09T14:11:33Z")

</div>

Perhaps the redaction is not clear but the lock to prevent DDL is taken for all tables, no matter which storage engine.

---

<div class="post-metadata">

**Author:** ![danarashad](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@danarashad](https://forums.percona.com/u/danarashad)\
**Post date:** [March 9, 2022, 2:13pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/6 "2022-03-09T14:13:29Z")

</div>

Thank you for the clarification, this helps a lot.

---

<div class="post-metadata">

**Author:** ![danarashad](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@danarashad](https://forums.percona.com/u/danarashad)\
**Post date:** [March 9, 2022, 3:41pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/7 "2022-03-09T15:41:29Z")

</div>

Does replication still work during backups or are those in a wait state as well?

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [March 9, 2022, 5:23pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/8 "2022-03-09T17:23:17Z")

</div>

Replication is not affected by the backup process

---

<div class="post-metadata">

**Author:** ![danarashad](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@danarashad](https://forums.percona.com/u/danarashad)\
**Post date:** [March 11, 2022, 12:08pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/9 "2022-03-11T12:08:36Z")

</div>

Does backup lock all nodes on the cluster from dml statements? I am running a backup and the node has issued the `waiting for table backup lock` the other node i tried to do some inserts and updates but I am running into table locks.

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [March 11, 2022, 12:21pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/10 "2022-03-11T12:21:47Z")

</div>

Are you running Percona XtraDB Cluster or traditional replication? which version? did you check that no DDL commands are being run?

---

<div class="post-metadata">

**Author:** ![danarashad](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@danarashad](https://forums.percona.com/u/danarashad)\
**Post date:** [March 11, 2022, 12:32pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/11 "2022-03-11T12:32:25Z")

</div>

running xtradb cluster 8.0.26. there might be a DDL running on the none backup node. Did something change between cluster 5.7 and 8.0.x. I have done the same back and the same activity, but these issues never happened on version 5.7. The only difference is i a using xbstream and on 5.7 i was using tar

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [March 11, 2022, 12:41pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/12 "2022-03-11T12:41:48Z")

</div>

OK, since you are running a cluster remember DDL entails a cluster-wide lock (in TOI mode) so that will conflict with the backup lock. You should avoid running DDL on ANY node while the backup is running.

---

<div class="post-metadata">

**Author:** ![danarashad](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@danarashad](https://forums.percona.com/u/danarashad)\
**Post date:** [March 11, 2022, 12:44pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/13 "2022-03-11T12:44:12Z")

</div>

thank you you have been really helpful. did this change between 5.7 and 8.0.x? With the older version we never encountered this issue. We used dml statements with temporary tables in the older version. is there a flag to ignore temp tables?

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [March 11, 2022, 12:48pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/14 "2022-03-11T12:48:01Z")

</div>

Nothing changed in this regard to the best of my knowledge. You should see the same behavior in 5.7… is it possible your DDL statements were not run at the same time as the backup before?

---

<div class="post-metadata">

**Author:** ![danarashad](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@danarashad](https://forums.percona.com/u/danarashad)\
**Post date:** [March 11, 2022, 12:50pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/15 "2022-03-11T12:50:44Z")

</div>

No it is not possible. the DDL statement is in a stored procedure that is used heavily (probably every 3rd hit to my application). It would be impossible for the stored procedure to not run during the backups.

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [March 11, 2022, 12:58pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/16 "2022-03-11T12:58:41Z")

</div>

I see. The only thing that comes to mind is that perhaps your dataset is bigger now so backups take longer and you notice the impact. If the backup used to take a short time before maybe it was too fast to notice?

---

<div class="post-metadata">

**Author:** ![danarashad](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@danarashad](https://forums.percona.com/u/danarashad)\
**Post date:** [March 11, 2022, 1:15pm UTC](https://forums.percona.com/t/waiting-for-table-backup-lock-drop-table-if-exists-file-search/14657/17 "2022-03-11T13:15:44Z")

</div>

No the dataset is more or less the same size about 1.3T. Since switching to xbstream the backups seem to go a lot quicker.
