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 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 quickest way to do it. Please let me know how it goes if you decide to do it this way. Cheers, Anirudh Sundar On Mon, Jul 26, 2010 at 9:56 AM, Rob Wultsch <wult...@gmail.com> wrote: > 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 and > then load on the new master and slave, or is it faster to just set the new > master up as a slave, and when it catches up to the old master I "flip the > switch?" The catch is that the new hardware is in a different datacenter. > > > > In other words, which is faster: dump and load or replication over the > Internet? > > > > Thanks for your time. > > > > > There may be significantly better options available to you. > > What version are you coming from and what version are you to? > > What engines do you use (Innodb, MyISAM,etc)? > > Is the data directory currently mounted on a lvm volume? > > -- > Rob Wultsch > wult...@gmail.com > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/mysql?unsub=sundar.anir...@gmail.com > >
