How to fix ERROR 1185: Storage engine doesn't support binary dump in MySQL

MySQLINTERMEDIATEHIGHUpdated Dec 23, 2025· 103 views

ERROR 1185 occurs when attempting binary backup operations on tables with storage engines that don't support this feature. Use mysqldump for logical backups or convert tables to InnoDB.

Quick fix

Fixes 1185

SHOW TABLE STATUS WHERE Name = 'your_table_name';
  1. Check your table's storage engine
  2. Switch to mysqldump for logical backups
  3. Convert to InnoDB if you need binary backups
  4. Use appropriate backup tools
mysql — error
SHOW TABLE STATUS WHERE Name = 'your_table_name';
ERROR 1185: Storage engine doesn't support binary dump

What this error means

This error (ER_DUMP_NOT_IMPLEMENTED) indicates that the MySQL storage engine for your table does not support binary table dumps. Not all storage engines—such as MEMORY, ARCHIVE, or certain third-party engines—support binary/physical backup operations. This restriction is particularly relevant when using tools like FLUSH TABLES ... FOR EXPORT or mysqlhotcopy, which rely on the storage engine's binary dump capability.

Typical symptoms

  • Binary dump operations fail with "Storage engine doesn't support binary dump"
  • FLUSH TABLES ... FOR EXPORT command returns error 1185
  • mysqlhotcopy fails when attempting to back up affected tables
  • Physical/binary backup tools abort unexpectedly
  • Backup automation scripts fail during binary dump phase

Common causes

  1. Table uses a storage engine that doesn't support binary dumps (e.g., MEMORY, ARCHIVE, MERGE, FEDERATED)
  2. Attempting FLUSH TABLES ... FOR EXPORT on non-InnoDB tables
  3. Using legacy backup tools incompatible with your table's storage engine
  4. Mixed storage engines in the same backup operation

How to fix "ERROR 1185: Storage engine doesn't support binary dump"

1Check your table's storage engine

Run this query to see what engine your table uses:

sql
SHOW TABLE STATUS WHERE Name = 'your_table_name';

Look at the Engine column. Common values: InnoDB, MyISAM, MEMORY, ARCHIVE, MERGE, FEDERATED.

For all tables in your database:

sql
SHOW TABLE STATUS;
2Switch to mysqldump for logical backups

The recommended solution is to use mysqldump, which works with all storage engines:

bash
mysqldump -u username -p database_name > backup.sql

For a specific table:

bash
mysqldump -u username -p database_name table_name > table_backup.sql

This creates a logical SQL dump that can be restored to any MySQL instance, regardless of storage engine.

3Convert to InnoDB if you need binary backups

If you specifically need binary dump support, convert your table to InnoDB:

sql
ALTER TABLE table_name ENGINE=InnoDB;

Verify the change:

sql
SHOW TABLE STATUS WHERE Name = 'table_name';

Note: This can be slow on large tables. Plan the conversion during low-traffic periods.

4Use appropriate backup tools

For production environments:

For InnoDB tables:
- MySQL Enterprise Backup (official)
- Percona XtraBackup (open source, highly recommended)
- mysqldump with --single-transaction for consistency

For mixed storage engines:
- mysqldump (works with everything)
- Logical backups via your application layer

Example with mysqldump and gzip compression:

bash
mysqldump -u username -p --all-databases | gzip > full_backup.sql.gz

Advanced notes

Storage engine compatibility varies widely. MEMORY tables store data in RAM and are rebuilt from scratch on server restart, making physical backups impossible. ARCHIVE tables are designed for compression and sequential access, not binary export. If you're using third-party storage engines (like Sphinx, Connect), check their documentation for backup capabilities. For high-availability setups, consider replication instead of binary backups: set up a slave instance and back up from the slave using mysqldump with --single-transaction to avoid table locks.

Frequently asked questions

What does "1185" mean?
This error (ER_DUMP_NOT_IMPLEMENTED) indicates that the MySQL storage engine for your table does not support binary table dumps. Not all storage engines—such as MEMORY, ARCHIVE, or certain third-party engines—support binary/physical backup operations. This restriction is particularly relevant when using tools like FLUSH TABLES ...
How do I fix "1185"?
ERROR 1185 occurs when attempting binary backup operations on tables with storage engines that don't support this feature. Use mysqldump for logical backups or convert tables to InnoDB.
What causes "1185"?
Table uses a storage engine that doesn't support binary dumps (e.g., MEMORY, ARCHIVE, MERGE, FEDERATED) Attempting FLUSH TABLES ... FOR EXPORT on non-InnoDB tables Using legacy backup tools incompatible with your table's storage engine
Is the "1185" error serious?
Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading