Hello!
Folks, looking through maillist history i saw that many of you are
running cyrus in rolling replication mode. I am interested in
configuring cyrus replica to use as a standby imap server, where we can
switch DNS in case of problems with primary backend. While testing on
On Mon, Aug 09, 2010 at 08:15:36PM +0400, Dmitry Ivanov wrote:
Hello!
Folks, looking through maillist history i saw that many of you are
running cyrus in rolling replication mode. I am interested in
configuring cyrus replica to use as a standby imap server, where we can
switch DNS in
On Thu, May 10, 2007 at 12:14:44PM -0400, Nik Conwell wrote:
Do you have separate IP addresses for each instance of cyrus on the
machine as well, or just the machine itself? If just the machine,
what 'names' does the front-end know the back-end instances by?
Every store has an IP address
On Jan 18, 2007, at 5:35 PM, Rob Mueller wrote:
Attached is our operation group's notes on the subject. It makes
reference to the tool we use to manage the OS of the machines
(radmind), but it should be pretty clear what they are talking about
without any radmind knowledge.
As an FYI, we
Hi!
Is there documentation abt replication failover scenarios anywhere? I
can, of course, conjure up a thing or two, but I'd like to see how other
people have resolved 'corrupted mailspool - services to the replica -
maintenance - resync master - services back to the master' situations.
I did
On 18 Jan 2007, at 05:41, Janne Peltonen wrote:
Is there documentation abt replication failover scenarios anywhere? I
can, of course, conjure up a thing or two, but I'd like to see how
other
people have resolved 'corrupted mailspool - services to the
replica -
maintenance - resync master
Attached is our operation group's notes on the subject. It makes
reference to the tool we use to manage the OS of the machines
(radmind), but it should be pretty clear what they are talking about
without any radmind knowledge.
As an FYI, we have a similar procedure to this, the main
