[TriLUG] MySQL service

[Tim Jowers]

I don't know about their enterprise product but know their
active-active and active-passive configs work fine. In db parlance
these are called mirroring. Might be all you need if your datasets can
fit on one box and can be served fine by one box. My rule of thumb is
1000 simultaneous users per box. Very rough estimate. I think the
peaks are around 9AM and 2PM.

I know MySQL now has an Enterprise Manager in the same vein as
SQLServer and Oracle. I know Oracle has a very fine grain of
roll-backs within the RDBMS and this is important for massive
databases. E.g. if a server fails then the dba can use the changelogs
to roll to a certain timestamp; thus preventing hell within the
corporation as work has to be redone. I know of one major telco who
runs one of their operational systems without an active backup! The
data set is too large to replicate over the network even over a
weekend and the management does not want to schedule outages to setup
a proper backup solution.

I like PostgreSQL for the little bit I've done with it. It is the
oldest lineage of all the major databases in fact as it is based on
the 1970 Berkeley Ingres database.

Another product to consider is the Steeleye failover product. They
have kits for all the major databses, server software, etc. And work
across Linux and Windows. Basically, they are the Cadillac of this
failover problem with the RDBMS-specific solutions being one-offs.
Anyways, one little thing they do which is really cool is make use of
shared storage so even in the case of HW failure the datastore is
still available.
http://www.steeleye.com/products/linux/lifekeeper.php


On 6/5/08, Cristóbal Palmer <cristobalpalmer at gmail.com> wrote:
> On Thu, Jun 5, 2008 at 5:53 PM, Paul G. Szabady <paul at thyservice.com> wrote:
>>
>> Thanks for the advice, but it doesn't help in this case.  We do and will
>> continue to use oracle, however, we have a growing number of requests to
>> support mysql.  Lots of open source (LAMP) applications are built around
>> mysql, not oracle.
>
> Which is one of the reasons we have a lot more MySQL than PostgreSQL
> at ibiblio. That doesn't mean we don't have our share of MySQL-related
> headaches. This bit us recently, for example:
> http://bugs.mysql.com/bug.php?id=4541
>
> Any particular reason you haven't considered PostgreSQL? Just not
> familiar with it?
>
>> We currently have five standalone mysql servers for a variety of apps.
>> I want to build a solid infrastructure and move these five to it and
>> have the ability to support future growth.
>
> We at ibiblio don't do clustering. We do use zmanda for some backups:
> http://www.zmanda.com/
>
> We'd be interested to hear back from you about how you end up
> structuring your cluster if you do move to it, but honestly ibiblio
> can't and won't pay for MySQL Enterprise.
>
> --
> Cristóbal M. Palmer
> http://tinyurl.com/3apraw "They also abandoned other volumes, later,
> while fleeing from the librarians."
> --
> TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG FAQ  : http://www.trilug.org/wiki/Frequently_Asked_Questions
>