Service manual

Upgrading a Single Server
Chapter 2 Upgrading From Previous Versions 55
Although you may choose to reuse most of the configuration information supplied
for the original installation, do not reuse the existing port number. Instead, you
may change the port number of the new server after migrating existing data.
(4.x to 5.2) Handling Custom Schema
Thescript providedformigrating datarecognizes onlythose customschema either
placed in the standard
slapd.user_oc.conf and slapd.user_at.conf files, or
placed in other files and included in
slapd.conf usinguseroc and userat
directives. If, for example, custom schema are included directly in slapd.at.conf
or slapd.oc.conf, the migration script does not recognize them.
Perform the following steps before proceeding with the upgrade.
1. Compare slapd.at.conf or slapd.oc.conf with the standard files provided
under ServerRoot
/bin/slapd/install/version4/ of the new server,
transcribing custom schema elements to
slapd.user_oc.conf and
slapd.user_at.conf files.
If the custom object classes haveinheritance relationships, ensure that superior
object classes precede others in the schema configuration file.
2. If custom attributes were added to standard object classes in slapd.oc.conf,
create a new object class including the attributes in
slapd.user_oc.conf,and
add the new object class to every entry in the existing directory that uses the
custom attributes.
3. Include the slapd.user_oc.conf and slapd.user_at.conf files in the
slapd.conf file for the existing server using the useroc and userat directives,
placing the new directives adjacent to include statements for other files.
At this point, all custom schema used by the existing server should reside in
slapd.user_oc.conf or slapd.user_at.conf,andslapd.conf should include
the files using the
useroc and userat directives.
Migrating Existing Data
After handling custom schema, perform the following steps to migrate existing
data to a new server.