Ondřej, Tanks for explaining. I must admit that I was happy go get syncrepl working many years ago. For delta-syncrepl I had thought the combination of accesslog (write changes) on the source database and logbase in syncrepl (read changes) were enough. I must admin that I still didn't quite understand the relationship between refreshAndPersist and the delta-syncrepl; somehow I thought refreshAndPersist is a fall-back whenever delta-syncrepl fails (for watever reasons). So I need a syncprov on the original database for refreshAndPersist, and one for the accesslog used by delta-syncrepl? And the syncprov is actually a trigger for database changes?
Kind regards, Ulrich Windl > -----Original Message----- > From: Ondřej Kuzník <on...@mistotebe.net> > Sent: Friday, March 21, 2025 12:28 PM > To: Windl, Ulrich <u.wi...@ukr.de> > Cc: openldap-technical@openldap.org > Subject: [EXT] Re: Notes on > https://kb.symas.com/en_US/configuration/configure-delta-syncrepl > > On Fri, Mar 21, 2025 at 06:07:41AM +0000, Windl, Ulrich wrote: > > Hi! > > > > Reading > > https://kb.symas.com/en_US/configuration/configure-delta-syncrepl > > I found some issues: > > Hi Ulrich, > I don't think a project mailing list is the right forum to request > changes to a non-project resource. Indeed that page seems to have a > "Give feedback" feature. > > > Also for MMR there is a syncprov defined for the database to sync and > > the accesslog for that database. Why is syncprov for accesslog needed? > > If you're asking why that's needed, read up on how deltasync works and > it will generally become self-evident. In short, the accesslog DB *is* > the source of changes once the "delta" part kicks in. > > Regards, > > -- > Ondřej Kuzník > Senior Software Engineer > Symas Corporation http://www.symas.com > Packaged, certified, and supported LDAP solutions powered by OpenLDAP
