(probably) The last GW8 Netware Server in NYC Query

i think GW8 on Netware is similar to an iPhone -- it just works! But now i'm being forced to migrate to gw2014 on Linux its about time. Environment: 40 users, 1 domain, 1 post office 1 gwia 1 webaccess. I had gwava 4 on this box but gwava has since been moved to their linux appliance.

Using Danita's Move guide (for GW2012) and some other internet sources like (http://www.slideshare.net/NOVL/migrating-novell-groupwise-to-linux) I did the following in a isolated Test vm environment:

1) installed new suse sp3 server ( 1 IP address)
2) ncp mounted to netware
3) dbcopy Domain and PO (tested 4 times with agents shutdown. average time 6h 2 min)
4) installed gw2014 on linux box
5) choose upgrade an existing domain
6) then, choose upgrade an existing PO
7) did not migrate any other agents
8) create new gwia
9) Issues with spinning wheel so upgraded to gw2014sp1
10) all good. one account with 20k emails works ok. As admin: I can add a new user, delete a user. Users can transfer mail between users MTA works -- no problem.

Q1: What problems should I be looking out for?

My production system will have gwava (192.168.1.4) on the frontend (appliance) pointing to the old gw8 server (192.168.1.5). When I unload the agents to perform the migration Gwava will hold incoming emails in a queue. The new linux will hold a temporary IP address (192.168.1.6) during the migration. Post migration I wish to change the linux box to the assume the gw8 IP so Gwava and the user clients can find it.

Q2: Is changing the linux server IP post setup okay? Will any certs be affected?

So, I'm thinking i should build this system with an incoming and outgoing GWIA. I'm also thinking about re-adding webaccess.

Q3: How exactly is this incoming and outgoing gwia gateways done? A secondary domain with another vIP on .5?

Q4: How about the new webaccess? A second secondary domain with another vIP on .5?

The final reason i'd like to change the linux IP post migration is that I also have datasychronizer and a blackberry BES thrown into the mix.

Q5: Any concerns now?

Thanks
BTW I Love my blackberry
  • I just did this last month.
    I was foolish enough to perform the whole job in one shot; over the President's Day weekend.
    The two biggest issues I ran into were related to LDAP and password policies.


    The short version:
    If you have the luxury of doing the upgrade at your own pace, I would do it in stages.
    Additionally, if your storage architecture utilizes SAN arrays, it can be used to an advantage when it comes to the migration of the PO data.

    The two biggest issues I ran into were related to LDAP and password policies.
    How this affects you will depend on whether or not you still use NetWare for other purposes; specifically data storage.

    Due to time constraints, I cannot go into more depth at this point, but if you wish, I will provide more details later tonight.
  • Can you give a few more details on your present system?
    Is your network providing storage resources for your users (home folders, shared data, etc..)?
    Is NetWare the only platform you currently have running? If not, what other platforms?
    Do you have an internal DNS server running on your system?
  • EBSR PARAMEDIC wrote:

    > Using Danita's Move guide (for GW2012)


    I hate to suggest such a thing, but we do have a specific guide for moving from
    NetWare to GW2014, and it goes over a lot of gotchas! Sounds like you have
    managed to get it working though, but I wanted to mention it in case someone who
    doesn't have the 2012 guide thinks they need THAT one to upgrade to 2014 :-)

    Q2: It's possible to change the IP address, but for me I would actually just
    add the old address as a secondary. As you point out, the server certs would be
    invalid. This isn't a HUGE issue on SLES, but honestly, if you add the
    secondary IP address now, in the future if you ever need to bring up a
    "temporary" server in a pinch, you can easily just "move" the GW IP address
    there. The only possible downside to this is the GWIA. It will listen on the
    secondary, so GWAVA will find it easily, but no matter what it listens on, it
    "sends" on the primary. Thus, you might have to adjust outbound firewall rules
    to allow sending by the new server.


    Q3 - I think that's just a continuation of the discussion for Q2 above.

    Q4 - webaccess no longer requires a domain. There is no WebAccess gateway any
    longer. For that though, if the webaccess server moves to a different server,
    you might need to open firewall ports between the GW server and webaccess (if
    there is a firewall). WebAccess needs to have access to ports 7191, 8301 and
    8400 on the GW server.


    Hope that helps.

    --
    Danita
    Novell Knowledge Partner
    Are you a GroupWise Power Administrator? Join our site.
    http://www.caledonia.net/register

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...
  • And port 8500 to the POA for autorefresh.
    Even with those ports open, we ran into communication issues that were only solved be disabling the SUSE firewalls.
  • gathagan wrote:

    > And port 8500 to the POA for autorefresh.


    Yeah - that's what I meant - typo! Port 8500, not 8400 :-)

    --
    Danita
    Novell Knowledge Partner
    Are you a GroupWise Power Administrator? Join our site.
    http://www.caledonia.net/register

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...