Migration to NW6.0

Migration to           NW6.0        [Dell 4600 Xeon-2.4Ghz]

from                     NW5.0        [Dell 2300 PIII-500Mhz]

Netware 6 Migration Wizard documentation

Search the Knowledgebase

Migration Wizard

Source Server

Destination Server

After Migration Wizard

Additional Services

Migration Wizard

Migration Wizard was originally very very slow.  I was connecting to the original server through a second switch.  This configuration resulted in a 3 week transfer duration of only 36GBs.   I moved both servers to connect through one switch.  This improved transfer duration to be 5 days.  I checked the switch and found variable speeds set.  I forced 100MB/half duplex on both servers.  This reduced the transfer duration to 12 hours.  Later I set the switch and manually configured the workstation running the Migration Wizard to run at 100/half duplex.  Transfer was finally reduced to a 3.5 hour duration for the 36GBs.

Migration Wizard Troubleshooting

TID 10071563 - Migration wizard fails with an error DSBACKUPCREATE xfffffd60.

TID 10071361 - When trying to migrate DS with the Migration wizard 6.0.1.0002 an insufficient rights error is received.

TID 10078795 - Error: DSBACKUP create NDS error.  You do not have sufficient rights to complete the operation

TID 10066210 - NetWare 6 Migration Wizard 6

If you have problems with NUWAGENT.NLM, try applying the TSA5UP11 (TID 2964311) patch on both the source and target servers...

If your MigWiz process fails at the end of step three, where the source server is downed but the client fails to reconnect to the target server, and you are running more than one protocol, a possible solution is to disable IP on both the source, target, and MigWiz workstations on future migrations. To try to pick up and proceed forward in this specific situation, I discovered you can manually run the DIBMIG.NLM on the target server - this is the next step to be done per the Detailed Steps TID, and then the target server can be restarted and the migration continued (this worked twice in 'lab situations').

Source Server

Netware 5.0 SP6a

GroupWise 5.5 sp5
Volume "SYS":  Traditional, compressed, 8GB
Volume "Volume1": NSS, no compression, 18GB
Volume "Volume2": NSS, no compression, 9GB
 
Added: Nss5o.exe (TID 10068067) It does load on my NW5.0SP6a.
Added: DS 7.60 (ds760c.exe)
Setting:  NSS /directoryquotas=ALL  (TID 10064226)
Setting:  MBNWSA.NSS /restoresp2 (TID 10070617)

Destination Server 

Install Netware 6.0 on Destination Server:

Dell 4600 Xoen 2.4Ghz

Put operating system CD in server.  Bootup to Option Install netware, run netware. Choose install “I”.

License accept

Create New partitions

Remove existing Netware Partitions.  Modify DOS partition. 1500MB. 

It Reboots. Makes partition.

License Accept.

Select Express. Enter to change to Custom.   Select New server. Enter to change to Pre-Migration..Continue

Continue.

Server Settings.   Accept default setting.   Continue.

Regional settings. Accept default setting.   Continue.

Mouse Video.  Accept default setting.   Continue.

Copies Files to C:\nwserver\

Device drivers.  Continue.. 

Loading driver….

SCSI.01.benchmark.DLT1.  NWASPI.cdm (temp) not NWTAPE.cdm.

Storage, Network boards, NLM.  Accept default setting.   Continue.

Volume SYS prots.  F5 to toggle to traditional.  No option for compression. 4000 MB largest it can go. Continue

Copies Files to SYS:\

Bootsup to Installation guide

Server name: Server2 . Next>

Put license/cryptogrphic disk in. Next>

Change SYS volume to 12GB. Create Volume1 (30GB, NSS, No Compress) and Volume2 (12GB, NSS, No Compress).  Advanced.

Change compression here.  OK>

Back to Volumes screen. Next>

Mount all volumes when the server reboots. Yes. Next>

Network board. IP address (xxx.xxx.xxx.xxx), IPX. Next>

Name server 1 and 2 (xxx.xxx.xxx.xxx and .xxx). Next>

EST time. Next>

New NDS tree. Next>

Tree=Tree2. O=org2.   Admin.org2  pw:xxxxx. Next>

Installs NDS

License. Next>

LDPD. Next>

Products to be installed. Netware OS. Next>

Copies everything….

“To complete the installation, remove disks, and restart” OK>

Reboots..

Destination:
Netware 6.0
Volume "SYS":  NSS, compressed, 12GB  (migrates great)
Volume "Volume1": NSS, no compression, 30GB 
Volume "Volume2": NSS, no compression, 12GB
Added: SP2
Added: edir862sp2b
Added: nw6nss2d (Post SP2 NSS)
Added: Httpstk2  (it previously abended, this file fixed it)
Setting:  NSS /directoryquotas=ALL  (TID 10064226)
Setting:  NSS /restoresp2 (TID 10070617)

After Migration Wizard

After the completion of the Migration Wizard several NDS changes had to take place.

Users lost rights to Login directory resulting in a login error when mapping drives. I scanned the ConsoleOne on both servers looking for discrepancies and found several. All but one non-ndps printer transferred correctly.  I deleted the printer, print server, and print queue from NDS.  I then reinstalled it on the network, keeping the same name as before.  This allowed client workstations to keep existing print configurations.

Additional Services

GroupWise

Copied GroupWise system (POA, MTA, GWIA) files to new server system directory.  GWIA did not transfer well so I deleted it and reinstalled with SP2.  It loads well but had 550 host unknown issues.  I had to add an IP entry to the host file in ETC directory.  I later found that this left Novell in a compromised state.

Updated GroupWise to version 6.0.3:

I deleted the GWIA and downloaded the SP3 for Netware 6.0.  I upgraded the POA and MTA without any problems.  Since I had deleted GWIA directories and leaf objects I could install version 6.0.3 with a clean version.  All GroupWise clients were running version 5.5 (PC) and 5.2.8 (Mac).  Client version 5.5 works fine with version 6 system files.  I would later upgrade everyone's client to version 6.0.3.   the MAC  client would work with 5.2.8 (2001), however I made sure everyone was using IP and port 1677. 

Arcserve 7 for Netware.

Must install latest cumulative patch to server and manger after installing or get a PFC error.

Arcserve Manger needs entry to workstation and server host file or manger login errors.

The new client for Arcserve 7 would never run correctly on either XP or 98.  I used an older client version for Arcserve 6 and it worked great.

Backup system would crash every three days.  Apparently the backup database would get too large for btrieve to function.  The following is a solution from Computer Associates.

http://support.cai.com/techbases/as61/10133.html

I would also have to create a new log database directory and a new LOG directory, ex.= sys:system\MKDE\LOG directory.

Netshield