Absent Member.
Absent Member.
2871 views

Migration from Groupwise 8 to 2014R2 plan verification

I need to migrate a Netware-based GroupWise 8 system to SLES-based GroupWise 2014R2.

I had previously done a similar migration by installing a new SLES GroupWise 2014 server and doing a dbcopy from the Netware NSS volume to the SLES EXT3 problem, to avoid having to do the intermediary steps of using the Migration Tool to migrate to GroupWise 8 from Netware to SLES, then upgrading GroupWise 8 to GroupWise 2012 before finally upgrading to GroupWise 2014R2, as the documentation recommends:
f you need to upgrade from an older GroupWise version, you must upgrade at least to GroupWise 8, and preferably to GroupWise 2012, in order to ensure that your GroupWise data is compatible with the upgrade process that is provided in GroupWise 2014.


I'm thinking that a better route might be to install GroupWise 2014 on Windows and simply do a restore of the GroupWise 8 email volumes to the Windows volumes so I can go directly from Netware-GroupWise 8 to Windows-GroupWise 2014R2 in "1 step", *then* use the migration tool to migrate from Windows-GroupWise 2014R2 to SLES-GroupWise 2014R2. It seems to me this may be a more direct route with the least chance of issues along the way.

Can anyone affirm that this is a reasonable/good procedure, or know reasons why it would *NOT* be recommended to do it this way?
Labels (1)
0 Likes
19 Replies
Absent Member.
Absent Member.

Answer from Novell support:


You can go straight from netware to linux. If you follow that TID , the only thing you will have to change is the type of mount from ncp to a samba mount. Once you transfer the data you can then proceed with the install of the software on the new box and continue the upgrade. But you don't have to go from gw8 netware to gw8 sles.

0 Likes
Absent Member.
Absent Member.

There is one big caveat! Make sure that on NetWare you change the PO link to TCP/IP if it's currently direct. This is one thing that is very difficult to "fix" once you get to Windows on GW 2014. But yes, otherwise, one step is no problem.
0 Likes
Absent Member.
Absent Member.

Whew! Good to know! Thank you! You might have saved the day with that tidbit!
0 Likes
Micro Focus Expert
Micro Focus Expert

Hi,

Don't forget the file/folder case sensitivity issue between NetWare and Linux if you go to a Linux based OS such as SLES or OES.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Commodore
Commodore

Don't go with 2014 R2. Read the Agents forum to see all the issues you will get. WebAccess has problems reported as well.
start at version 2104. wait for R2 to get stable.

I updated our 2014 system to R2, two weekends ago.
R2 has crashed (post offices) more the past two weeks than previous versions combined for the past 10 years.



bkeadle;2422375 wrote:
I need to migrate a Netware-based GroupWise 8 system to SLES-based GroupWise 2014R2.

I had previously done a similar migration by installing a new SLES GroupWise 2014 server and doing a dbcopy from the Netware NSS volume to the SLES EXT3 problem, to avoid having to do the intermediary steps of using the Migration Tool to migrate to GroupWise 8 from Netware to SLES, then upgrading GroupWise 8 to GroupWise 2012 before finally upgrading to GroupWise 2014R2, as the documentation recommends:


I'm thinking that a better route might be to install GroupWise 2014 on Windows and simply do a restore of the GroupWise 8 email volumes to the Windows volumes so I can go directly from Netware-GroupWise 8 to Windows-GroupWise 2014R2 in "1 step", *then* use the migration tool to migrate from Windows-GroupWise 2014R2 to SLES-GroupWise 2014R2. It seems to me this may be a more direct route with the least chance of issues along the way.

Can anyone affirm that this is a reasonable/good procedure, or know reasons why it would *NOT* be recommended to do it this way?
0 Likes
Commodore
Commodore

new public hot patch for 2014 R2 was just released this afternoon, so I would advise waiting to see if that fixes the problems everyone has been experiencing.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Am 23.03.2016 um 01:46 schrieb ShootDawg:
>
> new public hot patch for 2014 R2 was just released this afternoon, so I
> would advise waiting to see if that fixes the problems everyone has been
> experiencing.


Just for what it's worth: I don't deny those issues, really. But it's
*not* everyone. I have customers with several hundred users running on
R2 for months without any POA crashes.

U,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Micro Focus Expert
Micro Focus Expert

Hi,

I must agree with Massimo - I've run R2 since it's release date and not experienced any crashes.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Commodore
Commodore

ShootDawg;2423617 wrote:
new public hot patch for 2014 R2 was just released this afternoon, so I would advise waiting to see if that fixes the problems everyone has been experiencing.


The two issues I was experiencing have been resolved for our systems with HP1.
0 Likes
Absent Member.
Absent Member.

I wanted to verify something about the second/final copy when doing a migration. I seem to recall when I did this before, I had everything configured in my new GW2014 environment, and then when I went to cut over, I did the secondary copy, and then when I went to the GroupWise Administration page, I got an unexpected Installation Authorization page, presenting me with an Install/upgrade. Is that normal? When I do the dbcopy -m -s, will that overwrite the 2014 configuration dbs? Do I need to "upgrade" the databases again?
0 Likes
Micro Focus Expert
Micro Focus Expert

Hi,

Yes it will copy across your wpdomain DB's for the domain, and the post office db files etc. Run the upgrade again to upgrade these db's.

Note for future: Do not start your GW2014 agents until after your final copy and then do the upgrade - not the other way around.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
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.