Home / server / Questions / 146525
Accepted
Dave Forgac
Asked: 2010-05-30 07:37:49 +0800 CST

How can I speed up a MySQL restore from a dump file?

  • 772

I am restoring a 30GB database from a mysqldump file to an empty database on a new server. When running the SQL from the dump file, the restore starts very quickly and then starts to get slower and slower. Individual inserts are now taking 15+ seconds. The tables are mostly MyISAM with one small InnoDB. The server has no other active connections. SHOW PROCESSLIST; only shows the insert from the restore (and the show processlist itself).

Does anyone have any ideas what could be causing the dramatic slowdown?

Are there any MySQL variables that I can change to speed the restore while it is progressing?

backup mysql restore

7 Answers

  1. Best Answer

    One thing that may be slowing the process is the key_buffer_size, which is the size of the buffer used for index blocks. Tune this to at least 30% of your RAM or the re-indexing process will probably be too slow.

    For reference, if you were using InnoDB and foreign keys, you could also disable foreign key checks and re-enable it at the end (using SET FOREIGN_KEY_CHECKS=0 and SET FOREIGN_KEY_CHECKS=1).

    • 34

  2. This link shows what one can do to speed up restoring process.

    http://dev.mysql.com/doc/refman/5.5/en/optimizing-innodb-bulk-data-loading.html

    One can put put the commands at the top of the dump file

    SET @OLD_AUTOCOMMIT=@@AUTOCOMMIT, AUTOCOMMIT = 0;
SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS = 0;
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS = 0;

    And put these statements at the end of the dump file

    SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;
SET AUTOCOMMIT = @OLD_AUTOCOMMIT;
COMMIT;

    This worked for me. Happy restoring :-)

    • 34

  3. If you have the physical copy of the dump file (the DB directory), you can just copy it to the new server if the new server have the same MySQL version and it will work fine. This work fine with MyISAM and for me I think it is better than restoring the data based on the logical SQL dump file.

    • 2

  4. This will do:

    mysql --init-command="SET SESSION FOREIGN_KEY_CHECKS=0;SET UNIQUE_CHECKS=0;" -u root -p < Backup_Database.mysql

    • 2

  5. if you have multiple tables chances are you might benefit from mk-parallel-restore.

    • 1

  6. The only reason I can image why the restore would gradually slow down is indexing. Investigate turning off indexing until the end and then let it do the whole lot at once.

    • 1

  7. I suggested you ,

    1. Check your tables: Do it has triggers? Clear all triggers
    2. SET: AUTOCOMMIT=0, UNIQUE_CHECKS=0, FOREIGN_KEY_CHECKS=0 (AND DON'T FORGET TO ROLLBACK THIS CHANGES)
    3. USE COMMAND LINE LIKE mysql -u root -pPasss requests < mydb.sql
    4. Check your database file size

    Good Luck

    • 0