Article

Marcel_Cox's picture
article
Reads:

6878

Score:
4
4
2
 
Comments:

4

Migrating from NetWare to OES2 SP1

(View Disclaimer)

There are a number of documents and articles that explain how to use the OES2 migration tools and especially the new GUI migration tool from OES2 SP1. However all these articles just tell you how to use the tools in “normal” situations, and there is very little troubleshooting information available to help you when things don’t go as expected. Now the truth is that the migration tools as included with the release of OES2 SP1 are still far from robust and you are quite likely to encounter problems when using them.

So the scope of this document is not to give you a step by step guide on how to do migrations. There is the official documentation and a number of other documents that tell cover the various migration steps more than adequately. Instead, this document tries to give you more background information how the migration tools work and interact with each other and what kind of problems you might encounter and how to deal with these problems. It also gives you a number of recommendations that might help you avoid some problems and allow things to go smoother. Be aware that this document is based on the state of the migration tools as they are with the release of OES2 SP1. A number of bugs have already been fixed in the migration tools, but these fixes are not yet available to the public at the moment of writing this document. Of course, the recommendations do not hurt in case where bugs are fixed later on, and it is always better to be safe than sorry.

This document mainly targets the use of the migration tools to migrate from NetWare to Linux, but most of the document should also be relevant for Linux to Linux migrations.

The actual document is a wiki page that is continuously updated and can be found at: http://wiki.novell.com/index.php/NetWare_to_OES2


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.




User Comments

showmeohio's picture

Question / Clarification Please

Submitted by showmeohio on 25 March 2009 - 7:37pm.

I visited your very helpful wiki, but it brought up a question.... the wiki states "*** For ID swap migrations, install the destination server into the same context as the source server. Do not forget to use the "premigration" pattern when configuring OES2 during the installation.***"

During a Netware2Netware migration, you select "premigration" for the destination and install the server and edir into a SEPERATE and TEMP tree.

Is this indicating that a OES/NETWARE to OES/LINUX migration is done within the same tree and context as the source server? Can you clarify this please? Thanks.

Marcel_Cox's picture

Re: Question / Clarification Please

Submitted by Marcel_Cox on 26 March 2009 - 1:12pm.

There are 2 big differences in NetWare to NetWare and NetWare to Linux migrations:

1) In NetWare to NetWare migrations, the destination server is installed with a minimum number of services and most services are only installed after the migration. Services do not need to be converted by the migration as they are mostly compatible between NetWare versions. The install of the new version of a service after the migration takes care of upgrading the configuration for the service.
In NetWare to Linux migrations, all needed services are already installed on the destination server. This is because for the majority of the services, the configuration of the services is very different between NetWare and Linux. Therefore, the migration tools need to translate the settings from the NetWare service to the corresponding Linux service. This can only be done if the corresponding Linux service already exists on the destination server

2) As a consequenece of 1, the destination server must be in the production tree. In fact, many services put at least part of their configuration in eDirectory and many services rely on LUM working. In order not to loose the service configuration, the destination server needs to be in the production tree. However to avoid eDirectory synchronization issues after the migrtation, the destination server must not have a replica installed.

skipthompson81's picture

replica followup

Submitted by skipthompson81 on 18 November 2009 - 9:44am.

i've done this is testing repeatedly. how do i NOT install a replica?
i'm using gui methods....

gldavis's picture

replica followup 2

Submitted by gldavis on 18 November 2009 - 10:37am.

When you select the "pre-migration" pattern on your destination oes2 linux box, it will ensure "no replica" is added.

© 2013 Novell