# Mysqldump and locking tables

**URL:** <https://forum.inductiveautomation.com/t/mysqldump-and-locking-tables/35124>\
**Category:** Ignition\
**Tags:** database\
**Created:** [May 28, 2020, 2:21pm UTC](https://forum.inductiveautomation.com/t/mysqldump-and-locking-tables/35124 "2020-05-28T14:21:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jfryar](https://avatars.discourse-cdn.com/v4/letter/j/8e8cbc/32.png) [@jfryar](https://forum.inductiveautomation.com/u/jfryar)\
**Post date:** [May 28, 2020, 2:21pm UTC](https://forum.inductiveautomation.com/t/mysqldump-and-locking-tables/35124/1 "2020-05-28T14:21:57Z")

</div>

Our server is running MySQL and we use a scheduled batch file to run mysqldump on the database each morning. This backup is taking over 50 minutes to complete which causes transaction groups and historical data to go to store and forward. I’m pretty certain it’s because mysqldump is locking the tables during backup.

I’ve read in articles such as this one

> **[How to backup MySQL database using Mysqldump without locking?](https://www.eversql.com/how-to-backup-mysql-database-using-mysqldump-without-locking/)**
>
> Mysqldump can be executed without locking the entire database for read or write. All you need is to use a specific flag when running the tool.

that you can specify some options that will do the backup without locking out the tables. Does anyone have experience with this?