Highlighted
Absent Member.
Absent Member.
742 views

Confused on Upgrading to Enterprise Messaging

So I have a server running Groupwise 2014 R2 and have in my portal the upgrade to Groupwise 18. I also happen to own Reload 5 installed on its own server. I want to upgrade to the Enterprise Messaging to get Teams and Messenger, and I understand that Reload is now a part of that (as Groupwise Disaster Recovery). In trying to plan for all this, what I can not seem to find out is:
1) Do I have to stage a new server for Groupwise, and separate servers for Teams, Messenger and Reload/Disaster Recovery?
2) Will Teams run on Linux virtualization since I don't own VMWare or run Windows servers. Also I think that Teams is a virtual appliance.
3) I have eDirectory on my Groupwise server (talking to my production OES server) and plan on keeping that. Can I also put eDirectory on say, the Disaster Recovery server?


My user count is less than 44, but some of their mailboxes are large and they'll probably spend a ton of time messaging (they use the old Novell Send Message still and it's always on/always in use for many people). Teams will only be used by about 15 people in the company.

Can anyone shed some light for me here? The documentation isn't helping me.

Many thanks!

Val

GW 2018 & Mobility Service-Version: 18.1.0 Build: 410 on SLES 12SP3, GW Client 18.02 (Build 131493) on Windows 7 64bit; server OES 11 on SLES 11 SP3; eDirectory 9.1 on SLES12SP3 and eDirectory 8.8sp8 on SLES11 SP3
Labels (1)
0 Likes
4 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: Confused on Upgrading to Enterprise Messaging

In article <iliadmin.8iptpb@no-mx.forums.microfocus.com>, Iliadmin wrote:
> So I have a server running Groupwise 2014 R2 and have in my portal the
> upgrade to Groupwise 18. I also happen to own Reload 5 installed on its
> own server. I want to upgrade to the Enterprise Messaging to get Teams
> and Messenger, and I understand that Reload is now a part of that (as
> Groupwise Disaster Recovery).


The GroupWise in Enterprise Messaging is the same as regular GroupWise,
same code, and in the future will just be licensing differences to
activate Enterprise Messaging features that are built in, or at least that
is what the roadmap has been.
So
1) is the same upgrade as to regular GW18, in-place works just as well.
Reload really should be on a separate physical system since that is the
point of disaster recovery. Messaging run on SLES12 or OES2018, so is that
what your GroupWise is running on?

2) TeamWorks comes as a prepackaged vm (plus needed some NSF storage), and
at this point only for on ESXi. What you could do is get the free base
ESXi for one box for those systems that only come that way. You could use
that to run the systems or look at some of the migration options (such as
PlateSpin Migrate) to VtoV to your unspecified chosen hypervisor. Perhaps
this box might also host your Disaster Recover?

3) Since Reload runs on SLES and SLES is a supported eDir platform, yes
you can run it there.

Hope this sheds some light

Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
“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!
Highlighted
Absent Member.
Absent Member.

Re: Confused on Upgrading to Enterprise Messaging

Thanks, Andy. Yes, we run GW on SLES (upgrading to sles 12 on a new box), and Reload also with SLES (same, upgrading it to 12) on its own box. So it sounds like I can run the Messaging on my new GW box...? Is it a resource hog? I will look at the free base ESXi version, not really familiar with this at all. Good to know I can put eDir on the Reload box.

Thanks!!

Val

GW 2018 & Mobility Service-Version: 18.1.0 Build: 410 on SLES 12SP3, GW Client 18.02 (Build 131493) on Windows 7 64bit; server OES 11 on SLES 11 SP3; eDirectory 9.1 on SLES12SP3 and eDirectory 8.8sp8 on SLES11 SP3
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Confused on Upgrading to Enterprise Messaging

In article <iliadmin.8j6kun@no-mx.forums.microfocus.com>, Iliadmin
wrote:
> it sounds like I can run the Messaging on my new GW box...? Is
> it a resource hog?


I believe that combination will work. As all my clients have at least
some virtualization platform, it is just easier to keep the functions
separate to assist in any troubleshooting or DR issues.
I haven't see Messaging be much of a resource consumer, but I don't
have any heavy hitters using it yet.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
“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!
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: Confused on Upgrading to Enterprise Messaging

iliadmin;2482819 wrote:
Thanks, Andy. Yes, we run GW on SLES (upgrading to sles 12 on a new box), and Reload also with SLES (same, upgrading it to 12) on its own box. So it sounds like I can run the Messaging on my new GW box...? Is it a resource hog? I will look at the free base ESXi version, not really familiar with this at all. Good to know I can put eDir on the Reload box.

Thanks!!

Val


Although eDir can certainly be added to your reload box, I'd suggest avoiding that, as it complicates matters if the reload box goes belly up or needs to be replaced with newer hardware.
I can't think of any advantage that adding eDir to your reload server provides.
If you just want another replica of your eDir partitions in your tree and you end up rolling out the free ESXi host, you could create another minimal OES server whose sole purpose is hosting the replica(s).
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.