On 2/13/2013 9:22 PM, Sam Varshavchik wrote:
> David Pearce writes:
>
>> Can someone point me to a description of what it takes to move a Coutier
>> install from one server to another server? I know about the IP/DNS side of
>> things, but how do I move everything else.
> Well, what's everything else would be, in your case? As far as the server's
> configuration, if both servers used the same exact configuration for the
> Courier installation, and by that I mean both the installation directories
> or package, and the user and group ID for Courier, then moving
> ${sysconfdir}, which would be /etc/courier or /usr/lib/courier/etc,
> verbatim, will be sufficient. Care must be used to preserve the ownership
> and permissions of each file and subdirectory in there.
Set up the new server exactly like the old server and then copy all the
config files over. If I'm building a newer version or there are any
differences in the setup, I will copy the old config files into a
separate directory and then use "vim -d" to compare differences between
the old and new configs and copy over the relevant information into the
new config files.
> This will result in both servers, in most configurations, using the same
> hostname/servername as their own name, which is probably ok. In other
> situations where the server configuration defaults to the system hostname,
> this won't be the case, but since the aliases file depends on the system
> hostname, it will be necessary to rerun makealiases, and that's about it.
>
> As far as moving maildirs, rsyncing will be sufficient for them, again,
> taking care to preserve file permissions.
Once you have the new server configured properly, run rsync on the
maildirs to copy them to the new server. You can do this while the old
server is still running to copy over the bulk of the data. Once that is
done, shut down Courier on the old server, run rsync on the maildirs
again (this should not take very long since it only has to copy over
changes since the first rsync), start up Courier on the new server and
make the necessary network changes.
In my case, I simply changed the NAT config in my router to send traffic
to the new server. The local IPs are different, but the external IP and
the DNS did not change, so there was no delay. If you are changing DNS
records, it will be more complicated. You may want to set the DNS
record to a very low TTL a day or so prior to the migration to minimize
the delay.
> This won't move mail that's in the server's queue and hasn't been delivered,
> so your migration plan would involve keeping the old server running for a
> while, to flush out its outgoing mail.
Just make sure not to allow any incoming connections to the old server
while this is happening (smtp, pop, imap, or webmail). You don't want
any new messages coming in or user connections to the old server.
--
Bowie
--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
