migrate to new server same License 1

[rouse01]

I have two servers, one is a fully patched 4.1 and the other runs NW5.0. I've got the upgrades for each to nw 4.2 & 5.1 respectively - each with 50 user license that I've not activated yet. My 4.1 svr is about to die.

I wanted to do a server swap to new box from the old 4.1 using the 4.2 upgrade, but the new server doesn't have driver support for the raid controller. BUT the new server does support 5.1 & the current 5.0 server supports 4.2.
So I'm looking at migrating the 5.0 server to 5.1 on the new box & replacing the old 4.1 server with 4.2 on the 5.0 box. I've done a tenative install of 5.1 on the new server w/o the license (complains about that) but the drivers work fine.

I've been prowling for info on server swaps using the same license for upgraded OS on different machines. I need to keep the server names the same as they were. Anybody had experiance with this? Should I setup the new server in a new tree, then move the volumns over?

Thanks in advance...
Keith

 

[Provogeek]

Research how to use the Novell Migration Wizard.

Remember, 4.2 is no longer supported by Novell, so if you run into problems, you will need to do a lot of research and explain your issues very clearly in these forums to get help.

This will be an across the wire migration. The new server should have a basic load of NetWare 5.1. You can install using the SP6 overlay CD, or you can install SP6 after installing 5.1 You can install uisng your 5.1 license, it is different than the 5.0 license, and will work together (your just legaly obligated to bring the 5.0 server off line, there is no technical reason to stop you from using both). The new server will have a dummy name, dummy tree and dummy context. Volumes MUST be the same name as the old server, but everything else is a dummy name.

The migration wizard will be four steps. The first will migrate files, you must have an admin login and you must be using the same line protocol on both servers. The second will give you the chance to edit config files. The thrid will migrate the NDS database, in turn, it will do a brain transplant of the server. You will see both servers go down, only the old server will not come backup. The new server will come backup and assume it is the old server, same name and all. The fourth step restores trustee assignments to all the volumes.

You can use migration wizard 6 for the 5.0 to 5.1, but for 4.1 to 4.2, you will need to use the MW v3 (avoid 4, not sure what happend to 5). Again, the 4.1 and 4.2 license will not conflict if you have both on line. Again, the new 4.2 server load will be a dunny name and tree in prep for the migration.

I have not done a 4.1 to 4.2 migration, not sure if it will even work. You may need to just to a hardware upgrade (backup data from old server, backup NDS database to DOS partition, do basic load on new server with same name and internal IPX ID, restore NDS database, restore data), it's a long and pain in the rump project, but it works.

Remember, 4.2 is only 4.1 with SP8a applied to it (if you can even say it's pre-applied, cause it's not). You will still need to install SP9 and update NDS.

Avoid bring your 5.1 server to NDS v 8, the install does 8 by default, but you can choose to use 7 instead. You should continue to use 7 until you can get rid of NetWare 4. NDS 6 that runs on 4 has issues with attributes in NDS 8.

 

[rouse01]

That's what I was looking for. Thanks!