migration from netware 6 to netware 6.5

[jrp611]

I have a netware 6.0 sp3 (HP proliant ml330) running groupwise the server is running out of disk space and the company bought a new server with more disk space.
The new server (HP proliant ML350) has netware 6.5 sp5 (OES) installed. the question is I have heard not to migrate a netware 6.0 server to netware 6.5 server is there issue's on that if so then should I run an inplace upgrade to the netware 6.0 server to 6.5 then migrate the server to the new netware 6.5 server.

 

[brichr]

Im not a big fan of the migrate. What about doing a tape backup of the data and restoring it to your new server? How much data are you talking. The backup restore method will keep all your files system rights intact, so it works better than just copying the data.

 

[marvhuffaker]

There's nothing wrong with migrating from 6.0 to 6.5 if you plan correctly and do things correctly. Whether you need to migrate at all is more the issue than anything. If it's a single server implementation, it might be easier to just put both servers in the tree, then move the GroupWise system to the new server.



Marvin Huffaker, MCNE

http://www.redjuju.com

 

[terry712]

i would migrate personally - in some scenario's it is safer than an in place

as marv say though if it's a single server or in deed if grpwise is the only task it does this slap it in
and just copy the grpwise across

 

[jrp611]

Maybe this might help the groupwise server is one of 15 netware servers in the same tree this server holds the mta and poa my other server holds the gwia and webaccess the other servers are used for other programs. I would like to migrate the servers it would save time. is there any thing I should watch when migrating the server.

 

[marvhuffaker]

Technically if you only hold GroupWise on this server and that's it, you wouldn't need to 'migrate' in the traditional sense. You could copy data over and just reconfigure a few things in GroupWise.

But in larger networks where there are more than a few servers, I prefer to do a Migration.

But either way should be fine. Take the appropriate precautions. Health checks, time syncs, replica syncs, etc. Don't assume things will just work, make sure you understand what is happening during the migration process. It can get hairy if it fails and you have to backout.









Marvin Huffaker, MCNE

http://www.redjuju.com