--On Wednesday, April 7, 2021 8:02 PM +0000 [email protected] wrote:
Hello, I am setting up n-way multi-provider replication. Should we expect a full sync when we setup sync for the first time on a new provider? Can we load a backup data.mdb file first and have deltasync run from there to prevent a full sync (i.e. to save time)? What is the expected behavior/best practice?
Given the known issues in standard syncrepl it is ill advised to do a full sync. Additionaly it's a waste of time. ;)
The best practice is to either pre-load the DB via slapadd or provide it a binary copy of the db from mdb_copy -c.
Also, I have some questions around mdb_copy. Is there any concern using the -c flag for compacting the data.mdb file to be used for restore (or new n-way provider if that works)? I notice the compacted file is smaller on disk than the original data.mdb (due to the removed freed pages). I assume the data sets are still the same? Are there tools to compare the two?
You should use mdb_copy -c. All it does is de-fragment the database as much as possible.
And last question, I am using mdb_copy to create a backup but standard linux cp to put the new file into /var/lib/ldap/data.mdb. Will this cause any issues or is it recommended to use mdb_copy to also move the data.mdb file into place?
You can just use cp after you've made the initial copy. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>
