Skip navigation links

MySQL Forums :: Backup :: MySQL innoDBD Backup

Advanced Search

Re: MySQL innoDBD Backup
Posted by: Nick Roper ()
Date: August 05, 2004 02:51AM


In answer to your questions:

1) mysqldump should be available from the command line, i.e:

From windows:

c:\> mysqldump --options

Or Linux/Unix:

shell> mysqldump --options

If the MySQL installation is not included in your PATH sytem variable then you may have to use the full path to the utility, e.g.:

C:/> c:\mysql\bin\mysqldump --options

For information on how to use mysqldump and what the options are, see:

2) By default, the InnoDB engine stores information as follows:

Table format information is stored in a table.frm file in the database directory. So, for tables named table1 and table2 in a database named database1 the following files will exist:


Note: these store table format information - not data or indexes.

The data and indexes for all databases & tables will be stored in a single InnoDB tablespace which can comprise either a single file or multiple files. By default, the tablespace file(s) are stored in the server's data directory, i.e.:


You can in fact copy the tablespace and format files from one server to another, but you should be aware that this will not allow you to transfer a specific database - as the tablespace file(s) encompass all databases. If you just want to transfer a single database, then use a separate utility. Other conditions that apply are as follows:

Both machines must use two's-compliment integer arithmetic
Either both machines must use IEEE floating-point format, or none of of the InnoDB tables must contain floating-point columns.
If you need to transfer between Windows & non-Windows operating systems, then you must use lowercase names for databases and tables.

If you are transferring MyISAM files, then you should also take precautions to ensure that the tables are not being used by any client processes when you perform the copy.

The best source of information on all this is the MySQL Reference documentation at:

Hope this helps,


Nick Roper

Options: ReplyQuote

Subject Views Written By Posted
MySQL innoDBD Backup 3408 Yally Lee 08/01/2004 07:44PM
Re: MySQL innoDBD Backup 2517 Nick Roper 08/02/2004 03:57PM
Re: MySQL innoDBD Backup 2565 Yally Lee 08/04/2004 08:36PM
Re: MySQL innoDBD Backup 2656 Nick Roper 08/05/2004 02:51AM
Re: MySQL innoDBD Backup 2459 Yally Lee 08/06/2004 01:46AM
Re: MySQL innoDBD Backup 2652 Nick Roper 08/06/2004 04:13AM
Re: MySQL innoDBD Backup 2890 Yally Lee 08/09/2004 03:50AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.