Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
mysqldump -hlocalhost -uUSERNAME -pPASSWORD THEDATABASE | gzip > /home/db_backup/abc.sql.gz

tar -xzvf ./abc.sql.gz

mysql THEDATABASE -uroot -pPASSWORD < abc.sql

The important note is that currently, half of my tables are INNODB...and the other half are MYISAM.

If I run these commands...will my newly restored database keep the INNODB/MYISAM?

share|improve this question
up vote 2 down vote accepted

Look at the .sql file. Following each CREATE TABLE stanza, there should be an Engine= declaration. Those should match whatever engine the tables had when you performed the mysqldump. As long as the target mysql instance supports both storage engines, you should be all set.

share|improve this answer
I can't "look" at the file because I have 100 million rows in the database :/ – Alex Dec 8 '09 at 20:37
You should be fine. I've never seen a mysqldump not include the Engine definition. – EEAA Dec 8 '09 at 21:04

Beware of auto-increment integer fields that have a 0 value record -- I got bit by that:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.