RE: Configuration for redundancy?

[prev] [thread] [next] [Date index for 2005/04/05]

The MySQL folks say they do clustering.  There are whitepapers at this =
link.

http://www.mysql.com/products/cluster/
MySQL Cluster
MySQL Cluster combines the world's most popular open source database =
with a fault tolerant database clustering architecture so you can =
deliver mission-critical database applications with 99.999% =
availability. It is a high-performance main memory database that uses =
synchronous replication to achieve sub-second failover and ensure data =
is continuously available. MySQL Cluster is a cost-effective solution =
that runs on commodity hardware and open source software, and its =
"shared-nothing" architecture does not require any additional shared =
disk storage investment.




-----Original Message-----
From: Chris [mailto:chrisp3623@xxxxxxx.xxx]
Sent: Tuesday, April 05, 2005 3:25 PM
To: modperl@xxxx.xxxxxx.xxx
Subject: Configuration for redundancy?


Greetings,

We have developed a web application using mod_perl and MySQL. We chose =
the=20
light Apache + mod_perl Apache + MySQL method.

What we would like to be able to do is come up with a fully redundant =
setup of=20
machines so that we can sell this package to company's, install it in =
their=20
datacenter and thats it.=20

We are not very hardware minded, so we are looking for suggestions on =
what=20
kind of setup we should deploy. We want to keep redundancy and =
scalability as=20
top priority.

One of our basic ideas was to have a setup of 6 machines and a raid =
array. 3=20
machines would act as the primary machines, the remaining 3 would be =
backup=20
machines. That would leave us with a primary and backup light Apache, =
same=20
with mod_perl same with MySQL.

We would like to separate these three entity's so that as the install =
gets=20
larger and larger, all we need to do is add machines for that specific=20
purpose and not have to re-arrange anything.

The machines would each have a small harddrive connected to them, which =
will=20
contain the operating system. We would then have a raid setup which the=20
individual machines would mount (via NFS?) the raid setup would contain =
the=20
database files, the core code that powers the application, and any web =
files=20
to be served.

Like I said, we are not big into hardware, and this may be overkill or =
totally=20
wrong.=20

Any suggestions are highly appreciated!!