Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. 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

I was wondering if anyone had any pointers on migrating MyIASM tables from mysql 5.5 to 5.6, specifically using Percona builds, via an rsync?

Is this safe?

I know we need to do a full mysqldump/reload for a migration for InnoDB tables but I didn't see any notes about significant changes to the MyISAM format between the two.

It would make things a little nicer for a rather large MyISAM db that would take several days to complete with a mysqldump.

share|improve this question
So, you want to move the MyISAM tables apart from the move of the InnoDB tables ??? – RolandoMySQLDBA Apr 22 '14 at 21:15
up vote 3 down vote accepted

MyISAM didn't change between 5.5 and 5.6. It's not being developed, and it's virtually stagnant.

Use FLUSH TABLES WITH READ LOCK and then it's safe to copy the MyISAM tables. This is mentioned in

Other solutions:

  • mysqldump --tab outputs tab-delimited data files instead of SQL, so it's much faster to import with mysqlimport.

  • mysqlhotcopy does a physical copy of MyISAM tables (it doesn't work for InnoDB tables). But be careful because mysqlhotcopy is on the chopping block for deprecation.

  • mydumper, which dumps to SQL, but it supports compression and multi-threaded execution for both dump and restore. Unfortunately it does not support an option like --tab.

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.