3.3 Coexistence with
Windows NT
We strongly recommend installing OS/2 Warp Server for e-business on a test
machine prior to migrating a production system. Try both a pristine
installation and a migration of a cloned machine for achieving the following:
- Become familiar with the installation process.
- Discover hardware related problems.
- Discover software related problems concerning the migration of the
operating system, OS/2 LAN Server, MPTS, and TCP/IP.
- Find out if additional programs are migrated in an acceptable manner,
such as HP JetAdmin Port Driver, Lexmark Markvision Marknet Port Driver, Bonus
Pack Utilities, TME 10 Netfinity Server 4.0, or SystemView 1.0.1.
- Discover software related problems with the JFS file system, such as
does your backup software handle JFS formatted drives properly?
- Discover problems of the kind mentioned in Section
2.3.2 Windows NT Coexistence on Same Machine.
- Get the response files that will be created automatically by the panel
driven OS/2 installation program. Refer to Section
4.4.3 Attended Installation Response Files.
Possible hardware-related migration problems could be:
- Your server has a disk array. For some reason, the disk array controller's
device driver is downgraded during the migration process, and the RAID is not
be accessible after the next reboot.
- The migration routine examines the graphics chipset and installs a
driver that, for some reason, is not appropriate. After the next reboot, the
screen is unreadable.
- A hardware device that worked under previous OS/2 LAN Server versions
fails to work with OS/2 Warp Server for e-business. There is no chance to get
it running because an appropriate driver is not yet available.
Possible software-related migration problems could be:
- LVM reassigns drive letters to existing partitions that do not match with
those prior to the migration
- 386 HPFS formatted volumes are not migrated properly; so, access to the
hard disk will be denied due to missing access control information
- Values in some .INI files are modified during the migration; that is,
the CACHESIZE= parameter in the HPFS386.INI is
reset to a standard value, and the server might refuse to start due to lack of
memory.
| Important
Note |
|---|
|
If you migrate to a different hardware that is a clone of a currently
productive system, be careful not to use duplicate network addresses or names.
|
3.5 Evaluate Disk
Utilities and Customer-Written Tools