NetWare migration NetWare to OES2 SP1

From SEPsesam
Jump to: navigation, search
Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.

Copyright © SEP AG 1999-2018. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

System Requirements

Linux OES 2 SP1 and NetWare 5.x / 6.5 with all current patches

Attention
NetWare 5.x / 6.5 not longer supported by Micro Focus (former: Novell)
Note

At this time (2008.07.25) it is known that by the migration from NetWare to OES 2 the owners of the files will be overwritten with the owner of the server Objects NDS Trees. If the re-assignment to the original owner is indispensable, there is a service patch needed. This patch must be requested from Novell.

Configuration Steps

Restore an OES Netware backup onto an OES Linux system

Caution!

To restore a backup type OES Netware onto a OES Linux system a SEP sesam Server version 3.4.1.27 or higher is necessary!

By default, after the selection of the restore task on page "Start" in the restore wizard only hosts with the same operating system platform are offered. That means only OES Netware hosts will appear in the field "Target Node". To make it possible to restore this host backup to a OES Linux host you have to activate this with a Sesam database entry.

Before you execute the database command, you should set the SEP sesam profile. Now you can execute the sm_db command line.

sm_db "update task_types set flags='os_indep', protection='A' where backup_type='NetWare'"


In case of SEP sesam 4.0:

sm_db "update task_types set flags='os_indep', protection='A' where backup_type='NSS File System'"

After that you can select also OES Linux systems as "Target Node" in the restore wizard (see the example in the figure below, there is the OES Linux host "oesnix1").

Selection of platform independent hosts in the field "Target Node"

Linux OES 2 SP1 with TSAFS in dual mode

The TSAFS must be started in dual mode. Then both the "Linux file system" and the "NetWare File System" is provided for NSS volumes. In case of a migration customers often continue using programs and scripts with NetWare pathes. With the dual mode these programs and scripts can be used without modification.


Execute:

Temporary set with

 #> / Opt / novell / sms / bin / smsconfig-u tsafs
 #> / Opt / novell / sms / bin / smsconfig-l tsafs - = dual tsaMode

Make a lasting configuration in file / etc / opt / novell / sms / smdrd.conf " with entry autoload: tsafs - = dual tsaMode and restart the smdrd daemon:

 #> Rcnovell-smdrd restart

Effect:

Then, while browsing both file systems NetWare.Linux and NetWare.NetWare are displayed. E.g. NSS volume / media/nss/VOL1 under NetWare.Linux file system

  --> Media
    --> NSS
      --> VOL1

will also be shown under NetWare.NetWare file system as -> VOL1:.


Include Linux OES 2 client as a Linux system

The Linux OES 2 client must be included as a Linux platform in the GUI.

Execute:

Include in GUI. Specify user and password for SMS access.

Effect:

In the Restore Wizard, the client with platform Linux is provided as a target pc for the migration.


Include a NetWare client

The NetWare server intended for the migration must be included as a NetWare client with platform NetWare in the GUI.

Execute:

Include NetWare client in GUI with platform NetWare. Specify user and password for SMS access. Specify an appropriate DataMover OES client, e.g. the OES client with the previously established Linux platform. Of course - if the SEP sesam server itself is an OES system - it can also be indicated.

Effect:

The NetWare client is ready for backup.

Configuration of NetWare backups

For backing up the NetWare system select the volumes with the data for the migration.

Execute:

Define a task in the GUI per NSS volume for the NetWare client. Alternatively, a task for all volumes by specifying multiple volumes as source.

Effect:

The sources are defined.


Run NetWare backups

It should happen at minimum one successful backup per task.

Execute:

Start one backup per NSS volume in the GUI, for example under "Immediate start -> Backup. Choose a pool with the appropriate capacity.

Effect:

Volumes are backed up to the medias of the pool.


Make NSS volumes available on Linux OES2

Check if adequate NSS volumes are available on the target system Linux OES 2, mounted as NSS volumes and have the necessary capacity. If existing NetWare programs should continue running *without* path adjustments, it is necessary to specify an identical volume-name.

Execute:

Finding a mounted NSS volume

With

 #> mount

all currently mounted volumes and their access modes are displayed.

Example:

mount
/dev/sda2 on / type reiserfs (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/hdc on /media/cdrom type subfs (ro,nosuid,nodev,fs=cdfss,procuid,iocharset=utf8)
/dev/fd0 on /media/floppy type subfs (rw,nosuid,nodev,sync,fs=floppyfss,procuid)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/evms/NSS_POOL on /opt/novell/nss/mnt/.pools/NSS_POOL type nsspool (rw,name=NSS_POOL)
/dev/evms/VOL1 on /opt/novell/nss/mnt/.pools/VOL1 type nsspool (rw,name=NSS_POOL)
admin on /_admin type nssadmin (rw)
NSS on /media/nss/NSS type nssvol (rw,name=NSS,norename)
VOL1 on /media/nss/VOL1 type nssvol (rw,name=NSS,norename)

In the example, the NSS volumes 'NSS' and 'VOL1' with acces modes 'rw, name = NSS, norename'are displayed. If necessary appropriate NSS volumes must be configured in accordance to the Novell documentation.

Show capacitys of the NSS volumes

With

# df -h

the available capacitys are displayed in readable form.

Example:

# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda2             5.1G  3.2G  1.9G  63% /
tmpfs                 252M   12K  252M   1% /dev/shm
/dev/evms/NSS_POOL    499M   15M  485M   3% /opt/novell/nss/mnt/.pools/NSS_POOL
admin                 4.0M     0  4.0M   0% /_admin
NSS                   499M  3.8M  485M   1% /media/nss/NSS
VOL1                 82.0G  3.8M 81.6G   0% /media/nss/VOL1


Effect:

The target volumes are available.

Migrate NSS volumes on Linux OES 2

Start a restore task for every backup task you made to the corresponding OES 2 Volume.


Execute:

Start a complete restore for every task in the GUI Restore Wizard, specify Linux OES 2 server as the target-system and set the prepared NSS volume as target with the according 'Linux File System'identifier, such as '/ media/nss/VOL1'.


Effect:

The data is now available on Linux OES 2.


Done.


After that, the NetWare system can be turned off and the Linux OES 2 server can possibly be renamed. Don't forget to adapt accordingly in the SEP sesam GUI.