Critical Bug : Wrong Table Types Used When Restoring From A Scheduled

[Distinctive]

Problem:

When restoring a backup file created using the “Scheduled backups” the original table type is not restored. Therefore the restored database could be considered corrupt, or different to the original.

Current behaviour:

Restoring a database backup file created using the “Scheduled backups” function restores all tables as “InnoDB” regardless of whether the original table is “MyISAM” or another storage engine.

Expected behaviour:

I would expect that when tables are restored that their original storage engine would be used.

Reproducable: Possibly always?

Steps to reproduce:

• Connect to a MySQL server using SQLyog, and find (or create) a database that contains tables that use a mix of storage engines.
• Use SQLyog to create a SQL dump of the entire database, as a single SQL file (either use the “Scheduled Backup wizard” or the “Backup database as SQL dump” function).
• Use the [Menu] > [Database] > [Import] > [Execute SQL Script] function to restore the SQL file to another MySQL server.
• After the restore operation is complete, look at the table structure of the restored database and you will notice that all tables are restored as InnoDB.

Further information:

• MySQL version that I made the backup from: 4.1.22
• MySQL version that I restored the backup file onto: 5.5.25

I have yet to test it on other MySQL servers but I do fully intend to test it on MySQL 5.5 to MySQL 5.5.

This is very important for me as I have two MyISAM tables that contain in excess of 15 million rows, should a backup be required to be restored in an emergency, we would need to perform a table conversion which would take a long time, delaying a potential disaster recovery.

backup file created using the “Scheduled backups” function

[Author]

Posts