Highlighted
Absent Member.
Absent Member.
1391 views

GroupWise 2014/eDirectory In DR/BC Configuration

Hi all,

Right now we have a couple sites using GroupWise 2014 on OES11. The servers have NSS volumes and the GroupWise users are associated with an eDirectory account. Also, our main site uses eDirectory for the Mobility server (users are provisioned using LDAP group in eDirectory) and Novell Messenger. These servers all run on VMware ESXi hosts. We currently back up the VMs using Veeam Backup and Replication. I've been reading that eDirectory doesn't restore well using Veeam with Snapshot backups. Also, it sounds like I'm asking for trouble if I use eDirectory with Veeam replication if we fail over to a DR site.

So in order to use GroupWise in a DR/BC configuration with Veeam and fail over to a DR site, I'm thinking I'll need to do some reconfiguration to minimize problems with eDirectory. Should I do the following-
1. Add another hard disk onto the GroupWise server and migrate the data off the NSS volume onto the EXT3 partition and reconfigure GW for the new location.
2. Disassociate the users/objects in GroupWise from eDirectory. Eventually I'll associate the users in GW to Active Directory.
2. Remove eDirectory from the GroupWise server but keep eDirectory on a different server for the Messenger and Mobility users.

In essence, I'm getting rid of eDirectory/NSS volumes so I can eliminate problems when failing over and failing back to/from a DR site.

Does anyone else have some insight into this situation?

Thanks
Victor
Labels (1)
0 Likes
5 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Hi.

eDirectory is a database, and just like every other database that gets
written to more or less regularly, a backup using snapshots *can* be
problematic, but doesn't have to. First, the database itself might be in
an inconsistant state at the moment of the snapshot, and will not
open/work at all after a restore like this.

Of course, eDirectory also is a replicated database over multiple
servers using timestamps to make sure information between servers is
proper and identical. That adds another layer of *possible* problems,
when suddenly one of the involved databases jumps backward in time.

All this is true however for every similar database, *especially* for
AD, which copes *MUCH MUCH MUCH* less nicely than eDir with such situations.

Your question as such is not, how do I replace what I have with
something that's much worse under the same circumstances, but what do I
need to know and do to handle such situations.

Now, from a practical POV: In 99% of all cases, if you would restore a
snapshot that isn't too old, and where no dramatical changes have
happened between now and the time of backup (think, servers being added,
replicas chnaged or some such), everything will work just fine.

So, to avoid the 1% situations (whih of course murphy will make you
hit), all you need to do is (like with *every* other database too),
regularly create a supported backup using the database' own tools
somewhere on the disks, which then will be there in case the snapshot
backup fails to work.

Again, not at all eDir specific. You have to do the same for AD, any SQL
database you may run anywhere, and so on.

Here are some links how to proberly backup eDir:

https://www.netiq.com/documentation/edir88/edir88/data/bsl7jmp.html

Or in depth, with examples and alot of knowledge behind it:

http://ldapwiki.willeke.com/wiki/Edirectory%20Backup%20Strategy

CU,
Massimo

Am 28.02.2016 um 04:36 schrieb vpoon:
>
> Hi all,
>
> Right now we have a couple sites using GroupWise 2014 on OES11. The
> servers have NSS volumes and the GroupWise users are associated with an
> eDirectory account. Also, our main site uses eDirectory for the Mobility
> server (users are provisioned using LDAP group in eDirectory) and Novell
> Messenger. These servers all run on VMware ESXi hosts. We currently back
> up the VMs using Veeam Backup and Replication. I've been reading that
> eDirectory doesn't restore well using Veeam with Snapshot backups. Also,
> it sounds like I'm asking for trouble if I use eDirectory with Veeam
> replication if we fail over to a DR site.
>
> So in order to use GroupWise in a DR/BC configuration with Veeam and
> fail over to a DR site, I'm thinking I'll need to do some
> reconfiguration to minimize problems with eDirectory. Should I do the
> following-
> 1. Add another hard disk onto the GroupWise server and migrate the data
> off the NSS volume onto the EXT3 partition and reconfigure GW for the
> new location.
> 2. Disassociate the users/objects in GroupWise from eDirectory.
> Eventually I'll associate the users in GW to Active Directory.
> 2. Remove eDirectory from the GroupWise server but keep eDirectory on a
> different server for the Messenger and Mobility users.
>
> In essence, I'm getting rid of eDirectory/NSS volumes so I can eliminate
> problems when failing over and failing back to/from a DR site.
>
> Does anyone else have some insight into this situation?
>
> Thanks
> Victor
>
>



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

Thanks for the reply and links Massimo. It sounds like it may not be as bad as I thought. We probably won't be adding servers or anything drastic when in failover mode :D. Do you think there will be any issues if when in failover mode, the replicated servers are using different IP addresses as Veeam has as an option when replicating VMs?

Regards,
Victor
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Am 29.02.2016 um 05:06 schrieb vpoon:
>
> Thanks for the reply and links Massimo. It sounds like it may not be as
> bad as I thought. We probably won't be adding servers or anything
> drastic when in failover mode. Do you think there will be any issues if
> when in failover mode, the replicated servers are using different IP
> addresses as Veeam has as an option when replicating VMs?


Changing IP Addresses isn't a trivial task for OES. There are some
scripts provided that need to run to make sure the IP is changed
everywhere.

https://www.novell.com/documentation/oes11/oes_implement_lx/data/ipchange.html

CU,
--
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
Highlighted
Absent Member.
Absent Member.

Thanks for the help Massimo!

Kind regards,
Victor
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Another path to consider.
Make sure a replica of each eDir partition is in the DR site and use
GWAVA's Reload to handle the GroupWise side.


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
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.