Migration Wizard From CoolSolutionsWiki Search Views ArticleDiscussionEditHistoryUsing the Migration Wizard for NetWare servers Go 1 Introduction2 Choosing the right migration tool 2.1 Migration Wizard 8.22.2 Migration Wizard 6.53 Preparing the migration3.1 Stuff you need3.1.1 Hardware3.1.2 Software3.1.3 Other 3.2 Preparing yourself 3.3 Prepare your NDS tree3.3.1 Tree health3.3.2 Server certificates 3.3.3 Special NDS preparation (upgrade to NetWare 6.x) 3.3.4 Preinstall your licenses (upgrade to NetWare 6.x) 3.3.5 Normalize and repair volume objects 3.4 Preparing the source server 3.4.1 Patch your server 3.4.2 Tune the SET parameters3.4.3 Clean up AUTOEXEC.NCF3.4.4 Clean up your file system3.4.5 Reboot your server 3.4.6 Backup your trustees3.4.7 Update HOSTS file3.4.8 Backup your NDS3.4.9 Verify your XNTP configuration (NetWare 6.5 only) 3.5 Preparing the destination server 3.5.1 Verify your BIOS configuration 3.5.2 Install your NetWare3.5.3 Verify your eDirectory version 3.5.4 Clean up your AUTOEXEC.NCF3.5.5 Tune the server 3.5.6 Update the HOSTS file3.5.7 Backup the NDS3.6 Preparing your migration workstation3.7 Connecting your servers and your workstation 4 The Migration4.1 Step 0: starting the Migration Wizard and modelling your project 4.1.1 Special considerations regarding the SYS volume 4.1.1.1 Print Queues in Special considerations regarding the SYS volume 4.1.2 Modelling Complete4.2 Step 1: Copy File System Data4.3 Step 2: Edit Configuration Files4.4 Step 3: Begin NDS/eDirectory Migration 4.5 Step 4: Finish the NDS/eDirectory Migration+ MENU Page 1 of 10 Migration Wizard CoolSolutionsWiki 25/02/2009 http://wiki.novell.com/index.php/Migration_Wizard
1 Introduction 2 Choosing the right migration tool
2.1 Migration Wizard 8.2 2.2 Migration Wizard 6.5
3 Preparing the migration 3.1 Stuff you need
3.1.1 Hardware 3.1.2 Software 3.1.3 Other
3.2 Preparing yourself 3.3 Prepare your NDS tree
3.3.1 Tree health 3.3.2 Server certificates 3.3.3 Special NDS preparation (upgrade to NetWare 6.x) 3.3.4 Preinstall your licenses (upgrade to NetWare 6.x) 3.3.5 Normalize and repair volume objects
3.4 Preparing the source server 3.4.1 Patch your server 3.4.2 Tune the SET parameters 3.4.3 Clean up AUTOEXEC.NCF 3.4.4 Clean up your file system 3.4.5 Reboot your server 3.4.6 Backup your trustees
3.4.7 Update HOSTS file 3.4.8 Backup your NDS 3.4.9 Verify your XNTP configuration (NetWare 6.5 only)
3.5 Preparing the destination server 3.5.1 Verify your BIOS configuration 3.5.2 Install your NetWare 3.5.3 Verify your eDirectory version 3.5.4 Clean up your AUTOEXEC.NCF 3.5.5 Tune the server 3.5.6 Update the HOSTS file 3.5.7 Backup the NDS
3.6 Preparing your migration workstation 3.7 Connecting your servers and your workstation
4 The Migration 4.1 Step 0: starting the Migration Wizard and modelling your project
4.1.1 Special considerations regarding the SYS volume 4.1.1.1 Print Queues in Special considerations regarding the SYS volume
4.1.2 Modelling Complete 4.2 Step 1: Copy File System Data 4.3 Step 2: Edit Configuration Files 4.4 Step 3: Begin NDS/eDirectory Migration 4.5 Step 4: Finish the NDS/eDirectory Migration
To help with migrating to new hardware (with or without version upgrade), Novell has a tool called the “Migration Wizard”. The version is now aToolkit” aka SCMT and includes both the Migration and the Consolidation tool in one tool. This document however will mainly concentrate on Salso good for server consolidations. I will continue to call it the Migration Wizard for simplicity, especially since in certain cases; you may need tGenerally, the Migration Wizard works quite well. However without proper tuning, migrations can be slow, and also, if something goes wrong, tof this document is to give recommendations on tuning the server configurations so as to speed up the migration and reduce the risk of problesteps that will make it easier for you to recover from failed migrations.
Don’t be scared by reading this document. The document deals with a lot of smaller or bigger things that could go wrong. This doesn’t mean ththat you could potentially face and how to prevent them or deal with them.
6.3.1 %s is a NetWare 5.0 server. Install NICI patch 1.5.7 or newer on this server before proceeding with the migrat 6.3.2 Server 'NAME' won't return the correct time. 6.3.3 Invalid Microsoft Data Access Components (MDAC) version
Tip! This document also applies to migrations from physical to virtual servers. If you plan to move a physical svirtual server under VMware, just follow the instructions on moving a server to new hardware.
Migration Wizard 8.2
The latest tool is the Migration Wizard 8.2.709.14 which is part of SCMT 1.2.070914 and is dated 14 September 2007. IT is the version includeNetWare 6.5 as well as OES2. This version is also available for download at http://download.novell.com/Download?buildid=bibbruEYmPc~ It is important that you have the correct subversion as it fixes bugs found in earlier versions of the 8.x Migration Wizards. So don’t use any versThe documentation for this version can be found at http://www.novell.com/documentation/scmt/index.html This version supports migrations froOES/NetWare and OES2/NetWare).Migration Wizard 6.5
If your destination server for your migration is NetWare 5.1, then you need to use the Migration Wizard 6.5 instead. The latest version is 6.5.50http://www.novell.com/coolsolutions/tools/17244.html Once again, it is important that you use this version and not earlier 6.5 versions, especially since older 6.5 versions were not compatible with Xhttp://www.novell.com/documentation/migwiz65/index.html While this version also supports migration to NetWare 6.x, it is recommended to use version 8.1 when NetWare 6.x servers are involved.
Preparing the migrationStuff you need
Hardware
source server destination server. Make sure your destination server is compatible with the NetWare version you want to install and that you have the
(recommended but not required) a small fast switch and patch cables to directly interconnect your 2 servers and your migration workst a reliable workstation running Windows 2000 or Windows XP with the latest patches and a relatively up to date client (4.91 SP2 or late disable screen saver and power save mode if laptop.
Software
NetWare installation CDs. Use the latest overlay versions that already include the latest support pack The appropriate Migration Wizard (see versions in the previous section) The latest TRUSTEE.NLM available from http://ftp.novell.hu/pub/mirrors/ftp.novell.com/netwire/nsd/trust110f.exe (always useful) TOOLBOX.NLM 2.17 available at http://www.novell.com/coolsolutions/tools/13950.html
Other
a floppy drive cleaning kit in case you are using the Migration wizard 6.5
a paper printout or a downloaded version of all the migration documentation so that you can look it up at any time an Internet connection to get additional information in case you get stuck somewherePreparing yourself
The first thing to do before starting a migration is to thoroughly read the documentation involved. This involves reading at least the 3 following d
this document the documentation for the Migration Wizard. See the section above for the links to the correct documentation in case your migration is an upgrade, read the install/upgrade documentation for the destination NetWare version.
Tip! If your destination server is a NetWare 6.5 server, you should read the OES documentation athttp://www.novell.com/documentation/oes/index.html and not the NetWare 6.5 documentation which is outdatPrepare your NDS tree
This can already be done a couple of days in advance so that you don’t have a surprise the day of the migration. However if you do this before,
Tree health
It is important that your tree is healthy, especially the server you want to migrate. Time should be in sync, there should be no communication probituaries. Solve all your NDS problems before proceeding.
Server certificates
If your source server is running NetWare 5.1 or later, make sure it doesn’t have any expired certificates. Run PKIDIAG.NLM to verify and fix yoNetWare 6.x where a lot of services depend on valid certificates and will fail on expired certificates. While certificates can also be fixed after thepotential problem before the migration.
Special NDS preparation (upgrade to NetWare 6.x)
If your migration is not a same server migration but an upgrade from a NetWare 5.1 or lower to NetWare 6.x, then special care must be takes t
minimum NDS version requirements for all servers in your tree and you should use the deployment manager to prepare your tree (see the instFor a smoothest possible migration from 5.1 to 6.5, I would recommend that your root servers for your tree are already running eDirectory 8.7.36.5, the eDirectory version inluded with NetWare 6.0 SP5 is good enough for the migration, but if you are going to keep around some 6.0 serveupgrading to eDirectory 8.7.3, use the file edir_873_ir3_nw.iso which can be found at http://download.novell.com/Download?buildid=NUBsf-Zw
Preinstall your licenses (upgrade to NetWare 6.x)
If your migration is an upgrade to NetWare 6.x, I would recommend you do already install your NetWare 6.x licenses into your tree prior to theNWADMN32.EXE to install the licenses in the container of the server to be migrated or in a container somewhere above it. The normal documethe install/upgrade, but doing it before makes things easier as your server would already be fully licensed after the first reboot after the NDS mi
Normalize and repair volume objects
The Migration Wiazard assumes standard names and location for the NDS volume objects. It will fail on non standard names. Make sure the N
(e.g. servername_volumename) and are located in the same container as your server object. If for some reason, you are not using the defaultthe standard convention before the migration. After the migration, you can once again rename them to whatever suits you. Also, run DSREPAIrepair.Preparing the source server
It is important for the reliability and the speed of the migration that the source server is updated and tuned for the migration.
Patch your server
Install the latest support pack on the source server (NW50SP6a, NW51SP8, NW60SP5) as well as any other patches recommended by the MiWizard 6.5, also install the latest TSA patch on your 5.x servers. For NetWare 5.0, the NSS patch NSS5H.EXE mentioned by the migration wizcontaining the NICI 1.5.7 update is called 'NICID157.EXE'. Both these 2 files are no longer available on Novell's download web site.
Tune the SET parameters
For this, quit MONITOR if it is already loaded, and then load MONITOR with the command:
LOAD MONITOR !h
The option !h makes hidden SET parameters visible and this is important for the communication parameters. Now select the option “Server Parsections:
Communications
TCP Minshall Algorithm On (doesn’t exist in NetWare 5.0) TCP Nagle Algorithm On (Off for NetWare 5.0)
TCP Delayed Acknowledgement On (Off for NetWare 5.0)
Tip! Patches which are no longer on Novell's web site can still be found athttp://ftp.novell.hu/pub/mirrors/ftp.novell.com/updates/
Maximum Directory Cache Buffers 20000 (possibly less if your server does not have m
Minimum Directory Cache Buffers 1500
Disk
Enable Hardware Write Back On
Enable Disk Read After Write Verify Off
File caching
Dirty Disk Cache Delay Time 0.1 Sec
File system - only for TFS volumes
Purge Files On Dismount On (a quick way to purge deleted files on shutdown)
Clean up AUTOEXEC.NCF
Clean up the server’s AUTOEXEC.NCF to comment out all extra services. Especially disable any backup, open file manager and antivirus softapplication that keeps files open. Also, make sure that SMDR.NLM and TSAxxx.NLM are not loaded from AUTOEXEC.NCF as the Migration
Clean up your file system
Delete all unneeded files and directories to avoid unnecessarily copying unneeded stuff. Above all, delete support pack source directories, theSYS:PUBLIC\CLIENTS and old documentation directories (possible leftovers from NetWare 4.x).
Reboot your server
This will make sure that your server will just run in a minimum configuration which is best for the migration. If you don’t reboot your server but juwhen the migration starts. This may especially if your server has been running for a long time and you have run regular backups. In this case, tthe TSAs and SMDR.NLM.
Backup your trustees
Copy TRUSTEE.NLM to the SYS:SYSTEM directory of your server and then individually make trustee backup copies for each volume using th
LOAD TRUSTEE /R volumename: SAVE volumename: volumename:trustee.dat
where of course you replace volumename by the real name of the volume. Include the SYS volume as well. The trustee backup is important inoption ensures the trustee backup uses relative directory names. This allows you to restore trustees even if the volume names or directory stru
Update HOSTS file
Edit the file HOSTS in SYS:ETC and add an entry with the temporary name and IP address of the destination server. This will ensure that the fiduring the migration.
Backup your NDS
h) Take an NDS database dump using the following command:
Note: You will not be able to use these NDS dump yourself. However in case things go badly wrong and you need Novell's help, theyyour server.
Verify your XNTP configuration (NetWare 6.5 only)
If you have a NetWare 6.5 server and you are using XNTP.NLM instead of TIMESYNC.NLM, then verify that NCP is not disabled for XNTP. In
option. NONCP .Preparing the destination server
Verify your BIOS configuration
Go into the server’s BIOS and make sure you set the clock correctly and you disable hyperthreading if this is a server with hyperthreading supp
Install your NetWare
Do the installation from the latest overlay CDs. This is especially important if you use quite new hardware. Make sure you use the same code pspecial characters in their names may cause problems during the migration. Make sure you install your server as a “pre migration” server and yoption is available early in the text part of the install for NetWare 5.1 and 6.0 and in the GUI part of the install for NetWare 6.5 OES/NetWare. Mtemporary tree of its own. Name, tree name and IP address of the server must be different from the source server you want to migrate. Createsource server. However if your destination volumes are NSS volumes on NetWare 6.x servers, do not yet enable user or directory quotas on thspace when copying compressed files and will create zero byte files. If quotas were ued on the source server, the migration wizard will automa
migration.Make sure you do install a license on the destination server, but you can use the demo license found on the NetWare installation CD. Just poininstallation CD when the install asks you about the license. It is not needed to install your real licenses as whatever you license you install willIf you plan to install additional products like Groupwise, ZENworks, Antivirus, Backup, wait till after the migration until you install them.
Warning: If your destination server is a NetWare 6.5 SP6 server, don't install IPX on the destination server. There is a bug in SP6 thatcommunicating if IPX is installed, even when IPX is not used. If you need IPX on the destination server, only install it after the migration. If ySP5 on the destination server and not SP6. While not confirmed, the bug probably also exists in SP7.
Verify your eDirectory version
You should make sure that the destination server does never have an eDirectory version lower than the source server. This is especially the cawas upgraded at some point and the destination is also NetWare 5.1 or 6.0. Also pay attention to the following fundamental incompatibilities:
the destination server should not be running eDirectory 8.6.x. There is a problem with this eDirectory version that can cause the Migraserver is a NetWare 6.0 server, make sure you upgrade it to eDirectory 8.7.3.
if you plan to migrate to eDirectory 8.8.x, then your destination server must be running eDirectory 8.8.2 (or 8.8SP2) and you must be uwill cause the migration to fail and earlier versions of the Migration Wizard will not support eDirectory 8.8.x.
avoid migrating from older eDirectory versions to eDirectory 8.8.x. Such migrations are prone to fail with the problem described in TIDserver fails to open. If you want to go to eDirectory 8.8.x, then migrate to eDirectory 8.7.3.x and only do the upgrade to eDirectory 8.8.
Clean up your AUTOEXEC.NCF
Only on NetWare 6.5 servers: Aat the end of the installation, when the install asks you to reboot the server, do not click on the button yet, but uto edit your AUTOEXEC.NCF. In your autoexec.ncf, you can put a REM in front of the following lines: SYS:\SYSTEM\NMA5.NCF (unless you huse to mange your NetWare server) AFPSTRT.NCF (unless you have Macintosh computers that need to access your server) NFSSTART (unlthrough NFS) OPENWBEM.NCF ?STARTX
Then locate the line “MOUNT ALL”, and add the following line just before it:
NSS /NCPDisplayNonTranslatableNames
In non english speaking countries, this option is important if you have file names with extended characters. The option only exists in NW65SP5
After having made these changes, switch back to the GUI screen and click the button to reboot your server
Tune the server
Load monitor using the command:
LOAD MONITOR !h
Go to « Server Parameters », and change the options in the following categories
Edit the file HOSTS in SYS:ETC. Clean it up to remove all sample entries except for localhost and the server itself. Then add an entry with thethe file copy will not suffer from possible name resolution problems during the migration.
Backup the NDS
Make a backup copy of the NDS of the destination server using the command:
LOAD DSREPAIR -rc
Preparing your migration workstation
Make sure the workstation verifies the recommended configuration as mentioned earlier and then install the correct version of the Migration Wiverify the power options of the PC and make sure that it is configured to never go into sleep mode.Connecting your servers and your workstation
For reliability reasons, make sure the source server, the destination server and the migration workstation are all connected to a same switch. Pconnect the 3 computers and which in turn I connect to the remainder of the network. That way, I’m sure I have a reliably and fast migration netwould recommend the 3 computers and the switch to be connected to an UPS so that they can survive a power outage.
The Migration
The migration itself is a 5 step process. There is a first step (which I call 0) at startup, and then the Wizard itself presents a menu with 4 other sStep 0: starting the Migration Wizard and modelling your project
If you installed the SCMT 1.1, then you actually have the main SCMT program which you can start and which will guide you through a numberMigration or Consolidation. However, you have the option to go straight to the Migration wizard 8.1 by using the following menu sequence:Start -> All Programs -> Novell Server Consolidation and Migration Toolkit -> Tools -> NetWare Migration Wizard 8.1.For the Migration Wizard 6.5, the situation is simpler. You just have one tool, and it starts you out with the Migration questions right away.
Once you have launched the Migration Wizard, you create a project, and select source and destination servers and you start modelling your prsource server to your destination server. The easiest migration is you do a one to one copy where the destination server has exactly the sameadjustments to be done to scripts or configuration files that may refer to volume names. You can however also copy directories or volumes to vserver only had a SYS volume with the data on the SYS volume and on your new server you want to keep SYS separate and have a new voluand drop the complete SYS volume to the new destination volume. In case of volume remodelling, extra NDS operations are recommended at
Special considerations regarding the SYS volume
If you have the simple case where source and destination server have the same volume names, special care must be taken with the SYS voluSYS.MIG on the destination SYS volume which will contain the root directory and all the system related directory of the source server. This is dnew server will old stuff from the old server. If there are additional directories you want to migrate to the destination server while keeping the oriblindly copying directories that might conflict with already existing directories on the destination server. For instance, overwriting some system rdestinations server later on.
Print Queues in Special considerations regarding the SYS volume
Special care also needs to be taken of the printing related directories. If you have print queues on your old server, make sure you drag and drovolume. For this directory, you will get a conflict warning because the directory QUEUES already exists on the destination server. Resolve this
sure you drop and drop the NDPS directory from the source to the destination server. This time you should not get a conflict because if you follthe destination server.
Modelling Complete
Once you have finished modelling your project, you click on the “Verify and Migrate” button. After verification that your project is OK, you get thStep 1: Copy File System Data
Click on button “1” to start the data copy. You will get a number of additional questions regarding your data copy, for instance what to do in casuseful if you run the data copy multiple times. You can indeed rerun step 1 of the migration as many times as you want. In subsequent runs int
option to copy with users active or with login disabled.
Warning: You should never disable login yourself on the server console during the migration process. This would in fact cause the migrdisable login.
Once you answered all the questions, you will get to the point where the Migration Wizard will install/update NLMs on your source and destinatiare SMDR.NLM and TSAxxx.NLM. If you have old versions of these NLMs loaded and they have been used by a backup program after the lastupon the unloading of the old versions of these NLMs. That’s why it is important to follow the instructions on preparing the source server before
Next, the Migration Wizard will backup the trustee and file ownership information and then it will actually copy the files. The time estimate duringet an estimate how long the file copy will last, you will have to wait until the copy actually starts and best wait some 15 minutes into the file coWhile copying big files, the throughput is high and while copying small files, the overhead is much higher and so the copy speed is lower. Becahowever, the estimate given by the Migration Wizard 8.1 tends to be relatively reliable. The Migration wizard 6.5 however can give very bad estfact, in that case, the file copy can sometimes take twice as long as estimated. Furthermore, the progress indicator continues based on the origestimated time, but the last percent can take very long.
Once the copy has finished, make sure you check the error log to see if any files were missed. You will always see a couple of files that could nwhich of these files are just temporary system files and which files are important data. Another error you might see is error 0xFFFDFFF4. This icopied because it has the same date or is older than a file that already exists on the destination. This happens if you run step 1 multiple timesperformance reasons, if you rerun step 1 just to catch files updated since the first run, include a date filter filtering on the last modified date. Thithe time needed for the delta copy.
Warning: If during the file copy, one of the 3 machines (the 2 servers or the workstation) crashes, reboot the 3 machines before rerunniremaining machines will not properly close the file copy and the next migration step will fail.
Note: Step 1 is mandatory. You have to run it at least once in order to be able to continue your migration. If however you decide to use"empty" run of step 1 where you don't select any data to be copied.Step 2: Edit Configuration Files
Step 2 is actually a step where the Migration Wizard doesn’t do anything. It’s a step suggesting you to manually edit some configuration files. I
Assuming you want the destination server to take the IP address of the original server (which generally you want), it’s now the best timwhat it should be later once the destination server has taken over. I suggest not to use INETCFG.NLM yet as this point because editinuse INETCFG.NLM after a successful migration.
Also change the TIMESYNC configuration so that the destination server will take the time from the same source as the source server.the migration will not complain about unsynchronized clocks later on. Do *not* edit TIMESYNC.CFG as indicated in the documentationwill automatically update TIMESYNC.CFG for you.
If you want special SLP options and an SLP.CFG file, it is also now a good to configure them If during your migration, you plan to change the volume names, now is the moment you should rename the NDS volume objects for th
to migrate the old SYS volume to a new DATA volume, you should rename the volume object SERVER_SYS to SERVER_DATA. Doihome directory properties of the users) will follow the name change.
The following things should *not* yet be done as it is too early:
Do not edit the SYS:\ETC\HOSTS . Step 3 of the migration will make modifications to the HOSTS file. These modifications are general
address as indicated above. Therefore, you generally need to modify the file HOSTS after step 3 anyway and so any edit you do now i Do not add servers to your AUTOEXEC.NCF. Your destination server is installed in pre-migration mode. As such, most of the required
AUTOEXEC.NCF now will just confuse the installer later on.Step 3: Begin NDS/eDirectory Migration
Step 3 is the most critical step of the whole migration process. It’s during this step that the actual identity of the old server is transferred to the na special recover operation explained in the troubleshooting section). So make sure you have resolved all problems from prior steps and you amuch more difficult to still get files from your old server. It is also important that the NDS on the source server is absolutely healthy before this sget worse.
Note: The button for step 3 will only become active if you have at least once run the file copy of step 1.
The actual NDS migration in step 3 consists of 3 major operations:
The NICI configuration files copy. This is done by floppy disk or by network. For version 6.5 of the Migration Wizard, the floppy disk m
that you have a working floppy drive both on the source and the destination server. Given the source server might have been runningis important to clean the drive as otherwise, the migration is likely to fail.
Next, the configuration files (AUTOEXEC.NCF, HOSTS and a couple of other files) are updated on the destination server to reflect theconfiguration to match the source server.
Finally, the NDS is backed up on the source server, the source server is downed and the NDS backup file is updated and restored on
Warning: If there are users with open files on the source server, it will not down automatically. It will show you the open files and ask yowill however be replies negatively by additional commands sent to the server console. So be sure that on the source server, you switch to thcommand manually.
Note: The destination server can take a very long time to reboot. Give it a couple of minutes. Once these steps finished the destinationStep 4: Finish the NDS/eDirectory Migration
Before executing step 4 in the migration wizard itself, you should reboot your migration workstation and also make the following changes on th
Edit the files HOSTS and HOSTNAME in SYS:ETC. This is especially important if you changed the IP address of the destination serveHOSTNAME will cause some products installed later to receive incorrect configurations. If you want to use your old HOSTS and HOSany similar tool to copy the files from SYS:\SYS.MIG\ETC to SYS:ETC. Only copy exactly the files your need. Do not do wildcard copi
If you did a major NDS upgrade during the migration, you should run the following DSREPAIR options:
If the previous DSREPAIR reports schema problems for RBS and tells you to run DSREPAIR at a root server, or if you did an upgradeserver during the migration, then do the following in DSREPAIR:
Repair your volume objects. This will ensure that your volumes on the new server get attached to the old NDS volume objects. For thi
Advanced options -> Check volume objects and trustees
Run the back-linker process to verify and repair external references. For this, execute the following console commands:
SET DSTRACE=ONSET DSTRACE=+BLINK
SET DSTRACE=*B
Verify whether your server acquired its license by typing the following command at the server console:
VERSION
Verify and fix your certificates by running PKIDIAG.NLM
Now you are ready to run step 4. Step 4 of the Migration Wizard will restore the trustee, file ownership and quota information.
Note: If for some reason, step 4 fails, you can rerun it as often as you want, and if you followed the instructions on server preparation,information.
Post Migration tasks
Now we are ready to install any additional products. First install any additional products you need that are included with NetWare, and then instBackup software, Antivirus ...).NetWare 6.5
For this, you need the NetWare 6.5 Overlay Products CD or the NetWare 6.5 overlay DVD matching the support pack you used to install your d
Tip! On NetWare 6.5, you can also copy the CD image to the server and mount it using the command:
Now start the GUI environment using the command STARTX and from the Novell menu, select Install . Select the option ADD and browse to ththen get a list of products you can install. From this list, install at least the following products even though some of them are already installed. Iare made to the NDS. Ignore the version warnings you may get about some of these products.
Certficate Server
LDAP NDS iMonitor NRM SMS ConsoleOne NMAS
If you want to install iManager on your server, you need to install the following additional products:
Apache2 admin server Tomcat admin Apache2 web & Tomcat iManager
SEARCH ADD SYS:/APACHE2
SEARCH ADD SYS:/TOMCAT/4/BIN
Tip! If you want iManager to immediately run after the installation without having to reboot your server, executfollowing 2 commands *prior* to the installation of Apache2 and Tomcat:
Older NetWare versions
The post install procedure for older NetWare versions is similar to the one above. I just have no list of default products to install for those platforecommendations for that version at wikiCatagoryLink.
TID2961749 NSS update for Nw 6.0 pre SP2. This update is no longer available and you should only use SP5 on NetWare 6.0 anywa TID10080270 Server consolidation utility fails to copy files TID3213415 Error during Migration Wizard upgrade: "Can't license the connection to server <server name> Please install the licenses TID3272039 Best practices for NetWare Server Migration TID3303779 Web Services no longer function after using Migration Wizard 7.1 TID10100982 Migration Wizard fails in step 4 TID10100692 Migration Wizard is asking for authentication to the destination tree which is no longer there TID10099052 SYS volume fails to migrate. Error code: 0X8998 TID10098044 Out of disk space when doing step 1 of the Migration Wizard TID10095902 ABEND: LockDirectoryEntry called with entry already locked. TID10095334 MigWin32.exe - Unable To Locate DLL TID10094587 Unable to run Migration Wizard on Windows XP SP2 TID10093818 DSBackupCreate Xd - An unknown error has occurred.) BACKUP.NDS TID10090638 Trying to migrate data from NetWare 4.x to NetWare 6 gives errors TID10085486 Migration Wizard step 4 option greyed out or not available TID3395192 NetWare 6.5 Manual Server Migration (Hardware Upgrade)How to recover from a failed migration
The good thing about the Migration Wizard is that the source server can always be placed back into normal operation mode. Therefore, excepta way to bring the source server back to life. Let's see how to recover at the different steps of the migration.
Step 1 (Data copy)
The data copy is not destructuve to the source and destination servers. Also, step 1 is restartable. So if step 1 fails, you can start it over againdata copy, often there remain open SMS connections between the servers. These will lead to possible failure of further copy attempts. It is theryou reboot both the source and the destination servers so that they are in a clean state again.
Here are some common problems that may occur at the beginning of or during the file copy:
Abend of the source or the destination server. Sometimes, you might get an abend right at the beginning of the migration when the MiTSAxxx.NLM) and load the updated versions. With this kind of abend, it is just enough to restart both source and destination servers ainvestigate what the reason for the abend could be. First recheck whether you applied all the recommended patches and did all other
help, the debug your abend the "usual" way by looking at the abend.log file, searching the knowledgebase and askin for help int he su
Lost workstation connection during the migration. The file copy itself is actually done by NUWAGENT.NLM using a direct SMS connecprocess, receives the error messages and sends the instructions on what to do next. If for any reason, your workstation looses connecwill continue with their current job until it is finished, and then they will get stuck waiting for an acknowledgement from the migration w
never really finishes, and if you try to rerun the copy, you get a bad failuer. Therefore, if for some reson, your workstation lost its connehave finished with the copy they were busy doing.
SMS errors while starting the data migration or no migration with no errors at all.
Migration successful but errors in error log for certain files
Step 3 (NDS migration)
A failure during the NDS migration seems to be most scary because after the NDS migration, the source server is no longer operational. Howethe documentation. It is important that if you restore the source server that way, you take care of the destination server which might already hahave to disconnect the destination server from the network (to avoid conflict) and return the destination server to its temporary state.
Step 4 (finish NDS migration/restore rights)
One issue a couple of people may have seen after step 3 is that the Migration Wizard did somehow not correctly record the success of step 3. Idescribed and a fix is given in TID10100982. It is important to verify that step 3 was really successful and that the destination server has takenintegrated in the tree.Common error messages and their resolution
%s is a NetWare 5.0 server. Install NICI patch 1.5.7 or newer on this server before proceeding with the migration, or data l
If your server is running NDS7, you can safely ignore this message. If your server is running NDs8 or later, you should upgrade yopur server NI
about preparing the source server for more details.
Server 'NAME' won't return the correct time.
The complete error message is:
Server 'NAME' won't return the correct time. Please check the timesync status on this server.
--- Error caused by a NetWare API error ---
This error means that the error code returned has different meanings for different functions.
(Error code: 0X89fb Function Name: NWGetFileServerUTCTime)
This error can happen on NetWare 6.5 servers and is caused by the server using XNTP.NLM instead of TIMESYNC.NLM and NCP support for
SYS:\ETC\NTP.CONF and remove the option NONCP from it. This is also described earlier in this document.
Invalid Microsoft Data Access Components (MDAC) version
The Migration Wizard stores the project configuration in an MDB file and the MDAC components to access the MDB file. If you get a messagelatest update from the Microsoft web site and install it. It is however a bit strange that the Migration Wizard is so picky about the exact version gWizard is very small and the bulk of the data like for instance the file ownership and trustee information is not stored in the MDB database but r
Retrieved from "http://wiki.novell.com/index.php/Migration_Wizard "
Categories: Open Enterprise Server Migration | Open Enterprise Server | NetWare
This page was last modified 00:03, 16 October 2008.
