All of the reinitialization methods copy unnecessary data, for example data that contains values that were deleted or that maintain state information or other historical data. This unnecessary data makes the entry larger in disk. Also, the entry state information may need to be purged. If the root cause of the replication problem is related to this state information, the data is still present in the database and can cause another replication error. To avoid importing this unnecessary and potentially problematic data, you can do a clean reinitialization of your topology.
When you do a clean reinitialization, you create a clean master copy of the data that contains smaller databases, indexes, and empty change logs. A clean reinitialization uses less disk space and takes less time because it does not make backup copies of the database files. It also reduces index fragmentation, which can reduce performance. However, it requires you to stop the server that is being cloned to ensure that the database files are in a coherent state.
Stop the master server.
Export the database contents using the dsadm command.
Specify the -Q option so that replication information is not included in the export.
# dsadm export -Q instance-path suffix-DN /tmp/clean-export.ldif
Reimport the exported data to the same master server using the dsadm command.
# dsadm import instance-path /tmp/clean-export.ldif suffix-DN
Restart the master server.
The master server now contains clean data, meaning it contains smaller databases, indexes, and empty change logs.
Import the clean master data, to all of the other servers in your system.