I think you will find the most trouble in o=NetscapeRoot. More than likely you will have to recreate acls, roles, replication agreements, etc. by hand. I'm sure the data in o=UserRoot will not be a big deal. You just have to keep in mind that schemas may have varied slightly. Certificates and keys will have to be imported/exported to the new server also. In all, i think you can go from Netscape 4.1 -> FDS 1.1.3 manually if you are well prepared. You can always bring up a cloned instance of Netscape 4.1 and try the step upgrade. solarflow99 wrote: -- Marcelo Nicolás Halpern Systems Administrator Accoona Corporation T: +1-201-377-3424 B: +1-201-850-3135 aim:mnhxacna y!:mnhxacna msn:mnhxacna@hotmail.com

Everyone here hit on the main points. The products are made from the same code base so usually you only face minor schema changes. If you directory is small you can usually use the ldapsearch and ldapmodify command line tools. Some entire corporate directories are less then 4000 entries and export in less then a second. They import in less then 1 minute. I suggest exporting the data using an ldapsearch and try to load it on a fresh system using ldapmodify/add. The tools will stop on a schema violation and you investigate why that particular object did not load. What you are facing now is similar to a situation you may face with an upgrade from mysql 3.0 upgrade to mysql 5.0. It might be hard to find an upgrade path from vendor documentation, but a plain old mysqldump/mysqlimport will likely work. As mentioned you may have to specifically deal with acls, roles, replication agreements- but you would likely want to add those by hand so you can audit them in the process.

Hey everybody thanks for all the responses. I am new to this (if you couldn't tell), but this is a relatively small directory installation of about 500 people in the database. There is also iPlanet messaging server, app server, and web server installed, but job is to migrate off those platforms onto open source so I am not too concerned about the config schema for those services. With respect to exporting/import an LDIF file, yes there are about 20 custom fields in the schema for varying types of data such as user preferences. This is one reason I was trying to avoid an import/export of LDIF as it would require some cleansing. The challenge of doing the step-upgrade now appears to be in finding version 6 iPlanet Directory Server to download somewhere... By the way, f anyone is willing to take a crack at this I'd be more than happy to compensate... I have a Red Hat test server set up with fedora-ds installed and an LDIF file containing a dump of the Netscape DS 4.1 server. About Ed's comment about MySQL: I've never had so much trouble with SQL files as much as LDIF files... don't SQL files usually have the data and schema right in the same file so everything can be done on a single import without much need for cleansing? Thanks again -Dave Edward Capriolo wrote:

OK exporting/importing the LDIF worked, but I had to do some sleuth work to determine the custom objects and attributes in the slapd.user_oc.conf slapd.user_at.conf respectively, then manually create these in the new server using the same object and attribute types. I suppose this is what the migration scripts would have done in version 6.0... not sure why they couldn't do the same work in version 8.0. They build this software to last decades, but we're supposed to discard it after a few years when the support discontinues? good grief. Thanks again to all who chimed in. cheers -Dave Michael Ströder wrote: