Novell Server Consolidation and Migration Toolkit 1.2, Руководство администратора

Страница: 105 / 130

Migrating Data from NetWare Servers 105
no
vd
ocx
(e
n)
6 Ap
ril 20
07
6 (Conditional) If you selected the diskette swap, continue with Step 6a . If you selected the
automatic copy over the network, skip to Step 7 .
6a
To copy the
nuwnici.nlm
file to the source and destination servers, click Copy NLM
and then click Next .
6b Insert a blank formatted diskette into the floppy drive on the destination server.
6c At the destination server console, enter
load nuwnici -1
6d Remove the diskette from the destination server and insert it into the source server’s
floppy drive.
6e At the source server console, enter
load nuwnici -2
This copies the NICI files to the diskette.
6f Remove the diskette from the source server and insert it into the destination server's
floppy drive.
6g At the destination server console, enter
load nuwnici -3
This copies the NICI files to the destination server.
6h Click Next .
TIP: If you get NICI errors when eDirectory tries to load or when you copy the NICI files,
check to see if
pki.nlm
will load on the destination server. If it won’t load, see
Section 12.4.2, “NICI Errors,” on page 114 .
7 Delete all user connections (except your own) to the source and destination servers, then click
Next .
If you want to first broadcast a logout message to any users logged in to the server, select
Broadcast Logout Message , type the message in the field, and then click OK .
8
Type the passwords for the source and destination trees, then click Next .
9 Resolve any critical errors or warnings on the Migrate NDS/eDir Verification Results screen,
then click
Next .
10 Perform the eDirectory step-by-step migration.
The eDirectory migration is divided into several steps. This is for diagnostic purposes. If the
eDirectory migration fails for any reason, you know exactly what step it failed on and can take
the appropriate measures to fix the problem.
For more information on the NDS/eDirectory migration process, including steps to restore the
source and destination servers, see
Section 12.5, “Recovering from NDS/eDirectory Migration
Failures,” on page 115 .
10a Click Next .
The first step changes
autoexec.ncf
and
timesync.cfg
; modifies the server name
in
hosts
,
hostname
, and
snmp.cfg
; and renames
smdr.cfg
to
smdr.mig
. The
first step also renames
rootcert.der
in both the
sys:system
and
sys:public
directories to
rootcert.der.bak
.
At the end of the migration process, the source server is brought down and the destination
server reboots and takes over the name and identity of the source server.