Am 08.02.2012 10:41, schrieb Paul J Stevens: > On 02/08/2012 10:31 AM, Reindl Harald wrote: >> >> this maybe a much smoother way as export/transfer/import gigabytes >> of mysqldumps since it does not interrupt services > > How does a mysqldump interrupt services??
dumping gigabytes of data takes time i guess there are partly locks but the dumping is not the main problem it is the time until the dump is on the new server imported finally you need imapsync after the import to get the last messages even after change the MX since there is a timewindow where new messages are received on the old one * imapsync * another imapsync to get diffs * last imapsync whith delete option * change MX * normal imapsync several times which is fast to transfer the last new msgs to optimize this i would recommend using compressed SSH tunnel ______________ if both servers are on different locations i would always prefer imapsync in this case where "innodb_file_per_table" should be changed on the new server - without this change rsync auf the mysldatadir is the best way * hot rsync while services running * second one to get changes * shutdown source server * final rsync to get conistently last changes * start new server the rsync way with mixed cold/hot in the right order is really fast, independent how large are the databases and works well over WAN (compressed and encrypted)
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
