Red Hat Directory Server B.08.00.02 for HP-UX Release Notes and Supplemental Instructions

cd /opt/dirsrv/sbin
./migrate-ds-admin.pl --oldsroot oldserver_datadir \
--actualsroot /var/opt/netscape/server7 \
--instance slapd-instance --cross
The migration script migrates the legacy Directory Server and creates Red Hat Directory Server
8.0 Directory Servers using the configuration information from the legacy Directory Server
instances. If you used the migrate-ds-admin.pl script, the script also creates new a
Administration Server. The migration script also starts the new Directory Servers and
Administration Server.
NOTE: The migration utility copies the legacy Directory Server information and settings to
create information for the Red Hat 8.0 configuration. The migration utility does not modify or
delete legacy data.
6.4.3 Migration Script Examples
This section contains migration script examples.
Example 1
The following command migrates all configured Netscape Directory Server 6.11 or 6.21 instances
and the Administration Server to Red Hat Directory Server 8.0. The legacy server root directory
on the source system is /var/opt/netscape/servers. The archived installation root directory
files for the legacy Directory Server 6.11 or 6.21 on the destination system are located in /tmp/
server6.
cd /opt/dirsrv/sbin
./migrate-ds-admin.pl --oldsroot /tmp/server6
--actualsroot /var/opt/netscape/servers --cross
--file=setup.inf
Example 2
The following command migrates all configured Red Hat Directory Server 7.1 instances and the
Administration Server to Red Hat Directory Server 8.0. The legacy server root directory on the
source system is /var/opt/netscape/server7. The archived installation root directory files
for the legacy Directory Server 7.1 on the destination system are located in /tmp/server7.
cd /opt/dirsrv/sbin
./migrate-ds-admin.pl --oldsroot /tmp/server7
--actualsroot /var/opt/netscape/server7 --cross
--file=setup.inf
6.5 Additional Procedures for Migrating a Secure Directory Server
If you use SSL with the Directory Server, the Directory Server stores the SSL private key for a
server in a token and protects the token with a password. The password must be specified to
start the Directory Server. The password can be specified interactively or with a password file.
The migration scripts start the new Directory Server as part of the migration process. If you use
SSL to secure the existing Directory Server, the new Directory Server is also configured to use
SSL. However, the migration scripts are not interactive and cannot prompt for the password
used to protect the SSL private key token. There are two methods to work around this problem:
• Temporarily disable SSL security for the Directory Server
• Create a password file (also referred to as a PIN file) for the SSL private key token
6.5 Additional Procedures for Migrating a Secure Directory Server 47