<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 08/21/2015 02:58 AM, Michael Menge wrote:<br>
<blockquote
cite="mid:20150821095851.Horde.1v5xZHaNpbpZns6grhb3D6e@webmail.uni-tuebingen.de"
type="cite">Hi,
<br>
<br>
<br>
Quoting Nic Bernstein <a class="moz-txt-link-rfc2396E" href="mailto:nic@onlight.com"><nic@onlight.com></a>:
<br>
<snip><br>
<blockquote type="cite">I can write this up, I just wasn't sure if
it was still needed. I put a big ol' Note: in the replication
page saying:
<br>
<br>
Important
<br>
<br>
Within a Cyrus /Murder/
<br>
<a class="moz-txt-link-rfc2396E" href="https://docs.cyrus.foundation/imap/developer/architecture.html#architecture-murder"><https://docs.cyrus.foundation/imap/developer/architecture.html#architecture-murder></a><br>
environment, replicas must *not* be configured to invoke
<br>
ctl_mboxlist(8)
<br>
<a class="moz-txt-link-rfc2396E" href="http://docs.cyrus.foundation/imap/admin/commands/ctl_mboxlist.html"><http://docs.cyrus.foundation/imap/admin/commands/ctl_mboxlist.html></a><br>
on startup (pushing the local mailbox list to the *Mupdate
Master*).
<br>
This may only be done on the Master instance.
<br>
<br>
That's the only real gotcha I know of, but, having said that, I
did write up a brief set of instructions about this very topic
not that long ago (IIRC) for user mailing list. I figured I
could start with that.
<br>
<br>
</blockquote>
<br>
<br>
For the initial configuration I second this. But there are IHMO
things
<br>
to consider on failover.
<br>
<br>
<br>
1. ctl_mboxlist must be used with -m and -a Option on failover
<br>
2. on big installations updating all entries in mailbox.db on the
<br>
mupdate server can take some time, on our setup we switch the
IP address
<br>
of master and replic on failover
<br>
</blockquote>
<br>
And on 21 August at 06:12AM CDT, Ken Murchison wrote:<br>
<blockquote type="cite"> Right. We don't even have our replicas as
part of our Murder. They replicate their backend as if it were a
standalone server.</blockquote>
<br>
<br>
Yes indeed. We use the following in /etc/imapd.conf on our servers:<br>
<blockquote>
<pre>##
# Only one of these should be uncommented
@include: /etc/imapd-master.conf
#@include: /etc/imapd-replica.conf
</pre>
</blockquote>
And then comment/uncomment as needed. The difference between these
being the following (sanitized for your protection):<br>
<blockquote>
<pre>root@<a class="moz-txt-link-freetext" href="mailbox:~#">mailbox:~#</a> diff -uwb /etc/imapd-master.conf /etc/imapd-replica.conf
<font color="#009900">--- /etc/imapd-master.conf 2014-11-24 23:06:49.830675999 +0000</font>
<font color="#993399">+++ /etc/imapd-replica.conf 2014-11-24 23:06:49.834675999 +0000</font>
<font color="#009900">-servername: mailbox.example.com</font>
<font color="#993399">+servername: mailbox.wi.example.com
</font>
<font color="#009900">-##
-# Auth credentials
-mupdate_server: postman.example.com
-mupdate_username: postman
-mupdate_authname: postman
-mupdate_password: <secret>
-
-##
-# Replication support
-# This is how the BACKEND for this host is defined
-sync_host: mailbox.ia.example.com
-sync_authname: mailproxy
-sync_password: <secret>
-sync_compress: true
-sync_log: true
-sync_repeat_interval: 5
-sync_shutdown_file: /var/run/cyrus/sync_stop</font>
<font color="#993399">+## Auth credentials
+# The credentials below must match the account listed in lmtp_admins
+# on the backend servers.
+proxy_authname: mailproxy
+proxy_password: <secret>
+serverlist: mailbox mailbox.wi</font>
</pre>
</blockquote>
So the replica has no clue about the Murder. We switch DNS between
the two hosts during failover, so no IP address change [the servers
are in different data centers, so that wouldn't be practical in any
event]. I doubt we actually need that last blob of stuff on the
replica, but it doesn't seem to have hurt.<br>
<br>
As for /etc/cyrus.conf, we do something similar, in regards to
commenting/uncommenting START entries for ctl_mboxlist and
sync_client, versus an SERVICES entry for sync_server.<br>
<br>
It's not the cleanest process in failover, but a damn sight better
than nothing.<br>
<br>
Cheers,<br>
-nic<br>
<pre class="moz-signature" cols="72">--
Nic Bernstein <a class="moz-txt-link-abbreviated" href="mailto:nic@onlight.com">nic@onlight.com</a>
Onlight, Inc. <a class="moz-txt-link-abbreviated" href="http://www.onlight.com">www.onlight.com</a>
6525 W Bluemound Road, Suite 24 v. 414.272.4477
Milwaukee, Wisconsin 53213-4073
</pre>
</body>
</html>