Good morning,
I have been checking how could we manage for automating master -> slave and
slave->master transition. I though one possibility could be having both servers
configured in master mode with each being replicating to the other one. I know
this was some time ago unsupported and have
Thank you for your experience.
Best regards!
>Четверг, 13 сентября 2018, 19:26 +05:00 от Michael Menge
>:
>
>Quoting Evgeniy Kononov < egen...@inbox.ru >:
>
>> Hi!
>>
>> Thank you for reply.
>> Users can connect to only one server at a time. I move the master
>> server to another hardware and
Quoting Evgeniy Kononov :
Hi!
Thank you for reply.
Users can connect to only one server at a time. I move the master
server to another hardware and at this time it is necessary for
users to use the mail.
If this is not a secure configuration, then can I just run
"sync_client -A" from the
Hi!
Thank you for reply.
Users can connect to only one server at a time. I move the master server to
another hardware and at this time it is necessary for users to use the mail.
If this is not a secure configuration, then can I just run "sync_client -A"
from the master server, and then switch
Hi,
This setup is NOT SUPPORTED and WILL BREAK if the replication process
is triggered
from the wrong server (user is active on both servers, user switched
from one server
to the other while the sync-log file is still processed, after split
brain) and
some mailboxes have been subscribed,
Sorry! Previous message was sent by mistake.
For example, I can configure both servers as follows.
Server A.
-
/etc/cyrus.conf
START {
...
syncclient cmd="sync_client -r"
...
}
SERVICES {
...
syncserver cmd="sync_server" listen="csync"
...
}
/etc/imapd.conf
...
For example, on server A
--
Evgeniy Kononov
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
wait, but if I create a folder on the master, it perfectly syncs to the
replica. Also when I delete the folder on the master, it is also deleted on the
replica. It means that information about subscriptions to folders is
transmitted when synchronizing. but it works only if the client is the
master-master replication. Because of
CONDSTORE (https://tools.ietf.org/html/rfc4551) Cyrus is able
to handle messages on a master-master setup, but the information
about folder operations is not tracked and so cyrus is unable to
distinguish is a folder was subscribed on one server, or if a folder
Hello!
I have two servers with cyrus-imapd
cyrus-imapd-2.5.8-13.3.el7.centos.kolab_16.x86_64
One server as master and second as replica.
All worked fine when users login on master server, but when I temporary move
users on replica I found some trouble
Messages synchronisation from replica to
On 07/26/2017 04:54 PM, Michael Sofka wrote:
A while back there was some discussion of supporting Master-Master
replication in Cyrus. I'm busy updating from 2.4.17 to 3.0.2. What is
the state of Master-Master, as opposed to Master-Replica replications?
My current configuration is a Murder
A while back there was some discussion of supporting Master-Master
replication in Cyrus. I'm busy updating from 2.4.17 to 3.0.2. What is
the state of Master-Master, as opposed to Master-Replica replications?
My current configuration is a Murder cluster with three front-end
servers, two back
Is it possible to create master-master replication with cyrus, where the
same user always connects the same node? Are there any limitations?
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus
Hi, list
Currently I'm looking for mail solution for our company.
We need two syncronized imap-servers -- server1 on colocation (for
home, travelling users and several small additional offices) and
server2 in our main office (in general, it's internal corporate mail).
mailbox can be changed
14 matches
Mail list logo
