Migrating Replicated Servers
/opt/redhat-ds/is the directory where the old Directory Server is installed.
The migration process starts. The legacy Directory Server is migrated, and a new Directory Server 8.0 instance is installed using the configuration information from the legacy Directory Server.
4.2. Migrating Replicated Servers
The process for migrating a replicated system is the same as for a single server, but the order in which the Directory Server instances is important to keep from interrupting replication. First migrate all master servers, then all hubs, and then all consumers. If any Directory Server the replicated system will be moved to a different machine or a different platform, use the --actualsrootand --crossparameters with migrate-ds-admin.pl, as described in Section 4.3, “Migrating a Directory Server from One Machine to Another” and Section 4.4, “Migrating a Directory Server from One Platform to Another”.
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 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.
