Migration question

Ludvík Schmarcz schmarcz at blacksun.cz
Tue Mar 14 23:20:25 CET 2017


Hi Olivier,

question is, if you have one public IP address for both servers (behind NAT), or every one have own public IP address. In first case do nothing, only correctly set up postfix on new server as on old one. In second case you must add second server as next mail server (MX record) with low priorinty number. Good practice also is to reduce the expiration MX records to a small value (600s). In this moment you must turn off postfix or block postfix ports by firewall on new server, otherwise new server begin receiving mail before shutting down the old server. After sync turn off old server, turn on postfix (unblock) on new server and delete old MX record.


Ludvik


S pozdravem

Ludvík Schmarcz
IT specialista

tel.: 777 726 780









--
--------------------------------------
---- Black Sun IT Services s.r.o. ----
--------------------------------------
-- computers - graphics - solutions --
--- networks - internet - intranet ---
--------------------------------------
------- http://www.blacksun.cz <http://www.blacksun.cz/> -------
--------------------------------------

> 14. 3. 2017 v 22:38, Olivier Boucard <olivier at pafostech.com>:
> 
> Hi Ludvik,
> 
> Thanks for the tips.
> I vaguely remember having some mandatory DNS, and reverse-DNS, setup to do before installing. Is it not anymore the case?
> 
> Olivier
> 
> On 2017-03-14 19:21, Ludvík Schmarcz wrote:
>> Hi Olivier,
>> 
>> 
>> In my experience, the best new installation, add users and use imapsync. If the servers are virtualized, downtime is tens of seconds (only change IP addresses behind the firewall after last syncronisation).
>> 
>> Ludvik
>> 
>> 
>> S pozdravem
>> 
>> Ludvík Schmarcz
>> IT specialista
>> 
>> tel.: 777 726 780
>> 
>> 
>> <PastedGraphic-1.tiff>
>> 
>> 
>> 
>> 
>> 
>> 
>> --
>> --------------------------------------
>> ---- Black Sun IT Services s.r.o. ----
>> --------------------------------------
>> -- computers - graphics - solutions --
>> --- networks - internet - intranet ---
>> --------------------------------------
>> ------- http://www.blacksun.cz <http://www.blacksun.cz/> -------
>> --------------------------------------
>> 
>>> 14. 3. 2017 v 16:37, Olivier Boucard <olivier at pafostech.com <mailto:olivier at pafostech.com>>:
>>> 
>>> Hi,
>>> 
>>> I have an old Kolab 3.3 running on an old CentOS 6. I would like to migrate to a new server running CentOS 7 with the latest Kolab.
>>> 
>>> What would be the steps (not in details just the overall process) to do such a migration with no service interruption (keeping the old server running)?
>>> Especially concerning the DNS configuration.
>>> 
>>> Thanks
>>> 
>>> Olivier Boucard
>>> 
>>> _______________________________________________
>>> users mailing list
>>> users at lists.kolab.org <mailto:users at lists.kolab.org>
>>> https://lists.kolab.org/mailman/listinfo/users <https://lists.kolab.org/mailman/listinfo/users>
> 
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20170314/80776bb3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-1.tiff
Type: image/tiff
Size: 44492 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20170314/80776bb3/attachment-0001.tiff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4342 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20170314/80776bb3/attachment-0001.p7s>


More information about the users mailing list