[lug] mysqldump versus snapshot versus..

[Jason Vallery]

The other thing you can do is use replication with MySQL and backup
the hot spare box.  This uses binary log files to keep a second
"slave" instance of MySQL in sync with the "master" instance.  Useful
for providing hot spares or in some cases load balancing your select
queries across multiple servers (assuming your data doesn't change
that often).

You can also take down the "slave" instance and do a full backup.
When the slave comes back online it will sync what data it missed
using the binary logs and be back up to date with the "master" fairly
quickly.

There is a good tutorial on setting this up here:
http://www.databasejournal.com/features/mysql/article.php/3355201

You could even have two instances of MySQL running on the same box for
this purpose.


On 8/1/07, dio2002 at indra.com <dio2002 at indra.com> wrote:
> > I just saw this thread.  I thought I would point out the script I use
> > for mysql backups.  it is fantastic!
> >
> > http://sourceforge.net/projects/automysqlbackup/
> >
> > It uses the mysqldump method, but it works really well at automating
> > it and rotating out your backups.  I use this combined with Amazon S3
> > and another set of scripts to setup offsite backups.
>
> nice. thanks
>
>
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
>


-- 
Jason Vallery

mobile: +1.720.352.8822
home: +1.303.539.5347
web: http://vallery.net/