Highlighted
Absent Member.
Absent Member.
1385 views

Disaster planning

I need to setup a Backup Server to allow quickly get up and running if there is a server problem.

Setup a 2nd Server in the Tree
Install Groupwise system

Backup Main Server to 2nd Server using DBCOPY

If there is a problem would I be able to simply add a secondary IP address (Main server IP)
and Start Groupwise on the 2nd Server

is this practical ?

I'm not sure the Dbcopy process copies config files for GW, Webaccess etc

are there any other files I need to copy or include in my daily backup ?

Ideally, I'd like to be able to fix the main server and go back to it

Would like to TEST this without messing up the live system or backup server!

GW 2012 + Webaccess + GWIA

Would appreciate any help / pointers
Labels (2)
0 Likes
9 Replies
Highlighted
Absent Member.
Absent Member.

Re: Disaster planning

Should work.

Depending on your disaster scenario, I'd use OES11 as the OS and build a 2 node cluster.

Uwe
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Disaster planning

Uwe Buckesfeld wrote:

> Depending on your disaster scenario, I'd use OES11 as the OS and
> build a 2 node cluster.


Adding BCC to this could provide even more DR capabilities depending on
the needs.

--
Your world is on the move. http://www.novell.com/mobility/
BrainShare 2013 is coming! http://www.brainshare.com

Joe Marton Emeritus Knowledge Partner
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Disaster planning

* Joseph Marton wrote, On 03/10/2013 03:36 AM:
> Adding BCC to this could provide even more DR capabilities depending on
> the needs.


Last time I checked the price for that product was absolutely ridiculous, while a two node cluster is covered by the OES license 🙂

Uwe

--
Novell Knowledge Partner (NKP)
Please don't send me support related e-mail unless I ask you to do so.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Disaster planning

In article <bhrt60.5rxoen@no-mx.forums.novell.com>, Bhrt60 wrote:
> Setup a 2nd Server in the Tree
> Install Groupwise system
>
> Backup Main Server to 2nd Server using DBCOPY
>
> If there is a problem would I be able to simply add a secondary IP
> address (Main server IP)
> and Start Groupwise on the 2nd Server
>
> is this practical ?
>

There are a few gotchas, especially with it being in the same tree.

- Make sure your GW pieces all run on secondary IPs that you switch
over, otherwise you will have an upset tree when eDir tries to talk to
the failed server and finds it talking with itself.
- On a failure you'd have to go change the GW objects to tell them
where they are now on the new server (that's quick enough) but that
means that you can't readily test other than switch it over for real.
- You will have to install and configure the agents on the new server
as well.
- If you went with a different tree, you've have to graft the objects
in, including any new users, but if you could isolate it, you could
actually test it while the main system is live.

This solution can work between separate sites that Cluster Services
can't handle, and does so even if the data is directly corrupted, but
at a longer RPO & RTO.


Disaster Recovery terms RPO & RTO defined at
http://en.wikipedia.org/wiki/Recovery_point_objective

Andy Konecny
Knowledge Partner (voluntary SysOp)
KonecnyConsulting.ca in Toronto
----------------------------------------------------------------------
Andy's Profile: http://forums.novell.com/member.php?userid=75037


___
“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
Knowledge Partner
Knowledge Partner

Re: Disaster planning

In article <mM2%s.326$6y2.29@kovat.provo.novell.com>, Uwe Buckesfeld wrote:
> Last time I checked the price for that product was absolutely ridiculous, while a two node cluster is covered by the OES license 🙂
>

yes, VMware's fail over capabilities comes at a much lower cost even if it can hurt eDir
when migrating.


Andy Konecny
Knowledge Partner (voluntary SysOp)
KonecnyConsulting.ca in Toronto
----------------------------------------------------------------------
Andy's Profile: http://forums.novell.com/member.php?userid=75037


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

Re: Disaster planning

Uwe Buckesfeld wrote:

> Last time I checked the price for that product was absolutely
> ridiculous, while a two node cluster is covered by the OES license 🙂


The pricing model has changed significantly over the past 18 months or
so. It used to be something like $150k which covered unlimited nodes.
Now it's priced per node, and until you hit about 20 or so nodes it's
more cost effective to stick with per node pricing instead of going to
the unlimited model (which is still available).

That being said it's still expensive compared to a free 2-node cluster.
🙂 But if you have to go across multiple sites it may be difficult to
geographically disperse nodes within the same cluster especially if
there's not a ton of bandwidth. However, BCC may be a play to failover
GW from a cluster in one location over to a cluster in another location.

--
Your world is on the move. http://www.novell.com/mobility/
BrainShare 2013 is coming! http://www.brainshare.com

Joe Marton Emeritus Knowledge Partner
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Disaster planning

Andy Konecny wrote:

> yes, VMware's fail over capabilities comes at a much lower cost even
> if it can hurt eDir when migrating.


Ah but VMware does not fail over services. It's only essentially a DR
solution for "hardware" failover and that's it.

--
Your world is on the move. http://www.novell.com/mobility/
BrainShare 2013 is coming! http://www.brainshare.com

Joe Marton Emeritus Knowledge Partner
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Disaster planning

In article <%xk%s.374$6y2.194@kovat.provo.novell.com>, Joseph Marton
wrote:
> Ah but VMware does not fail over services. It's only essentially a DR
> solution for "hardware" failover and that's it.
>

Yes, but the VMware model is essentially that of one service per server,
therefor you are essentially failing over a service in a fashion that is
not that dissimilar to NCS, with VMware's SRM being a lose match for
BCC. From a highlevel business view, there really is no difference
despite all the nuts 'n bolts differences we tech types see.


Andy Konecny
Knowledge Partner (voluntary SysOp)
KonecnyConsulting.ca in Toronto
----------------------------------------------------------------------
Andy's Profile: http://forums.novell.com/member.php?userid=75037


___
“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
Knowledge Partner
Knowledge Partner

Re: Disaster planning

In article <gxk%s.373$6y2.89@kovat.provo.novell.com>, Joseph Marton
wrote:
> The pricing model has changed significantly over the past 18 months or
> so. It used to be something like $150k which covered unlimited nodes.
> Now it's priced per node,
>

that must have been just after I helped architect a client's move to
VMware with a DR center setup. At least they don't need a real time
switch over, just that the data be available the day after the prime
site becomes a crater, so VMware's SRM didn't even make that cut since
it and eDirectory don't appear to play nice.



Andy Konecny
Knowledge Partner (voluntary SysOp)
KonecnyConsulting.ca in Toronto
----------------------------------------------------------------------
Andy's Profile: http://forums.novell.com/member.php?userid=75037


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