The following is an example of transferring a NetWare 6.5 SP7 CA and eDirectory replica server to an OES server using the Transfer ID option in the OES Migration Tool.
Table E-1 Service Migration Summary
|
Pre-Migration |
Post-Migration |
|---|---|
|
A NetWare 6.5 SP8 server running as the master replica server and certificate authority for the eDirectory tree. |
A single OES server running as the master replica server and certificate authority for the eDirectory tree. The server has the same name and IP address as the NetWare server. |
|
This server currently provides these services:
|
This server provides these services:
|
Q: Do we need to remove the Certificate Authority and create a new one on the new server?
A: No. The Identity Transfer option migrates the existing eDirectory Certificate Authority to the new server.
Q: To migrate the master, do we need to remove all eDirectory replicas, remove the server from eDirectory, build a new server with the same name, add replicas back, etc.?
A: No. The Identity Transfer option migrates the existing eDirectory database to the new server.
Prepare your servers by following the instructions in Preparing for Transfer ID
in the OES 2015 SP1: Migration Tool Administration Guide.
Make sure you do the following:
Install the OES target server in the same context as the NetWare source server, using the Novell Pre-Migration Server pattern and the patterns for all services that correspond to the services running on the NetWare server.
This ensures that eDirectory is installed on the target server without a replica and that the target server is prepared for all of the services being migrated.
IMPORTANT:You must select the Pre-Migration Server install pattern during the initial OES installation. Otherwise, an eDirectory replica is installed and/or configured on the server, and the server is not a valid migration target server.
Selecting the pattern later will not remove the replica configuration.
If you install a server without selecting the pre-migration pattern initially, you must start fresh by performing a New Server installation and being sure to select Pre-Migration Server as one of the initial OES patterns.
For instructions, see Installing OES 2015 SP1 as a New Installation
in the OES 2015 SP1: Installation Guide.
If you are moving data from NSS volumes on the NetWare source server, create corresponding NSS volumes on the OES target server. Be sure to use the same names as on the source server.
Do not create any new volumes that will not have data migrated to them until after the Identity Transfer migration is completed.
Verify that the host name and DNS entries in your local /etc/hosts files and on the DNS server are correct.
Apply the latest SLES 11 and OES patches from the Novell Customer Center to the target server. For more information, see Updating (Patching) an OES 2015 SP1 Server
in the OES 2015 SP1: Installation Guide.
If the source server is running NetWare 6.5 SP7, install the SMS patch first. If the source server is running SP8, this is not necessary.
Migrate your server by following the instructions in Using the Migration GUI Tool for Transfer ID
in the OES 2015 SP1: Migration Tool Administration Guide.
Make sure you do the following:
If you are moving data from NSS volumes on the NetWare source server, follow the instructions in Migrating File Systems to OES 2015 SP1
in the OES 2015 SP1: Migration Tool Administration Guide.
Do not select iManager, VLDB, NetStorage or LDAP for migration. These services work automatically after the ID Transfer is complete.
SLPDA must be manually reconfigured after the migration completes.
Set up the SLP DA on your OES server by following the instructions in Setting Up an OpenSLP DA Server
in the OES 2015 SP1: Planning and Implementation Guide.
Clean up the old eDirectory target server objects by following the instructions in Cleanup Objects
in the OES 2015 SP1: Migration Tool Administration Guide.
If you have DFS junctions, check one of them in this VLDB management context to make sure it is still working. If it is not working, rebuild the VLDB using the instructions in Repairing the VLDB
in the OES 2015 SP1: Novell Distributed File Services Administration Guide for Linux.
For information about time synchronization services on a Novell network, see Time Services
in the OES 2015 SP1: Planning and Implementation Guide.
Verify that all of the other services are working as expected.