Link to home
Start Free TrialLog in
Avatar of calger
calger

asked on

Moving the GroupWise Message Server

I am preparing to upgrade from Novell GroupWise v.4.1 to v.5.2.  At the same time I will be moving the Message Server from our site in Tampa, FL to our site in Atlanta, GA.  The NLMs will be running on a completely different server - I'm not just moving the hardware - only the modules.

My concerns and questions are these:

1) Can I install the Message Server software on the new server in Atlanta without bringing the Message Server in Tampa down?

2) How do I correctly move the Domain information from one server to the other?  Is it just a simple file copy?

3) I know I will have to redirect each of the POs to look at the new Message Server once it is configured, but are there any other considerations I should be looking into regarding the various POs on the WAN?

I would also appreciate someone sharing information on any other issues that they know about.

Since this is a multi-part question, I'll make the points nice and juicy..... LOL

Craig Alger, MCNE
PC/Network Administrator
Namasco, Corp.
ASKER CERTIFIED SOLUTION
Avatar of elmorec
elmorec

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of calger
calger

ASKER

Can you be a little more specific on the following points?

1) You say "upgrade the primary message" - I assume you mean Tampa.  Upgrade Tampa to v.5.2, then install MS in Atlanta, then convert Tampa to a PO?

2) If I were to just take the whole DOMAIN directory from under the GW directory (where GW is installed) in Tampa and move it to Atlanta should that take care of it?

3) Do you have any experiences that you can relate as to the "wide and scattered" issues?
1. upgrade tampa then come to atlanta and set that server up as a primary message server.  copy the message servers files from Tampa to Atlanta.  Make Tampa a po. point all po's to ms.

2. the files in question are hidden.  Just like bindery files and NDS tree files.  I don't know their names right off the top of my head but you can find out in the gw admin. book.  You need to use an attrib command of some sort to show the files.  once they are visible all you'll need to do is to copy those files from the Tampa MS to the correct location on the Atlanta MS.  Then once that is doone you will need to convert the Tampa server to a PO.  Then you will need to point all the po's to the MS.

3.  Widely scattered problems with the po's.  For instance a common problem is the po not taking to the new message server.  I mean there are other things that can happen as well.  I have some experience in this as I have done it with 4.1 to 5.0  however problems are too scattered and too varied to give too many specifics.  However I am sure I could help you troubleshoot where you need it. just let me know.
Avatar of calger

ASKER

Thanks - all the info was very helpful!