Chapter 8. Migrating from Previous Versions
WARNING
If Directory Server databases have been moved from their default location (/opt/redhat-ds/slapd-instancename/db),migration will not copy these databases, but will use the directly. This means that if you run migration, you may not be able to go back to the old version. Migration will not remove or destroy the data, but may change the format in such a way that you cannot use the older version of the Directory Server. Therefore, make a database backup using db2bak and an LDIF dump using db2ldif of the databases to make sure everything can be recovered.
The most common reason for using a non-default database location is the performance for large databases. For example, if a Directory Server instance has several gigabytes of data, the index files and transaction logs can be moved to a separate disk device to improve the Directory Server performance, especially if there are high update rates. In this case, migration will not attempt to move the databases to the new default location, /var/lib/dirsrv/slapd-instancename/db, but will instead assume that the databases should be in their non-standard location and configure the new server to use the databases in the old location.
This issue does not occur in cross-platform migrations or migrating using LDIF files instead of the binary databases because these already work with an LDIF copy of the database.
1.Stop all old Directory Server instances and the Administration Server.
2.Back up all the Directory Server user and configuration data.
3.On the machine where your legacy Directory Server is installed, install the Directory Server 8.0 packages.
IMPORTANT
Do not set up the new Directory Server instances with setup-ds-admin.plbefore running the migration script.
4.Run the migration script, as root.
# /usr/sbin/migrate-ds-admin.pl --oldsroot /opt/redhat-ds/ General.ConfigDirectoryAdminPwd=password