[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Copying database files from one platform to another

2006/11/6, Aaron Richton <richton@nbcs.rutgers.edu>:
> Do the slapadd tool keep the operational attributes values ?

It does not. See the slapadd man page.

So the migration process  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 ?

> If we try and copy the database, shall we see instantly if there is a
> problem, or can it occur at any time ?

slapadd has very little error checking versus adding through slapd. The
restrictions are detailed in the slapadd man page. If you feed slapadd
invalid data, but not so grossly invalid that slapadd errors out, it is
quite possible that lingering effects (missing parents, schema violations,
etc.) will "occur at any time" in the future. You basically want your data
to be clean enough for ldapadd, whether you use slapadd or not.

Ok, but I was speaking of the first way (copying the database files). Do the problems occurs immediately or not ?
By the way, if you're going to be migrating anyway, you really don't want
to migrate from 2.2 to 2.2. Try the latest version of 2.3 available at

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).