Re: Migrating Netscape DS to FDS

[Dave <dave@xxxxxxxxxxxx>]

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:
> 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.
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>   

--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users