HP-UX Directory Server Release Notes Version B.08.10.01 - Updated 11/13/2009

improved compatibility with server applications that might misinterpret a Directory Server's
success response to bind operations that lack a password.
Account policy plug-in provides control over inactive accounts The new account policy
plug-in tracks login time stamps and provides the administrator with the option to lock
accounts based on the duration of inactivity since the last login time.
Replication agreements can be prioritized The multi-master replication plug-in has been
enhanced to allow prioritization of replication agreements. This allows the administrator to
control the order in which multiple replicas are updated. This may be useful, for example,
when you require that a backup master replica be updated completely before updating one
or more read-only replicas accessible by client applications.
3 Upgrade and migration notes
3.1 Upgrading from Red Hat Directory Server 8.0
When you upgrade from Red Hat Directory Server 8.0 to HP-UX Directory Server 8.1, the upgrade
script first saves any configuration files and data that need to be upgraded, storing them in the
archive file /var/opt/dirsrv/upgrade/8.0/cfgPreUpgradeBackup.tar. This archive
is created in addition to any backup that you created manually prior to the upgrade by following
the instructions in Section 6.2.1 (“Backing up the Directory Server data and configuration prior
to the upgrade”) of the HP-UX Directory Server installation guide.
3.2 Migrating from Netscape Directory Server 6.x
When migrating from Netscape Directory Server 6.11 or 6.21, you are moving from a 32-bit
architecture to the HP-UX Directory Server's 64-bit architecture. Therefore, you must use the
cross option (--cross) with the migration script. This option indicates that the migration is
across platforms.
As documented in the HP-UX Directory Server installation guide, the cross-platform migration
action takes database information exported to LDIF and imports LDIF data into the new 8.1
databases. Certain data is not migrated with cross-platform migrations, possibly causing an
adverse affect on replication. The following table lists the data that is not migrated and the impact,
if any:
Table 1 Data not migrated when using the cross option
ImpactData
The replicated topology must be in synch before starting
the migration; otherwise, consumer replicas must be
reinitialized after migration.
Replica nsState attribute
Changelogs
No effect
nsslapd-idl-switch attribute
Creates the possibility that a non-unique nsUniqueId
value could be generated. This is unlikely because of the
algorithm used for generating unique IDs.
The unique ID generator entry, cn=uniqueid
generator,cn=config
For more information on these attributes, see the HP-UX Directory Server configuration, command,
and file reference.
3 Upgrade and migration notes 7