Re: Migrating Database
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 [EMAIL PROTECTED] To: mysql@lists.mysql.com 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/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Migrating Database
Brian Erickson wrote: 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! If you could bring both database servers down, you could tar up the data directory and untar it on the other server. -- Ryan Cavicchioni GPG ID: C271BCA8 GPG Public Key: http://confabulator.net/gpg/ryan.asc GPG Fingerprint: 83E4 2495 6194 0F66 ED85 22B4 4CC0 DA01 C271 BCA8 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Migrating Database
MySQL data files are binary compatible from one machine to another. Even InnoDB data files. As long as you are not trying to upgrade from version 3.23 to version 4.1, you are okay with copying the data files from one machine to another. -- Partha Dutta Sr. Consultant, MySQL Inc. Quoting Chris Knipe [EMAIL PROTECTED]: 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 [EMAIL PROTECTED] To: mysql@lists.mysql.com 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/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
