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

canonical way to force full refresh in 2.4.28 / n-way multimaster



I’m preparing to rollout 2.4.28 with n-way multimaster (in this case, it’s really 2-way multimaster but could become more), and I’m looking to clarify what the exact canonical way to force a full refresh.  Here’s what I’ve come up with:


By “full refresh” I mean, blow away whatever is on machine Y with whatever’s on machine X.


olcServerID: 1 ldaps://animal.clarku.edu

olcServerID: 2 ldaps://zoot.clarku.edu


olcSyncrepl: {0}rid=001 provider=ldaps://animal.clarku.edu binddn="DN OF REPLICATION USER" bindmethod=simple credentials=<PASSWORD> searchbase="dc=clarku,dc=edu" type=refreshAndPersist retry="5 5 300 5" timeout=1

olcSyncrepl: {1}rid=002 provider=ldaps://zoot.clarku.edu binddn="DN OF REPLICATION USER " bindmethod=simple credentials=<PASSWORD>  searchbase="dc=clarku,dc=edu" type=refreshAndPersist retry="5 5 300 5" timeout=1


1.       Stop slapd on zoot.

2.       slapcat > ocrap-backup.ldif

3.       rm –rf /var/lib/ldap/* on zoot

4.       SLAPD_OPTIONS=”-c \”rid=001,sid=001\”” /etc/init.d/slapd start


Then wait and it will refresh.


Is this correct? Is there some easier way?  Is there a way to do it without the rm –rf ?  After it’s done, do I need to restart slapd again without the –c option?


Thanks, and if I’m doing something stupid, I’m happy to look stupid in exchange for knowledge. J





Aaron Bennett

Manager of Systems Administration

Clark University ITS