Jeff Smelser wrote:
Well, then you would be more interested in mysqlhotcopy.. That pretty much
does what your doing..
Mysql INC has yet to make a real backup/restore procedure for mysql. So
mysqldump or mysqlhotcopy is pretty much it. If you use innodb, I would go
after ibbackup. (not free).
I have been on a few developers about it, just doesnt seem high priority to
them. (or I am not talking to the right ones).
Because once you start caring about your db that much it's usually
easier to setup a crap box that replicates off your master. Then you can
lock the whole db on your slave and do a mysqldump without causing
issues on your main db regardless of which table type you're using. You
also get the added benefit of a hot backup and no I/O hits on the main db.
I'm managing five fairly busy Mysql servers so my tactics might not be
those of the average user making the above a bit of overkill. I was very
excited about Mysql's instance manager. However if your database has
known periods of time when it isn't being used, ie you're using it as an
Access replacement. Lock the tables, do the dump, free the tables, and
save your cash for flaming Tiki drinks.
kashani
--
gentoo-user@gentoo.org mailing list
