Re: Migrating Database

[Chris Knipe]

Temporary replication comes to mind.... fs hot copy as well (maybe)....


--
Chris.

I love deadlines. I especially love the whooshing sound they make as they 
fly by..." - Douglas Adams, 'Hitchhiker's Guide to the Galaxy'

----- Original Message ----- 
From: "Brian Erickson" <erickson.brian@stripped>
To: <mysql@stripped>
Sent: Sunday, May 08, 2005 10:47 PM
Subject: Migrating Database


Greetings all,

We are migrating our web site from one server to another and are
having some issues with transferring our MySQL database. Here's the
process we're currently using:

1) run mysqldump for each table in our database (i.e. one file for each 
table)
2) compress each file using gzip
3) transfer the files to our new server
4) decompress
5) import each table using:
mysql [dbname] < [filename]

Here's the problem: several of our tables have over 20 million rows,
and this import process is taking well over 6 hours. Obviously, our
site cannot go live until the database is fully imported, and this is
much too long for us to be down.

The two possible solutions I've researched are:

1) Copy data files directly. This concerns me because of possible
version incompatibilities.
2) Using LOAD DATA commands. I'm not familiar with these at all, and
frankly, not real sure how they work.

Can anyone offer us some advice as to the easiest way we can
accomplish this, whether it's one of the above solutions, or another
one completely?

Thanks in advance!

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=1