HP-UX Directory Server B.08.10.02 Release Notes (5900-0842, May 2010)

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 Sun Java System Directory Server
HP-UX Directory Server shares a common heritage with Sun Java System Directory Server (SJDS)
and has almost identical features and capabilities. This helps provide SJDS consumers a smooth
transition from their product to the HP-UX Directory Server, the latter which provides a stable
platform that is based on current industry standards and is supportable for the long term. To
make the transition even easier, HP now provides the sjdsmig.pl script with the HP-UX
Directory Server software (in /opt/dirsrv/contrib). This script facilitates migrating data
from SJDS.
3.3 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.
NOTE: If a supplier or hub is not fully synchronized with its consumers at the time of migration,
you must reinitialize all its consumers after migration.
4 Known problems fixed in this release (B.08.10.02)
Table 2 Fixes in the latest release of HP-UX Directory Server (B.08.10.02)
Description of corrected problemDefect
The log rotationinfo file is corrupted at startup. As a result, log files that were created
before the restart are not removed after they expire.
QXCR1000977427
8