Installation guide
packages.
Make the first migrated master the configuration instance since it is not replicated. T hen,
register other master and hub servers with the first master Directory Servers configuration
instance.
This instance needs to listen on your standard port, usually 389.
5. Run the migration script, as root.
IMPORTANT
Do not set up the new Directory Server instances with setup-ds-admin.pl before
running the migration script.
# /usr/sbin/migrate-ds-admin.pl --oldsroot /opt/redhat-ds/
General.ConfigDirectoryAdminPwd=password
/opt/redhat-ds/ is the directory where the old Directory Server is installed.
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. Once the old Directory Server instance is migrated, test replication to make sure it is working
correctly.
8. After you finish this process for all of the master server, repeat the steps for the hub servers and
then for the replicas.
9. 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.
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.5. Migrating a Directory Server from One Machine to Another
To migrate a Directory Server installation from one machine to a new Directory Server instance on a new
machine of the same platform, run the migration script (m igrate-ds-admin) with options specifying
the physical, network-accessible old server root directory (oldsroot), such as tarball or network drive,
and specifying the actual directory name of the server root on the old machine (actualsroot), such as
/opt/redhat-ds. In this case, actualsroot names the original absolute installation directory, which
oldsroot gives the path to access that directory.
Chapter 5. Migrating from Previous Versions
71