[PLUG] Mysql newbie question

[Keith Lofstrom]

On Fri, Jun 21, 2013 at 03:39:18PM -0700, Russell Senior wrote:
> replication and it'll be great!"  The message was, paraphrasing, "it's
> not magic, and it won't magically solve all your problems", and "make
> good backups".

Sophisticated questions and answers.   Perhaps someone can point
me at a not-too-complicated tutorial which quickly summarizes
what is simpler and harder to do with mysql backup/mirroring.

I'm using an app that uses mysql, and I know too little about
mysql for safety.  Especially backup and mirroring.  But wuth
way too much to do, I don't have time to become an expert.

I'm guessing mysql is getting 20 reads and 5 writes per minute
during office hours, with zero user load between midnight and 6AM.

At minimum, I want to do the right thing to image the database to
backups at 3 AM.  I rsync them to two different backup servers, but
I don't know that the databases will recover to a viable state.  
Is there something I should be doing to freeze the database?

At maximum, I would like to do realtime imaging to a failover
server on a different network far far away.  About 100kbps between
a couple of lightly loaded machines with solid state drives.
In the rare event that I lose the primary server, I expect to 
lose some recent activity, and spend an hour or two recovering.

What's reasonable to expect from a maintainable-by-dummies backup
and/or failover process for mysql?

Keith


-- 
Keith Lofstrom          keithl at keithl.com         Voice (503)-520-1993