Re: migration via replication for large DB?

2010-07-26 Thread Anirudh Sundar
Hello Goeff, Data Import might take some time (considering 50 GB) if the majority of the tables are of type INNODB. If yes, 4 hours should not be enough. If its MYISAM, you can go ahead (Provided you choose data import to replication). Another suggestion would be :- Take a FULL tar of the MYSQL

Re: migration via replication for large DB?

2010-07-26 Thread Prabhat Kumar
Another suggestion would be :- Take a FULL tar of the MYSQL Data Directory and push it to the NEW server and untar and start mysql (take the master status of the probable Master Server, for replication and bringing the new server to sync with its Master). I think this should be one of the

migration via replication for large DB?

2010-07-25 Thread Geoff Galitz
Hello. I need to migrate a master and slave to new hardware. The DB is approx 50G on disk and my time window for downtime is approximately 4 hours. My question is, is it advisable to do a mysqldump from the old master and then load on the new master and slave, or is it faster to just set

Re: migration via replication for large DB?

2010-07-25 Thread Rob Wultsch
On Sun, Jul 25, 2010 at 12:55 PM, Geoff Galitz ge...@galitz.org wrote: Hello. I need to migrate a master and slave to new hardware.  The DB is approx 50G on disk and my time window for downtime is approximately 4 hours. My question is, is it advisable to do a mysqldump from the old master