George C. Lutch

judgedrunkshipServers

Nov 17, 2013 (3 years and 10 months ago)

118 views

November 17, 2013

George C. Lutch

Senior Consulting Engineer


Infrastructure

The Harding Group Inc.

glutch@harding
-
group.com

© Beginfinite Inc, Confidential & Proprietary

2

NetWare to OES2


Migration Best Practices

Trivia


When did NetWare first come out? (Year)



1983


When did Novell start shipping NDS? (Year)


1994


When did Novell acquire SuSE? (Year)


2004





© Beginfinite Inc, Confidential & Proprietary

3

What Services run on OES2 Linux

© Beginfinite Inc, Confidential & Proprietary

4


AFP


Backup (SMS)


Clustering (High Availability)


DNS/DHCP


Domain Services for Windows


eDirectory


CIFS


FTP


iFolder 3.x


NetStorage


Novell Client Access


Management Tools (NRM, iManager, etc)


iPrint


QuickFinder


Novell Storage Services (NSS)

© Beginfinite Inc, Confidential & Proprietary

5

© Beginfinite Inc, Confidential & Proprietary

6

Why go to OES2 Linux:



Performance tests show a 65% or better


improvement over NetWare due to the 64
-


bit kernel.



NSS on NetWare and OES2 Linux are feature


comparable.



iFolder 3.8 is included in OES2 Linux and


not NetWare.



Clustering improvements make the move to


clustered OES2 Linux very appealing.

© Beginfinite Inc, Confidential & Proprietary

7

Why go to OES2 Linux:

(cont)



New tools included in OES2 SP1 and above


for migration and consolidation.



ZENworks imaging is faster from a linux


host.



DST or Dynamic Storage Technology is a


new feature in OES2 and not available on


NetWare.



Xen virtualization is included in SLES.


© Beginfinite Inc, Confidential & Proprietary

8

Why go to OES2 Linux:

(cont)



Domain Services for Windows is included in


OES2 SP1 Linux and above.



The Open Source solutions you have come


to know, Apache, Tomcat started on


Linux.



In 2010 NetWare enters extended support,


hardware vendors will cease to certify it


on new server hardware.



NetWare / OES Support

© Beginfinite Inc, Confidential & Proprietary

9

©
Beginfinite

Inc, Confidential & Proprietary

10

Best practices for new server loads.

These are things I have found that make
loading and managing a new server easier.



New servers with local attached storage


should include a raid controller that can


create multiple logical drives.



Use Local time during load.



Configure NTP source during install.



During software selection make sure to add


“Kernel source” and “gcc” packages.


© Beginfinite Inc, Confidential & Proprietary

11

Best practices for new server loads.



Disable all but the primary NIC in bios. This


will prevent a service from binding to an


unused NIC. You can re
-
enable it after


server load.



The 64
-
bit version of the SLES 10 OS is


preferable to the 32
-
bit as this allows


addressing memory above 3.6 gig. The 64
-


bit version also as stated earlier performs


significantly better.


© Beginfinite Inc, Confidential & Proprietary

12

OES2 Linux migration best practices.




First and foremost, Make backups and verify


them.


Planning


Assess your environment


http://support.novell.com/advisor


Hardware requirements


Training


Setup a lab


Test


Create a Project / Scheduling

© Beginfinite Inc, Confidential & Proprietary

13

© Beginfinite Inc, Confidential & Proprietary

14

OES2 Linux migration best practices.

Continued

Decision Time….. Migration or Consolidation

© Beginfinite Inc, Confidential & Proprietary

15

OES2 Linux migration best practices.

Continued



Migration:



If you need to remain with the number of


servers you currently have either due to


geographic locations or services.




Consolidation:



If you are trying to reduce the number of


servers and combine services on fewer servers.




© Beginfinite Inc, Confidential & Proprietary

16

OES2 Linux migration best practices.

Continued

New tools are available with OES2 SP1 and
better making either decision fairly painless.



Migration Tool Features


Supports several Novell Services migration
in a single Tool


AFP, CIFS,DHCP, File System, FTP, iFolder, iPrint, NTP and
Archive Version


Same Tree, Different Tree


Server Identity Migration (Transfer ID)


Scheduling


Email Notification


Dashboard View

© Beginfinite Inc, Confidential & Proprietary

17

Migration Tool Features

cont


Non
-
destructive migration


Uses different CLIs to perform the
migration

© Beginfinite Inc, Confidential & Proprietary

18

Migration Architecture

© Beginfinite Inc, Confidential & Proprietary

19

OES2 Migration Tools DEMO

© Beginfinite Inc, Confidential & Proprietary

20

© Beginfinite Inc, Confidential & Proprietary

21

Pre migration check of eDirectory


Make sure eDirectory is healthy.



Verify time is sync’d on your servers.



Verify that replicas are in sync.



Run a DSRepair / NDSRepair in unattended mode on all your


servers to verify that eDirectory is healthy.



Check external references on all replica holders.



Make sure you have server to server synchronization.



Verify that there are no hung obituaries.

© Beginfinite Inc, Confidential & Proprietary

22

Some gotchas to watch out for


XEN virtualization is not compatible with NSS.



Adding an OES2 Linux server node to an existing NetWare 6.5


sp8 cluster is doable however some items need to be


considered.


-

CIFS needs special handling.


-

AFP needs special handling.


-

DHCP needs special handling.


-

DNS needs special handling.


-

FTP Doesn’t migrate.


-

iFolder requires special handling.


-

iPrint needs special handling.


© Beginfinite Inc, Confidential & Proprietary

23

Some gotchas to watch out for


-

Once an OES2 Linux server is added to a cluster you cannot


add any more NetWare 6.5 servers to that cluster.


-

Cluster volumes cannot be added without special handling.


-

You can’t change an existing shared pool or volume in a


mixed NetWare OES2 cluster.


-

When trustee assignments are added after fail over, they


will not be picked up by Linux for NCP after fail back


-

The server holding the master eDir replica in the cluster


must be done last.



Novell proprietary SLP doesn’t migrate



If you are upgrading from any NetWare version below


NetWare 5.1 SP8, you will need to upgrade it.


© Beginfinite Inc, Confidential & Proprietary

24

Some gotchas to watch out for

Cont

A couple of great URLS to assist in these
gotchas.


http://www.novell.com/documentation/oes2/clus_admin_lx/?pa
ge=/documentation/oes2/clus_admin_lx/data/ncsconvertnw2lx.h
tml#ncsconvertnw2lx


www.novell.com/communities/coolsolutions/upgradetooes


http://www.novell.com/communities/node/8781/top
-
oes
-
upgrade
-
tids





© Beginfinite Inc, Confidential & Proprietary

25

Questions?

Thank You!