On 08/21/2013 05:43 PM, Reindl Harald wrote:
*forget it this can not work in a database with relations* * make a backup * close POP3/IMAP for the clients * stop dbmail-lmtpd * so you can have postfix online, receive new messages and defer them * after the migration is done start dbmail-lmtpd * postqueue -f * all new messages are delivered as you have two servers clone the complete setup including rsync of the whole database folders and test the migration there
Service downtime is veeery undesirable, thats why the partial migration issue rose. Its not just the IMAP access to stop, its all the services utilizing mail access to shut down. Basically even minimal data migration is painful from the time consuming perspective.
rsync databases: * first time hot with db-server running on production * stop the services on the source * rsync again * start the services on the source this are a few bash-lines and the downtime is very small because the way rsync works only transfer changes
This won't fly, I forgot to say mysql -> oracle migration is implied :) -- Best regards, Pavlo Lavrenenko, PortaOne, Inc., Junior Software Developer Tel: +1-866-SIP VOIP (+1 866 747 8647) ext. 7624 PortaOne - VoIP Solutions Company Visit our Website: http://www.portaone.com _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
