Move to Linux (Option 2)

From MicroFocusInternationalWiki
Jump to: navigation, search

Introduction

This documentation is intended for customers planning to migrate all or part of their NetWare environment to Open Enterprise Server SP2 and SUSE Linux Enterprise Server 9 SP3. The step-by-step instructions describe how to move data from a NetWare server being access by users running Windows workstation and the Novell Client software to a Linux server.

Moving the data following these instructions creates an environment Linux environment that recognizes file attributes and trustee rights as specified in eDirectory. In the Linux environment, the data and users are managed using iManager and other eDirectory solutions. Users running Windows workstation and the Novell Client for Windows will have access to the files in the Linux environment.


Before and After Configurations

After the migration, the server in Configuration 1 and the server in Configuration 2 both exist on the network but some or all data from Server 1 is now moved to Server 2. Server 1 might still contain data to be accessed and might still be providing services. After the migration, desktop users can use Novell Client for Windows to access files and services on both Server 1 and Server 2.


Component Before (Configuration 1) After (Configuration 2)
Server computer hardware Existing computer New computer
Server operating system NetWare 6 or Later

SUSE Linux Enterprise Server 9 SP3

Open Enterprise Server SP2

Server software for network access Native File Access Protocols Samba
Server protocol for network access CIFS CIFS
Server storage device   New storage device
Storage device file system Novell Storage Services (NSS) Novell Storage Services (NSS)
eDirectory tree name   Same as current tree name
Server name in eDirectory   New server name
Desktop operating system Windows 98, 2000, or XP operating systems Windows 98, 2000, or XP operating systems
Desktop software for network access Novell Client for Windows Novell Client for Windows
Desktop protocol for network access Novell Core Protocol (NCP) Novell Core Protocol (NCP)

Note: Shaded items indicate a component change from Configuration 1 to Configuration 2)


Issues and Considerations

This option has a combination of benefits and drawbacks that may make it appealing for your situation. The following topics describe issues you might encounter if you select this option.

Migrating Services

These instructions are meant to document how to migrate data-type files and directories, such as user home directories and company documents, to the Configuration 2. They do not describe how to migrate services that might be running on Configuration 1 such as printing, domain name services, email post office, or Web server.

Desktop Access Issues

To access the data on Server 2, users running Windows and the Novell Client for Windows are required to update any drive mappings and desktop shortcuts that pointed to data previously located on Server 1.


Step 1: Meet the Prerequisites

Computer Server 2 must meet minimum system requirement for SLES 9 SP3 and OES SP2
Storage device Server 2 must have enough disk space to install SLES 9 SP3, OES SP2, and the files to be transferred from Server 1
Network requirements Server 2 must have a unique IP address


Step 2: Install SLES 9 SP3, OES SP2, and Set up NSS Storage

Summary: During the SLES 9 install, partitions must be set up with EVMS.

  1. On the new computer, boot from the OES installation CD or DVD to begin the installation.
  2. When the installation reaches the Installation Settings screen, delete all partitions and the partition table.
  3. Create a primary partition on the disk to use as the boot partition. When a computer has multiple types of partitions, this separate boot partition lets Linux identify the proper partition to boot from.
  4. Create a secondary primary partition on the disk to hold the swap file and system files. Allow at least 2 GB (minimum) or up to 10 GB (recommended), depending on the OES services that you intend to install on Server 2.
  5. Leave enough free space for the files being transferred from Server 1.