Absent Member.
Absent Member.

Moving GroupWise Systems

Hi all,

I've got this scenario-
Remote site- GW7 running on Netware 6.5. Secondary GW Domain. 15 GB Post Office
Head office- GW8 running on OES Linux. Primary GW Domain.

We want to get rid of servers at the remote site and move their GW mail to the Head office. Would this be a good plan to make this happen:
1. Upgrade the Remote system to GW8.
2. Use DBCopy to copy PO to the OES Linux server (using Migration option).
3. Cut over and do a final DBCopy of Post Office and DBCopy over the Secondary Domain DB.
4. Edit the PO and Secondary Domain info in C1 making the POA object run on port 1678 so we can use the same IP.
5. Reconfigure the Secondary Domain to use the existing GWIA and WebAccess. We have DataSync running currently on the PO in the Primary Domain. I assume the SOAP connections will allow for connections to this PO in Secondary Domain.

Would it be better too if after moving the GW system to the Head office to move the PO from the Secondary Domain to the Primary Domain and get rid of the Secondary Domain? If so, what's the best way to do this?

Thanks in advance
Labels (2)
1 Reply
Knowledge Partner
Knowledge Partner

In article <vpoon.5q1x1z@no-mx.forums.novell.com>, Vpoon wrote:
> We want to get rid of servers at the remote site and move their GW mail
> to the Head office.

Another option to consider is to move users directly to the primary
PostOffice. Depending on your site to site bandwidth and the size of the
users mailboxes, some nights you might only migrate one user, others
could be bunches. Just upgrade that remote system first so they are both
to a common current patch level and that both systems have had a decent
health check done.

On first blush your proposal looks doable, though more of a do or die
weekend than the above option. I've never done that type of
consolidation, so I don't have any direct experience to go by.
Step4, you'd also have to do the same for the MTA ports

Either way, this would also be a good time to find who has the big
messages and make sure they are actually needed or deleted.

Your remote sites might benefit from caching mode with losing there local
server. Also will help make the migration a bit more transparent.

And make sure you're existing system has plenty of resources, drive and

Andy Konecny
Knowledge Partner (voluntary SysOp)
KonecnyConsulting.ca in Toronto
Andy's Profile: http://forums.novell.com/member.php?userid=75037

“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.