few queries to ask?

[omagen]

Hello friends,
I have got a mysql db on a Windows 2000 server that is using mysqldump to create an .sql file every 12 hours. The .sql file is about 340 mb, and there are 3 tables with > 750,000 rows in them. The mysqldump takes only a few minutes to run.

I'm setting up a 2nd copy of the database to a new catalog, so I can do some development work on a backup copy of the database. I launched mysqladmin, created the new empty catalog and a user for the catalog and went to restore.
I located my .sql file, restored into the new database and not overwrite my good one and it's been running now for 24+ hours and is only about 1/3 done.

Please tell me what am I doing wrong, and if my production db were to go down and I were to use this method to restore, are we down for 2+ days? Lastly, how to copy the raw data files to the new directory?
Thank you. -- This message may have been cut off and the rest will only be shown to members. To become a member, click here --

[Yadira]

If you can, provide your entire mysqldump command. Some of the options such as "--extended-insert" or "--disable-keys" can make the reload faster. The option "--opt" is a shortcut to enable several of the available options at once.

Using MyIsam tables, it would be possible to copy the files. Going by this route, you'll want to shutdown the database first so the tables are in a consistent state. -- This message may have been cut off and the rest will only be shown to members. To become a member, click here --