Show Table of Contents
Chapter 5. Migrating from Previous Versions
This chapter describes migrating from previous versions of Red Hat Directory Server to Red Hat Directory Server 9, including tasks that you must perform before the migration can begin, and different database migration methods.
5.1. Important Considerations
The migration process does not and cannot change the host name. If you are migrating a Directory Server instance from one machine to another, the new machine must have the same host name as the old machine.
There are a number of reasons why the host name cannot change because of the number of configuration areas that are not touched by migration and require the host name of the Directory Server in order to function:
- The Configuration Directory Server must have the same host name before and after migration or console clients will fail to connect.
- Replication and synchronization will break because both replication agreements and replication metadata (RUV) contain the host name.
- Changing the host name breaks SSL/TLS because server certificates use the fully-qualified domain name in the subject DN.
- SASL GSS-API connections will fail. The Kerberos principal for the server is tied to the fully-qualified domain name. Changing the host name will break GSSAPI clients.
Even though the old host must be renamed before migration is complete, the old machine should still be available on the network so that its data are available to the new Directory Server instance. This is required for a 7.1 migration for the migration script, but it is a convenience for a cross-platform upgrade process.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.