The following lines were added (+) and removed (-):
How you choose to backup the MySQL database may also depend on the MySQL engine employed. [[MySQL Engines MyISAM and Innodb]] How you choose to backup the MySQL database may also depend on the MySQL engine employed. [[MySQL Engines MyISAM and Innodb]] and both be backed up using mysqldump. However, with Innodb, just copying the .frm and .ibd files from one location to another will likely lead to a 'table does not exist' error when you try to access the database on the restored system. == Raw Dump == This works fine with MyISAM engine databases. It can also work with Innodb if you are making a backup that is to be restored to the exact same system, in the exact same place, with the exact same version of MySQL. Raw Dumps are not advised with Innodb if you are moving the database to another server, say, for migration. "''Just copying the .frm and .ibd files from one location to another is asking for trouble. Copying the .frm and .ibd file of an InnoDB table is only good if and only if you can guarantee that the tablespace id of the .ibd file matches exactly with the tablespace id entry in the metdata of the ibdata1 file.''" source: http://stackoverflow.com/questions/5745221/import-frm-and-opt-files-to-mysqlYou can also simply copy all table files (`*.frm', `*.MYD', and `*.MYI' files) as long as the server isn't updating anything. The script mysqlhotcopy does use this method.If your MySQL database uses the MyISAM engine, you can simply copy all table files (`*.frm', `*.MYD', and `*.MYI' files) as long as the server isn't updating anything. The script mysqlhotcopy does use this method.