Installation guide

1. Stop all Directory Server instances and the Admin Server.
2. Back up all the Directory Server user and configuration data.
3. Install the Directory Server 8.2 packages on the new machine which will host Directory Server.
4. Make the old Directory Server accessible to the new machine, either through an NFS-mounted
drive or tarball.
5. Run the migration script as root. Specify the current physical location of the Directory Server with
the oldsroot parameter and the location on the old machine with the actualsroot parameter.
IMPORTANT
Do not set up the new Directory Server instances with setup-ds-admin.pl before
running the migration script.
For example:
# /usr/sbin/migrate-ds-admin.pl --oldsroot server2:/migration/opt/redhat-ds -
-actualsroot /opt/redhat-ds General.ConfigDirectoryAdm inPwd=password
6. T he migration process starts. T he legacy Directory Server is migrated, and a new Directory Server
8.2 instance is installed using the configuration information from the legacy Directory Server.
7. After the migration process ends, then the Windows Synchronization service has to be manually
resynchronized.
a. Reboot the Windows machine.
b. In the Directory Server Console, open the Configuration tab.
c. Expand the Replication folder, and select the database.
d. Right-click the synchronization agreement, and select Initialize Full Re-synchronization
from the drop down menu.
8. Verify the Directory Server settings.
IMPORTANT
Always verify the Directory Server configuration after migrating from 7.1 to 8.2. Some
configuration settings, like passwordMinLength for a global password policy, are not
migrated.
Review all policy settings in the new 8.2 instance and make any changes before putting the
system into production.
5.2.6. Migrating a Directory Server from One Platform to Another
To migrate a Directory Server installation from one platform to another is similar to migrating from one
machine to another. T he difference between a migration between platforms and other migration
scenarios is the information migrated from the old Directory Server. The databases are in an
architecture-dependent binary format and can be migrated only after they are exported to LDIF. Other
data, such as the changelog, is not migrated. As explained in Section 5.2.5, “Migrating a Directory Server
from One Machine to Another”, the migration script uses the actualsroot and oldsroot parameters to
migrate across machines and the cross parameter to signal that the migration is cross-platform.
Chapter 5. Migrating from Previous Versions
73