Best practices for NetWare Server Migration

  • 3272039
  • 17-Jan-2007
  • 16-Mar-2012

Environment

NetWare 5.1
NetWare 6.0
NetWare 6.5
OES - NetWare

Situation

Best practices for NetWare Server Migration

Additional Information

Preparing the Destination Server
The destination server should be installed as a pre-migration server, in a temporary tree with a temporary server name. You need to install licenses on this server as well, so that multiple connections can be made to the server. You may create additional volumes on the destination server at this time. After the server is installed with licenses and volumes are created, you should leave this server alone until you begin the migration, with the exception of things noted in the next section, Preparing for the Migration. You should NOT install any additional products on it at this point, such as iPrint, Groupwise, etc. This is done after the migration.

One thing to be aware of is that if the source volume is compressed, and your destination volume is uncompressed, then make sure there is enough space assigned to the destination volume for all uncompressed files on the source volume. All files should be decompressed during the migration (unless the destination volume also has compression turned on).

Preparing for the Migration
Before you actually begin the migration, there are a few things you should do first.
- Get the latest Migration tool that supports your source and destination server versions.
- Carefully review the documentation for your Migration tool.
- Make a full backup. It is extremely rare that you will need it, if the steps in this TID are followed, but the worst case scenario can and does happen on occasion.
- Run DSREPAIR -RC to make a backup of the DS Database. The Migration tool automatically makes its own backup of the DS database, but sometimes this backup becomes corrupt.
- Manually backup the trustees with a tool such as TRUSTBAR.NLM. The most common problem NTS sees with the Migration Wizard is that the trustees cannot be restored. This is a simple fix if you have your own manual backup.
- Put the servers at the latest support pack. Support packs are made to fix problems.
- Put the latest TSAs on. The TSAs are the main component the migration tool uses to perform the migration.
- Use ONLY one protocol. If you can use IP, we recommend that protocol. Disable other protocols entirely (unbind it from the Network Cards).
- Make sure the servers know about each other. Edit the SYS:\ETC\HOSTS file on both the source and the destination, and put entries for both servers in each file. In other words, either server's hosts file will have an entry for itself and the other server. Make sure the servers can ping each other.
- Check the free space on SYS. Note that purgable space is not free space. If SYS is low, problems can occur during the migration. You'll need to find a way to free up space on SYS.
- Make sure directory quotas are disabled on the destination.
- Be aware that compressed files have to be decompressed, this will increase the time the data copy takes.
- You can do a "pre-copy" of the data with the migration tool, which will shorten the time required to perform the migration. Use the tool to copy the data, then when you're ready to perform the migration, re-do that step, copying only the newer files. This copies only the files that have changed.
- Check the Speed / Duplex settings and make sure they match.

Performing the Migration
- Migrations should be performed on the same subnet.
- Disable logins during the migration.
- Shut down any programs that are running on the server.
- Pay attention to what the wizard tells you.

How to deal with problems that may occur
- The most common problems are covered in the documentation in the troubleshooting section.
- If the DS Migration fails, make sure the Destination server is in a pre-migration state. It needs to be in a temporary tree with a temporary server name, using an available IP address. If it is not in that state, get it back to that state by making appropriate changes in the autoexec, remove DS, reboot, and re-install DS. For the source server, bring it back up and follow KB 10066225 to restore DS back to it. Reboot it, and you should be ready to re-do the DS migration portion of the migration.


Post-Migration tasks
After the migration is complete, you can install additional products, both those included with NetWare and anything extra. If there is data used by those programs, remember to point them to where that data is.

.

Formerly known as TID# 10099115

Feedback service temporarily unavailable. For content questions or problems, please contact Support.