# innodb backup

**URL:** <https://forums.percona.com/t/innodb-backup/1087>\
**Category:** Other MySQL® Questions\
**Created:** [February 15, 2009, 3:51pm UTC](https://forums.percona.com/t/innodb-backup/1087 "2009-02-15T15:51:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![farrokhp](https://avatars.discourse-cdn.com/v4/letter/f/a183cd/32.png) [@farrokhp](https://forums.percona.com/u/farrokhp)\
**Post date:** [February 15, 2009, 3:51pm UTC](https://forums.percona.com/t/innodb-backup/1087/1 "2009-02-15T15:51:01Z")

</div>

what is your strategy for backing up a very large high traffic innodb database? if you can provide a brief script that would be great.

---

<div class="post-metadata">

**Author:** ![ahbruinsma](https://avatars.discourse-cdn.com/v4/letter/a/dc4da7/32.png) [@ahbruinsma](https://forums.percona.com/u/ahbruinsma)\
**Post date:** [February 17, 2009, 12:03pm UTC](https://forums.percona.com/t/innodb-backup/1087/2 "2009-02-17T12:03:42Z")

</div>

I know of a few options, you’ve got mysql hotbackup, it’s a snapshot-type backup tool but isn’t free.

For small databases you can do a dump like:

mysqldump --master-data=1 --single-transaction \>DB.dump

fyi:

The --master-data option automatically turns off --lock-tables. It also turns on --lock-all-tables, unless --single-transaction also is specified (in which case, a global read lock is acquired only for a short time at the beginning of the dump. See also the description for --single-transaction. In all cases, any action on logs happens at the exact moment of the dump.