
Chapter 8. Migrating from Previous Versions
96
8.4. Migration Scenarios
The migration scenario differs depending on the type of existing Directory Server configuration you
have. It is possible to migrate a single Directory Server instance, all Directory Server instances on
a machine or replicated servers and to migrate the Directory Server to a different machine, or to
a different platform. 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. To migrate
specific instances, use the
instance
with the
migrate-ds-admin
tool. For example, to migrate
the Directory Server instance named
example
and
example3
, but not
example2
, the migration
command would be as follows:
/usr/sbin/migrate-ds-admin.pl --oldsroot /opt/redhat-ds --instance example --instance
example3
General.ConfigDirectoryAdminPwd=password
NOTE
On Red Hat Enterprise Linux and Solaris machines, the
migrate-ds-admin
tool is in
the
/usr/sbin/
directory. On HP-UX machines, the
migrate-ds-admin
is in the
/
opt/dirsrv/sbin/
directory.
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