[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: 3 database multimaster



Thanks Alvin

I have a couple of remaining questions

When svr1 is updated and replicates across to svr2 and svr3, what stops svr3 from then replicating to svr2 and svr2 replicating across to svr3?
Do the slave updates not get replicated further because the replicated update retains the modifyUser of svr2 and svr3 respectively?


Why do you use two replogfile directives per database?
Is there some magic I'm missing here?

Regards
Don

Alvin Wong wrote:

I do it as follows:

In Server 1's slapd.conf:
updatedn "cn=Svr1,o=someorg"

# Replication
replica host=Svr2:389
	    binddn="cn=Svr2,o=someorg"
	    bindmethod=simple credentials=passwd
replogfile "C:/ldap/database/rep.log"

replica host=Svr3:389
	    binddn="cn=Svr3,o=someorg"
	    bindmethod=simple credentials=passwd
replogfile "C:/ldap/database/rep.log"

In Server 2's slapd.conf:
updatedn "cn=Svr2,o=someorg"

# Replication
replica host=Svr1:389
	    binddn="cn=Svr1,o=someorg"
	    bindmethod=simple credentials=passwd
replogfile "C:/ldap/database/rep.log"

replica host=Svr3:389
	    binddn="cn=Svr3,o=someorg"
	    bindmethod=simple credentials=passwd
replogfile "C:/ldap/database/rep.log"

In Server 3's slapd.conf:
updatedn "cn=Svr3,o=someorg"

# Replication
replica host=Svr1:389
	    binddn="cn=Svr1,o=someorg"
	    bindmethod=simple credentials=passwd
replogfile "C:/ldap/database/rep.log"

replica host=Svr2:389
	    binddn="cn=Svr2,o=someorg"
	    bindmethod=simple credentials=passwd
replogfile "C:/ldap/database/rep.log"


-----Original Message----- From: Don McPhee [mailto:don@donmcphee.com] Sent: Monday, December 13, 2004 7:33 AM To: openldap-software@OpenLDAP.org Subject: 3 database multimaster


Hi

Has anyone ever setup a three database multimaster system?

All examples and documentation I've found refer to two system multimastering (and there aren't many of them!)

I'm trying to create a system where I have two slaves and one master, most changes are made to the master and replicated to the slaves, but any updates to the
slaves need to be replicated back to the master and back down to the other slave from time to time.


Any suggestions would be much appreciated.

The problem I have here is that you can't have multiple updatedn directives in slapd.conf, otherwise I'd use the following.

<slapd.conf.0>
replica host=host1:389
  binddn="cn=REPLICATOR0,o=someorg"
  bindmethod=simple credentials=passwd

replica host=host2:389
  binddn="cn=REPLICATOR0,o=someorg"
  bindmethod=simple credentials=passwd

updatedn cn=REPLICATOR1,o=someorg
updatedn cn=REPLICATOR2,o=someorg
</slapd.conf.0>

<slapd.conf.1>
replica host=host0:389
  binddn="cn=REPLICATOR1,o=someorg"
  bindmethod=simple credentials=passwd

replica host=host2:389
  binddn="cn=REPLICATOR1,o=someorg"
  bindmethod=simple credentials=passwd

updatedn cn=REPLICATOR0,o=someorg
updatedn cn=REPLICATOR2,o=someorg
</slapd.conf.1>

<slapd.conf.2>
replica host=host0:389
  binddn="cn=REPLICATOR2,o=someorg"
  bindmethod=simple credentials=passwd

replica host=host1:389
  binddn="cn=REPLICATOR2,o=someorg"
  bindmethod=simple credentials=passwd

updatedn cn=REPLICATOR0,o=someorg
updatedn cn=REPLICATOR1,o=someorg
</slapd.conf.2>

Cheers
Don