[Dovecot] Dovecot Replication setup
Hi,
I am trying to setup a master/master replication with dsync (according to the first part of: http://wiki2.dovecot.org/Replication).
Sorry if this question sounds foolish, but I would like to ask/confirm whether the indicated setup is required on *both* servers participating in the master/master replication. It seems to me that both need it, but I would like to confirm, just in case.
Both servers are running 2.2.12 on CentOS x86_64 (5.10 and 6.5 respectively) and users are virtual over ldap.
I might have more questions in the near future, but this is a starting point.
Please clarify.
Best regards, Nick
On 26/3/2014 1:30 μμ, Nikolaos Milas wrote:
I am trying to setup a master/master replication with dsync (according to the first part of: http://wiki2.dovecot.org/Replication).
...I would like to ask/confirm whether the indicated setup is required on *both*servers participating in the master/master replication.
Anyone?
If users are going to be able to access any of the two masters directly, and changes will therefore need to propagate on both directions (depending on the point of access), do we need to configure both servers for replication (as above), or doing so will end up in an undesired loop?
Please clarify.
Thanks, Nick
On 28/3/2014 12:17 πμ, Nikolaos Milas wrote:
On 26/3/2014 1:30 μμ, Nikolaos Milas wrote:
I am trying to setup a master/master replication with dsync (according to the first part of: http://wiki2.dovecot.org/Replication).
...I would like to ask/confirm whether the indicated setup is required on *both*servers participating in the master/master replication.
Answering my own question (after our test deployment), I can tell now that it is enough to set up the main server with the replication configuration.
I don't know if setting up the second master (the mirrored one) with replication config as well would cause conflicts/loops/issues.
Nick
On 31/3/2014 1:15 μμ, Nikolaos Milas wrote:
I am trying to setup a master/master replication with dsync (according to the first part of: http://wiki2.dovecot.org/Replication).
...I would like to ask/confirm whether the indicated setup is required on *both*servers participating in the master/master replication.
Answering my own question (after our test deployment), I can tell now that it is enough to set up the main server with the replication configuration.
I don't know if setting up the second master (the mirrored one) with replication config as well would cause conflicts/loops/issues.
After further testing, I can now say that I was wrong; Both masters must be configured for replication to have proper two way sync.
I wish someone -with earlier experience- would answer these questions, to help us avoid all this fuss....
Nick
On 04/17/2014 03:05 PM, Nikolaos Milas wrote:
After further testing, I can now say that I was wrong; Both masters must be configured for replication to have proper two way sync.
I wish someone -with earlier experience- would answer these questions, to help us avoid all this fuss.... I regret that I did not spot the error in your configuration and Im sorry nobody else was able to answer you either. The dsync feature (as it is used since v2.2) is one where perhaps not so many have a lot of production environment experience. I hope you will have an easier time from now on.
br, Teemu Huovila
On 17 April 2014 14:31, Teemu Huovila <teemu.huovila@dovecot.fi> wrote:
I wish someone -with earlier experience- would answer these questions, to help us avoid all this fuss.... I regret that I did not spot the error in your configuration and Im sorry nobody else was able to answer you either. The dsync feature (as it is used since v2.2) is one where perhaps not so many have a lot of production environment experience. I hope you will have an easier time from now on.
I struggled getting any information together on getting replication set up. It took a while, but finally I got there.
I have to say, once set up it has been very robust and reliable. To know that our production mails are replicated to an offsite system over a VPN is very comforting. Why more people aren't using this I don't know... it has been brilliant.
Thanks as always to Timo for putting together a brilliant product.
-Mark
participants (3)
-
IT geek 31
-
Nikolaos Milas
-
Teemu Huovila