Installation guide

The migration script has different options available to facilitate migration; the different usage scenarios
are explained in the following sections.
Section 8.4.1, “Migrating a Server or Single Instance”
Section 8.4.2, “Migrating Replicated Servers”
Section 8.4.3, “Migrating a Directory Server from One Machine to Another”
Section 8.4.4, “Migrating a Directory Server from One Platform to Another”
8.4.1. Migrating a Server or Single Instance
To migrate a Directory Server installation to a new one on the same machine, run the migration script,
specifying the old server root directory:
/usr/sbin/migrate-ds-admin.pl --oldsroot /opt/redhat-ds
General.ConfigDirectoryAdminPwd=password
That command automatically migrates every Directory Server instance configured. T o migrate specific
instances, use the instance with the m igrate-ds-adm in tool. For example, to migrate the Directory
Server instance named exam ple and exam ple3, but not exam ple2, the migration command would be
as follows:
/usr/sbin/migrate-ds-admin.pl --oldsroot /opt/redhat-ds --instance exam ple --
instance example3
General.ConfigDirectoryAdminPwd=password
NOTE
On Red Hat Enterprise Linux and Solaris machines, the m igrate-ds-adm in tool is in the
/usr/sbin/ directory. On HP-UX machines, the m igrate-ds-adm in is in the
/opt/dirsrv/sbin/ directory.
WARNING
If Directory Server databases have been moved from their default location (/opt/redhat-
ds/slapd-instancenam e/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. T herefore, 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-
instancenam e/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.
Chapter 8. Migrating from Previous Versions
101