On 03/19/2015 11:24 AM, Lucio Crusca wrote:
> Hello all,
>
> I have a production courier-mta server (along with imap and pop) with a
> number
> of domains and mailboxes, authentication through userdb. It's a old Debian
> GNU/Linux 6.0 server with packaged courier-mta 0.65. I plan to migrate it to
> a
> new server with Debian GNU/Linux 8.0 and packaged courier-mta 0.73.
>
> What's the best live migration path that ensures no messages are lost in the
> move? My idea is:
>
> 1. Install new server & configure all domains & accounts
> 2. Make old server send a copy of incoming messages to the new server
> 3. manually copy old messages
> 4. switch DNS records & wait propagation
> 5. shutdown old server
>
> Assuming my idea makes sense, what's the simplest way to configure
> courier-mta
> for point 2?
I did this kind of migration a few times, so it was something like that:
1. set DNS propagation time to minimum
2. as 1. above
3. rsync imap files / email messages to new server
4. test setup on new server
5. disable daemons on old server
6. rsync again
7. switch DNS
8. reverse 1.
You might also do something about Courier queues.
No guarantees, just suggestions :-).
Regards
Racke
--
Modern Perl, Dancer and eCommerce consulting.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
