RE: APYJRNCHG

If you rely on journaling for hardware failures, put your journal receivers
into a different ASP.  If you want to protect your data from loosing your
computer room, have two rooms in two different building fiber attached and
mirror from one cabinet in room A to the remote cabinet in room B or to a
completely different machine in a completely different building.  If you
want to protect from application failure, journaling is great.  Journaling
also works great for catastrophic disk/ctl failure if you use two ASP on two
controllers on two busses.

Journaling does have its place but not for High Availability!

Christopher K. Bipes      mailto:ChrisB@Cross-Check.com
Operations & Network Mgr  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.                  http://www.cross-check.com
6119 State Farm Drive     Phone: 707 586-0551 x 1102
Rohnert Park CA  94928    Fax: 707 586-1884

-----Original Message-----
From: prumschlag@phdinc.com [mailto:prumschlag@phdinc.com]
Sent: Wednesday, August 22, 2001 1:11 PM
To: midrange-l@midrange.com
Subject: Re: APYJRNCHG




Al,

So the bottom line of your advice is this:  If you want recovery capability
up
to the last time someone pressed the ENTER key, use a HA solution (which
costs
big bucks).  If you expect to depend on Journalling as a poor-man's
solution,
there's a good chance that you are fooling yourself.  You can set up
procedures
so that you can be fairly confident in recovering from your last SAVLIB (or
SAVwhatever), but  the confidence level in applying journal changes goes
down
quickly.

Thanks for the info, Al.  It's not what I wanted to hear, but I appreciate
your
frankness.

Phil