Robert Mueller wrote:
1. Server A is master (sync_client) replicating to Server B (sync_server)
I'd like to add replication to my server as well. Is this replication
possible in Cyrus 2.2.13? Is this [1] what you are talking about (merged
into Cyrus 2.3 as stated in that page)? Or are you using
On Thu, 13 Jul 2006, Robert Mueller wrote:
I think that should do it. There might be another option as well to make
this easier. From the top:
1. Server A is master (sync_client) replicating to Server B (sync_server)
2. Server A dies/is stopped
3. Restart Server B after adding this to the
Title: Cyrus 2.3.7 Replication Question
I would like to set up replication between two Cyrus servers A and B.
Server A will replicate to server B and Server B will replicate to server A.
For half of the subscribers we have the proxy point to server A, the other half of
the subscribers
I would like to set up replication between two Cyrus servers A and B.
Server A will replicate to server B and Server B will replicate to
server A.
[...]
Will this work in Cyrus 2.3.7?
It won't. Cyrus currently only supports unidirectional replication.
Baltasar
_ former 03 gmbh
_
It won't. Cyrus currently only supports unidirectional replication.
You can make it work (we do), but you need 2 separate instances of cyrus on
each machine, which basically means 2 start/stop scripts, 2 different
ports/ips for each service, 2 imapd.confs, 2 cyrus.confs, and lots of -C
On Thu, 2006-07-13 at 07:58 +1000, Robert Mueller wrote:
It won't. Cyrus currently only supports unidirectional replication.
You can make it work (we do), but you need 2 separate instances of cyrus on
each machine, which basically means 2 start/stop scripts, 2 different
ports/ips for each
You can make it work (we do), but you need 2 separate instances of cyrus
on
each machine, which basically means 2 start/stop scripts, 2 different
ports/ips for each service, 2 imapd.confs, 2 cyrus.confs, and lots of -C
command line params to everything so it uses the right conf file.
to avoid
Robert Mueller wrote:
You can make it work (we do), but you need 2 separate instances of
cyrus on each machine, which basically means 2 start/stop scripts, 2
different ports/ips for each service, 2 imapd.confs, 2 cyrus.confs,
and lots of -C command line params to everything so it uses the
Robert Mueller wrote:
1) Server A dies
2) Users are sent to Server B via DNS redirects
3) Server A is restored
4) Mailboxes on Server B are now more 'current' than mailboxes on
Server A
In other words, the failover is easy(ish) but the failback has me
scratching my head. I Think two way
Can you detail this A - B replication setup more? I've been trying to
figure out how to make use of the new 2.3.7 replication features outside
of a murder. The thing I can't wrap my head around is the following
situation:
1) Server A dies
2) Users are sent to Server B via DNS redirects
3)
Interesting. This process also implies you want to stop incoming mail
for a period of time to both servers. Sound right?
I would say the process for failover is:
1. Server A is master (sync_client) replicating to Server B (sync_server)
2. Server A dies/is stopped
3. All IMAP/POP/LMTP
, July 12, 2006 5:59 PM
To: former03 | Baltasar Cevc; Esh, Thomas D (Tom);
info-cyrus@lists.andrew.cmu.edu
Subject: Re: Cyrus 2.3.7 Replication Question
It won't. Cyrus currently only supports unidirectional replication.
You can make it work (we do), but you need 2 separate
instances of cyrus
12 matches
Mail list logo
