Re: Syncrepl vs. replication

[Ralf Haferkamp <rhafer@suse.de>]

On Wednesday 01 June 2005 17:01, matthew sporleder wrote:
> Wouldn't this require at least one back-dbd/back-hdb server to be
> configured?  Or am I misunderstanding the second part of this
> statement (from the 2.2 admin guide):
>
> While slapd (8) can function as the LDAP Sync provider only when it
> is configured with either back-bdb or back-hdb backend, the syncrepl
> engine, which is a consumer-side replication engine, can work with
> any backends.
>
> I read this to mean the "master", which provides the info for
> syncing, must run one of those backends?
This is true of version 2.2. But the syncrepl provider code for the 2.3 
release has be completely rewritten as an overlay. That can also be 
used with other backends. From the 2.3 admin guide 
(http://www.openldap.org/doc/admin23/syncrepl.html):

"... The syncrepl engine, which is a consumer-side replication engine, 
can work with any backends. The LDAP Sync provider can be configured as 
an overlay on any backend, but works best with the back-bdb or back-hdb 
backend. The provider can not support refreshAndPersist mode on 
back-ldbm due to limits in that backend's locking architecture. ..."

> > The slurpd replication mechanism probably ran out of steam a long
> > time ago. I'm on the verge of completely replacing it with syncrepl
> > in 2.3, as slurpd itself is not viable in the dynamic config
> > environment.

-- 
Ralf Haferkamp
SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg
T: +49-911-74053-0
F: +49-911-74053575 - Ralf.Haferkamp@suse.com