2006/11/6, Aaron Richton &lt;<a href="mailto:richton@nbcs.rutgers.edu">richton@nbcs.rutgers.edu</a>&gt;:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
&gt; Do the slapadd tool keep the operational attributes values ?<br><br>It does not. See the slapadd man page.</blockquote><div><br>So the migration process&nbsp; bring you to a new directory, not a copy of the previous one. And if some LDAP application use the entryUUID attribute to refer to the users (in order to prevent problems when renaming a user), it does not work anymore after the migration. Am I right ? Is there still this problem in OpenLDAP 
2.3 ?<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">&gt; If we try and copy the database, shall we see instantly if there is a
<br>&gt; problem, or can it occur at any time ?<br><br>slapadd has very little error checking versus adding through slapd. The<br>restrictions are detailed in the slapadd man page. If you feed slapadd<br>invalid data, but not so grossly invalid that slapadd errors out, it is
<br>quite possible that lingering effects (missing parents, schema violations,<br>etc.) will &quot;occur at any time&quot; in the future. You basically want your data<br>to be clean enough for ldapadd, whether you use slapadd or not.
</blockquote><div><br>Ok, but I was speaking of the first way (copying the database files). Do the problems occurs immediately or not ?<br>&nbsp;<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
By the way, if you're going to be migrating anyway, you really don't want<br>to migrate from 2.2 to 2.2. Try the latest version of 2.3 available at<br><a href="http://www.openldap.org">www.openldap.org</a>.<br></blockquote>
</div><br><br>Of course, but in this project I am working with a customer who is changing its platform and I am not responsible of the migration process at all (actually I am supporting an application using the directory).
<br>