Thursday, November 16, 2023

[389-users] Re: Documentation as to how replication works

several ways to access a changelog
dsconf IDM-EXAMPLE-TEST replication dump-changelog -o ~/changelog.ldif
or use dbscan -f
doc ref

the retro changelog is different, for example used for IPA DNS, via a dedicated plug-in, or can be used for migrations in a general purpose LDAP use case.

about the RUV records and values in the replication agreements:
this is a local view of what each replica thinks the other replicas know at a moment in time, a local private topology snapshot view, and those views are supposed to be all very close, or converge. if not, there can be chaos.
and more replication agreements = more processing when many updates are sent to various replicas.

On Thu, Nov 16, 2023 at 4:38 PM David Boreham <> wrote:

On Thu, Nov 16, 2023, at 5:17 PM, William Faulk wrote:

Since asking the question, I've been doing some research and found that the "cn=changelog" tree is populated by the "Retro Changelog Plugin", and on my systems, that has a config that limits it to the "cn=dns" subtree in my domain. I

Retro changelog is not the changelog you are looking for :)

The cn=changelog5,cn=config entry contains the on-disk location of the changelog where its saved as a Berkeley DB. It's almost as easy to pull the same data out of there.

You could do that. Also I noticed there is code to dump the changelog to a flat file, but it isn't clear to me how to call it : 

389-users mailing list --
To unsubscribe send an email to
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:

No comments:

Post a Comment