[THIN] high availability

  • From: "Lilley, Brian" <brian.lilley@xxxxxxxx>
  • To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
  • Date: Mon, 10 May 2004 14:38:34 +0100

Chaps, I need to draw on your experiences again...

Does the primary IMA Data Store really need to be clustered, or is this more
complication than it is worth. KISS principle, etc.?

I appreciate that high availability is important, but isn't the integrity of
the database even more important.  Without a Data Store, what's the worse that
could happen during the 96 hours, you can't make changes??

If something was seriously wrong the master IMA Data Store cluster node A,
would we want the second cluster to take over?  Is there not a further chance
of corrupting data by having this nice-ity??

If the Data Store becomes unavailable, presumably an app server can still boot
from the contents of the LHC?



This message is for the sole use of the intended recipient. If you received
this message in error please delete it and notify us. If this message was
misdirected, CSFB does not waive any confidentiality or privilege. CSFB
retains and monitors electronic communications sent through its network.
Instructions transmitted over this system are not binding on CSFB until they
are confirmed by us. Message transmission is not guaranteed to be secure.

This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest
constraint to scaling up?! Get this free white paper to understand the
real constraints & how to overcome them. SAVE MONEY by scaling-up rather
than buying more servers.
Useful Thin Client Computing Links are available at:
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:

Other related posts: