Simon Rosenthal <[EMAIL PROTECTED]> wrote:
>b) Does anyone have redundant database servers ? If so ... are there any
>implementation gotchas ? and if you have a single server, how does session
>management work when it goes down ? (I'm pretty happy with the hardware -
>Suns - which we have, but a disk can go at any time....)
Sun (and most other server/disk providers - e.g., SGI, NetAPP) provides a
volume manager that can handle RAID volumes. If you have a spare disk in the
system and a disk goes bad in the volume, you can take the bad disk out, put
the spare in, and then replace the bad disk at a convenient time. The machine
has to only be down for the hardware replacement then (Sun server), not at all
(SGI disk array) or quiesced for a few seconds (NetApp). Disclaimer -- I am
not an employee of any of the companies mentioned, nor am I endorsing any
particular product or company. These are the systems that we have on the
floor.
I would suggest Apache::DBI to have persistant connections to the database and
a fast local network to reduce latencies, though that's probably not the
largest source of them.
--
James Smith <[EMAIL PROTECTED]>, 409-862-3725
Texas A&M CIS Operating Systems Group, Unix
