fribert Absent Member.
Absent Member.
753 views

Deep trouble, mixed versions on system after botched upgrade

Ok, so I've gotten into a real mess here.
I have the GW servers virtualized on a KVM type server (QNAP fw 4.3.5).
So I was running GW 14.2.2.
I did a snapshot before attempting to update to GW 18.
The update went fine, but darned, the license I have doesn't currently cover GW 18, so I thought no problem, I'll just revert to before the snapshot.
BUT, the snapshot feature malfunctioned when rolling back, my guess is that it rolled back disc 0, but not disc 1 (GW datastore).

So now I have a mixed system, part of it is 14.2.2, the other is 18, the webaccess didn't work, the GMS didn't work.
The webaccess didn't want to log in 'not compatible with po'.
When looking in the monitors for the agents they all said Groupwise 18, but I could see that the db's where still at 1420
So after fiddling a bit, and activating external support for the KVM like system to make them roll back properly, I noticed that they had started the agents, which now fed mails into groupwise folders, OH NO.
Now I can't roll back, then I'll loose 2 days of mail.

Looking at the domain and po folders, the .dc files are not updated, and the databases are still 1420
I decided to install 14.2.2 again, on top of 18.
All the agents are now back to 14.2.2, the webaccess is working again, the GMS can log in as well, so far so good.

Now the only thing that is odd, is that if I start the groupwise administration console, it still says 18???
What on earth is that now?
How do I get that fixed, so that will also install as a 14.2.2? Will I get in trouble if I modify anything with a GW18 administration console on a GW14.2.2 system (apart from licensing issues which I can't figure out in that case).
Labels (1)
Tags (3)
0 Likes
3 Replies
Knowledge Partner
Knowledge Partner

Re: Deep trouble, mixed versions on system after botched upgrade

fribert wrote:

>
> Ok, so I've gotten into a real mess here.


Yes, that seems to be the case.
It's a good thing you have a backup! 😉

> I have the GW servers virtualized on a KVM type server (QNAP fw
> 4.3.5). So I was running GW 14.2.2.


It's nice to know it will run on a QNAP device but that is not one of
the supported virtual environments!

> I did a snapshot before attempting to update to GW 18.
> The update went fine, but darned, the license I have doesn't currently
> cover GW 18, so I thought no problem, I'll just revert to before the
> snapshot.


What license do you have and what is GroupWise complain about? It's
very unusual for GroupWise to complain about a license.

> BUT, the snapshot feature malfunctioned when rolling back, my guess is
> that it rolled back disc 0, but not disc 1 (GW datastore).
>
> So now I have a mixed system, part of it is 14.2.2, the other is 18,
> the webaccess didn't work, the GMS didn't work.
> The webaccess didn't want to log in 'not compatible with po'.
> When looking in the monitors for the agents they all said Groupwise
> 18, but I could see that the db's where still at 1420


The documentation describes how to do an upgrade...
After you install the software you upgrade the domain, then the post
office. If the database was still showing 1420 then it wasn't upgraded
(yet).

> So after fiddling a bit, and activating external support for the KVM
> like system to make them roll back properly, I noticed that they had
> started the agents, which now fed mails into groupwise folders, OH NO.
> Now I can't roll back, then I'll loose 2 days of mail.


This is where you take another backup, just in case...

> Looking at the domain and po folders, the .dc files are not updated,
> and the databases are still 1420
> I decided to install 14.2.2 again, on top of 18.
> All the agents are now back to 14.2.2, the webaccess is working again,
> the GMS can log in as well, so far so good.
>
> Now the only thing that is odd, is that if I start the groupwise
> administration console, it still says 18???


What still says 18?

> What on earth is that now?
> How do I get that fixed, so that will also install as a 14.2.2? Will I
> get in trouble if I modify anything with a GW18 administration console
> on a GW14.2.2 system (apart from licensing issues which I can't figure
> out in that case).


What OS/version/SP are you running on?

How can you be sure you don't have a mixture of GW 14 and GW 18
components installed?

It looks like you have a bit of work to do. I would start with the
documentation:
https://www.novell.com/documentation/groupwise18/

--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
fribert Absent Member.
Absent Member.

Re: Deep trouble, mixed versions on system after botched upg

Yes, I've never seen a license problem before, but with 18 it shows it, so I decided to go back to 14.
I know it's not a supported VM, but that is not the issue at hand here, it's the cause.
I do have backups, but then I'll loose even more emails, because the agents were started.
So I was fortunate that the databases didn't get updated by themselves and I'm well aware of the procedure of how to update them, it's only in the last 3-4 years I haven't worked professionally with GW, now it's a hobby project to keep up the skills.

It's only the administration console that says 18 when I start it, everything else is at 14.2.2.
I'm pretty sure, the openmotif is also rolled back.

The OS is

po:~ # cat /etc/*release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 3
LSB_VERSION="core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64"
Novell Open Enterprise Server 2015 (x86_64)
VERSION = 2015
PATCHLEVEL = 0
0 Likes
Knowledge Partner
Knowledge Partner

Re: Deep trouble, mixed versions on system after botched upgrade

fribert wrote:

>
> Yes, I've never seen a license problem before, but with 18 it shows
> it, so I decided to go back to 14.


What is the error you receive? If GroupWise 18 complains, it would seem
that issue needs to be dealt with before you can attempt another
upgrade.

> I know it's not a supported VM, but that is not the issue at hand
> here, it's the cause.
> I do have backups, but then I'll loose even more emails, because the
> agents were started.
> So I was fortunate that the databases didn't get updated by themselves
> and I'm well aware of the procedure of how to update them, it's only
> in the last 3-4 years I haven't worked professionally with GW, now
> it's a hobby project to keep up the skills.


Fair enough, as long as you are aware of the risks!


> It's only the administration console that says 18 when I start it,
> everything else is at 14.2.2.
> I'm pretty sure, the openmotif is also rolled back.


That would suggest that some remnants of GroupWise 18 may still remain.


> The OS is
>
> po:~ # cat /etc/*release
> SUSE Linux Enterprise Server 11 (x86_64)
> VERSION = 11
> PATCHLEVEL = 3
> LSB_VERSION="core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-
> x86_64:core-3.2-x86_64:core-4.0-x86_64" Novell Open Enterprise Server
> 2015 (x86_64) VERSION = 2015
> PATCHLEVEL = 0


Your OES is quite out of date. Not only should you upgrade to OES 2015
SP1 plus the latest patches but this is also a requirement before
upgrading to GroupWise 18.

I suggest you first determine what the issue is with licensing, then
patch your system, run the necessary checks on your GroupWise 2014
databases to insure they are healthy and, finally, attempt the upgrade
once again.

--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
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.