I'm not sure why you are tied to a three hour window. Can you import to a test server and then copy the database over via s file system copy?
On Saturday, June 13, 2015 at 2:16:52 PM, "Ezsra McDonald" <[email protected]> wrote: Having the server down for the initial import is not a problem. I am able to load 650 - 700 entries a minute. With almost 340k entries to import this will take too long. My estimate is approximate 8.5 hours. I tried breaking the import into four files and executing four ldapadds simultaneously but that does not improve the load rate. I really did not expect the import would be faster but I am desperate to get the migration done in less than three hours. This is just informational. I really don't expect there are any solutions to meet my desired 3 hour window. Thanks for the assistance. I will inform my team of my findings. On Fri, Jun 12, 2015 at 10:29 PM, Emmanuel Lécharny <[email protected]> wrote: > Le 12/06/15 23:18, Ezsra McDonald a écrit : > > The OpenLDAP ldapadd utility works. I wish there was a direct load kind > of > > utility like slapadd. Ldapadd is slow but studio is slower. > > Everything that inject data into a live server will be slow. > > In the near future, we will have a bulk import tool that will be way > faster, but it will require the server to be down. > > -- *Confidentiality Notice: The information contained in and transmitted with this communication is strictly confidential, is intended only for the use of the intended recipient, and is the property of Ginkgo LLC or its affiliates and subsidiaries. If you are not the intended recipient, you are hereby notified that any use of the information contained in or transmitted with the communication or dissemination, distribution, or copying of this communication is strictly prohibited by law. If you have received this communication in error, please immediately return this communication to the sender and delete the original message and any copy of it in your possession.*
