Installation guide

be removed.
5.3.4. Moving from Solaris to Red Hat Enterprise Linux
The upgrade process is largely similar when migrating from an 8.2 instance on Solaris to a 9.1 instance
on Red Hat Enterprise Linux, but there are two significant differences:
You cannot use the regular system tar command in bin/tar or /usr/bin/tar on Solaris. This
version of tar is incompatible with the Red Hat Enterprise Linux version of tar. You must use GNU tar
or gtar, which is available through the supplemental or community software packages.
Use the gzip (gtar -z) compression method since bzip2 (tar -j) is not supported on Solaris. For
example, to create a tar file on Solaris, run the following:
# tar cpfz
Then, use the following command to unpack the tar file:
# tar xfpz
Many of the path names are different between Solaris and Red Hat Enterprise Linux.
Solaris Path Red Hat Enterprise Linux Path
/usr/lib/sparcv9
/usr/lib (32-bit)
/usr/lib64 (64-bit)
/etc/default /etc/sysconfig
/usr/lib/sparcv9/sasl2 Not used in Red Hat Enterprise Linux
WARNING
Migration cannot change the hostname used by the Directory Server and Admin Server. T he old
machine must have the same hostname as your new machine. T o commission a new machine on
which to run Directory Server 9.1, first rename the old machine (for example, change
ldap.example.com to ldap_old.exam ple.com ), then give the new machine the original
name of the old machine (ldap.exam ple.com ). Because of the large number of configuration
issues based on the Directory Server's hostname — including the Console, replication, T LS/SSL,
and Kerberos — it is extremely difficult to rename the server. Red Hat strongly recommends that
you do not attempt to change the Directory Server hostname.
1. Upgrade 8.0 and 8.1 servers to 8.2 on the local machine.
NOTE
Upgrade is only supported from 8.2 to 9.1.
2. If the new machine is a different architecture than the original machine, meaning the original
machine is 32-bit and the new machine is 64-bit, export all of the Directory Server 8.2 databases
to LDIF.
The LDIF files must be the same as the database with a .upgrade.ldif appended, and they
must be located in the /var/lib/dirsrv/slapd-instance_name/ldif directory for the
Chapter 5. Migrating from Previous Versions
75