If you want a full sync, I'd export and import, then "delta sync". Reason: The change messages will be quite a lot and the performance is non-optimal. Also the server may answer while it's not up to date. Why do you want a full sync?
Kind regards, Ulrich Windl
-----Original Message----- From: Brendan Kearney bpk678@gmail.com Sent: Wednesday, December 17, 2025 3:18 PM To: openldap-technical@openldap.org Subject: [EXT] Migrating HA Cluster, Want to Force Full Replication
Sicherheits-Hinweis: Diese E-Mail wurde von einer Person außerhalb des UKR gesendet. Seien Sie vorsichtig vor gefälschten Absendern, wenn Sie auf Links klicken, Anhänge öffnen oder weitere Aktionen ausführen, bevor Sie die Echtheit überprüft haben.
List members,
I plan on updating my 3 node multi-primary instances and want to have a full resync done when each instance is rebuilt and rejoined to the cluster. Currently, I have both config and DIT fully replicated between all instances. When I rebuild each node, it will have all of the configs in place to be a part of the cluster. What I would like to have is all the data pushed to the newly built, but empty, instance.
I have a process that is somewhat brute force, where all data is exported, stripped of entryCSN and contextCSN values, then added back to the newly built instance. This would require that the other instances be stopped or otherwise not take any updates during the transition. I would like to avoid this disruption in service, if at all possible.
Is there a way to have a full resync done when a rebuilt instance that has no data rejoins a cluster?
Thanks in advance,
Brendan Kearney