Argh, I figured out this problem was self-inflicted. I used too old a revision of the dse.ldif file as the basis for my migration. Updating to a newer revision (that included references to the missing backend) solved the problem. Thanks for the help and sorry to have wasted time with this. Jeff > -----Original Message----- > From: Jeff Tharp > Sent: Tuesday, January 29, 2008 2:40 PM > To: 'Fedora-directory-users@xxxxxxxxxx' > Subject: Migrating from 1.0.2 to 1.1, not all databases migrated > > I'm working on migrating our Fedora DS 1.0.2 server to > FedoraDS 1.1. I did a same platform migration on test box by > installing the FedoraDS 1.1 binaries, taring up > /opt/fedora-ds from one of our old FedoraDS boxes and then > using migrate-ds-admin.pl to migrate the instance. While > NetscapeRoot and UserRoot were migrated correctly, the > mgration script skipped over our custom database entirely. > Now I can always export to LDIF and migrate this database > that way, I was hoping to do a direct binary migration to > minimize downtime. Are UserRoot and NetscapeRoot the only > databases supported, or is it likely that something was > misconfigured with my test? > > Any advice is appreciated, > Jeff Tharp > System Administrator > ESRI - Redlands, CA > http://www.esri.com -- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
