Tool

(View Disclaimer)

Author: Mohd Sayeed Akthar

Using this single script users can perform OES2 File System Migration

Table of Contents

1. Introduction
2. Prerequisites
3. How it works?
4. Using the script for Migration

Introduction

This document explains about the Script which allow users to complete their Migration job by executing a single script, instead of using several migration tools. This script takes all the required information from user before it starts Migration. Once it collects all the required information it executes the different tools sequentially to finish Migration job.

Prerequisites

1. OES2.0 Migration tools should be installed. OES 2.0 Migration Tools comes along with OES2.0.
2. Create appropriate volumes or directories in destination server. If you are migrating to NCP volume, then ensure admin user has rights over it.
3. Make sure micasad daemon is running on Destination Server.
4. If you are migrating from Windows Source Server then make sure you have exported (shared) the directory in Windows Server which has to be migrated.
5. If you are using perl version of the Migration script, then make sure Perl is already installed

.

How it works?

This script is available in Ruby and Perl. User can use any flavor whichever is comfortable. These scripts supports NetWare, OES 1.0 Linux and Windows as sources and OES 2.0 Linux as the target. The following scenarios are supported with the script.

1. Migration from NetWare 5.1 or 6.5 to OES 2.0 Server.
2. Migration from OES1.0 Linux to OES 2.0 Linux Server.
3. Migration from Windows NT, 2000, 2003 Server to OES 2.0 Server.
4. Migrating to Server in same Tree or different tree .
5. Supports NSS, NCP and POSIX (except for Windows) as target file system on Destination

Following are the details which you need to know before you start the script.

1. Source Server IP address.
2. Source volume name.
3. Destination volume or directory name where you want to migrate all data.
4. Type of Migration (NSS, NCP, POSIX).
5. Destination LDAP container (if it is a Windows Migration).
6. E-mail id where status of Migration should be sent.

This script uses Migration command line utilities in a particular sequence based on user input to perform Migration job. For example in case of NetWare Migration different tree scenario this script calls the following command line tools in sequence.

1. mls
2. maptrustees
3. migtrustees
4. migfiles

If any point of time during Migration if script fails to perform a particular job then it will send E-mail notification to the user along with the description. It also sends the information regarding when Migration is started and when it has completed. For sending E-mail notifications script uses “sendmail” command.

Using the script for Migration:

Copy the Migration Script to a local directory. Run the Migration script and enter the required details when it prompts.

NetWare Migration sample:

Here is the screen shot which shows Migration in a different Tree scenario:

$:/home/MIGRATION # ./OES2_FSMigration.rb
Enter the Source Server's IP address: 192.168.100.101
Enter the type of Source Server (Netware/OES1.0 (N)/Windows (W)) (N): N
Enter name of the Source volume: FUN
Enter name of the Destination volume: NSSVOL1
Enter the type of destination volume NSS (N), NCP(C), POSIX(P) (C)?:
Enter the mail Id where you want to recieve status:admin@company.com
Enter the username (e.g cn=admin,o=mycompany)
for the server 192.168.100.101: cn=admin,o=novell
Enter cn=admin,o=novell password:
Enter the username (e.g cn=admin,o=mycompany)
for the server 192.168.100.100: cn=admin,o=novell
Enter cn=admin,o=novell password:

Migration started at Thu Nov 15 15:57:03 IST 2007

mls: Collecting user information, please wait...
maptrustees: Mapping Users and Groups, Please wait...
migtrustees: Creating Users on Destination Server, Please wait...
migfiles: Copying files from Source Server to Destination Server, Please wait...
Migration process Completed Successfully at Thu Nov 15 15:57:47 IST 2007 
Windows Migration sample:
Here is the screen shot which shows Migration from Windows Sources:

$:/home/MIGRATION # ./OES2_FSMigration.pl
Enter the Source Server's IP address: 192.168.50.60
Enter the type of Source Server (Netware/OES1.0 (N)/Windows (W)) (N): W
Enter name of the Source volume: data1
Enter name of the Destination volume: NCPVOL1
Enter the type of destination volume NSS (N), NCP(C), POSIX(P) (C)?:C
Enter the destination LDAP container: ou=winusers1,o=novell
Enter the mail Id where you want to recieve status:admin@company.com
Enter the username (e.g administrator)
for the server 192.168.50.60: administrator
Enter administrator password:
Enter the username (e.g cn=admin,o=mycompany)
for the server 192.168.50.61: cn=admin,o=mycompany
Enter cn=admin,o=novell password:

Migration started at Thu Nov 15 16:00:10 IST 2007

migfiles: Copying files from Source Server to Destination Server, Please wait...
ntfsmls: Collecting file attributes and User permissions, Please wait...
ntuserls: Collecting User and Groups information from Source Server, Pease wait...
maptrustees: Mapping Users and Groups, Please wait...
migtrustees: Creating Users and Groups on Destination Server, Please wait...
ntfsmap: Mapping Windows Access rights to NSS/NCP, Please wait...
migrights: Setting file rights on Destination Server, Plase wait...
Migration process Completed Successfully at Thu Nov 15 16:00:10 IST 2007

Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.