Knowledge Partner
Knowledge Partner
307 views

Migrating a clustered messenger 3.x system?

Oh well. Once  again a what you would think common product and scenario is simply undocumented.

So here it goes: "How do I migrate a NCS Clustered Messenger 3.X system to Messenger 18.1?"

Apart from the documentation mentioning clustering like it is supported, but then *completely* failing to actually document it (I'll get to that later), it seems that in the installer clustering and migration from 3.X are mutually exclusive. At least, when you specify migrating a 3.X system in the configuration, no option for clustering is shown anywhere, and if you try to "manually" do it by specifying the cluster resource IP and shared storage everywhere, the install fails like this:

Error initializing database connection: 0xB407
Failed. Error connecting or authenticating to the database.
Possible causes:
1. User root does not exist.
2. Password for root was entered incorrectly.
3. Database server address [X.X.X.X] and/or port [8320] are incorrect.
4. SSL is not configured on the database server.

Which only adds to the confusion, especially the mentioning of the root user, as it never ever asked for the root password in the first place.

The reason for above seems to be a rights issue on the shared storage, but again, that's not my job to find and debug, as it's not documented.
Also, the arango database itself gets created locally when you specify migration, which is totally not what is wanted in a cluster scenario.

Now, for the documentation:

Here: https://www.novell.com/documentation/groupwise18/messenger18_install/data/t43gnf9mgfxd.html

we find this sentence on Clustering:

"The Messenger agents can be configured to take advantage of the fault-tolerant environment provided by Novell Cluster Services. The installation program adds a /cluster switch to the Messenger agent startup files. This tells the Messenger agents to use the cluster virtual server name."

As for *HOW* the Messenger agents can be configured that way, there is *zero* information anywhere. I so love this type of information that simply leaves you stumped.

However there is also a link "For more information on clustering Messenger, see the GroupWise 18 Interoperability Guide." Maybe that helps, but...

Which again contains *zero* information on clustering Messenger.

Seriously Microfocus...

 

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
Labels (1)
7 Replies
lelle Valued Contributor.
Valued Contributor.

Re: Migrating a clustered messenger 3.x system?

Hi,

Only want to say I have been there, gave up on migration since it not working and are completely undocumented, did set up a new clustered system (witch more or less i undocumented to)

Same thing with update/upgrade a messenger 18 to 18.1 in a cluster environment

/Lelle

0 Likes
Knowledge Partner
Knowledge Partner

Re: Migrating a clustered messenger 3.x system?

Oh well:

https://www.novell.com/documentation/groupwise18/gw18_bugfixlist/messenger18_1_sp1_bugfixlist.html

"B-130660 - Disabled cluster configuration."

 

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
lelle Valued Contributor.
Valued Contributor.

Re: Migrating a clustered messenger 3.x system?

Hi,

well it hard to know what that means?

Is cluster setup not supported anymore or does it mean that you have to enable it yourself

/Lelle

0 Likes
Knowledge Partner
Knowledge Partner

Re: Migrating a clustered messenger 3.x system?

*That* is a 64 million dollar question. The documentation says it can be clusered, so does that mean it's supported?

Let me try to get an official answer here.

 

 

 

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
lelle Valued Contributor.
Valued Contributor.

Re: Migrating a clustered messenger 3.x system?

Hi,

 

I did open a SR to find out, according to support now seup and updated will not be installed in a cluster config.

I is related to issues with corruption in ArrangoDB.

Suggestion is not to cluster Messenger if you have a cluster setup allready

/Lelle

0 Likes
Knowledge Partner
Knowledge Partner

Re: Migrating a clustered messenger 3.x system?

I know, I had a SR open too, but didn't want to post the full details publicy.

But hey, who needs high availability... <shrug>

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

Re: Migrating a clustered messenger 3.x system?

This is an error in the documentation that I will have corrected.    The database system in use does not support clustering and so Messenger 18.x does not support clustering at this time.  That is why there was no documentation.   We plan to move Messenger into docker containers,  the database supports clustering in that environment.    Look for that in an upcoming release.

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.