On 02/08/2012 10:56 AM, Reindl Harald wrote:
>
>
> 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
Eh, if you use 'mysqldump --single-transaction' the top of the output
will contain the information you need to start-up the new mysql
installation as a slave of the old one.
And --single-transaction will also prevent table locks and enable MVCC
if the database dumped is in innodb.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/i...@nfg.nl/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
