several ways to access a changelog
dsconf IDM-EXAMPLE-TEST replication dump-changelog -o ~/changelog.ldif
or use dbscan -f
doc ref
https://access.redhat.com/documentation/en-us/red_hat_directory_server/11/html/administration_guide/exporting-up-the-replication-changelog
15.15. EXPORTING THE REPLICATION CHANGELOG
15.15. EXPORTING THE REPLICATION CHANGELOG
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.
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 <david@bozemanpass.com> 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. IRetro 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 -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
No comments:
Post a Comment