On 11/17/06, Dan Buettner <[EMAIL PROTECTED]> wrote:
James, for a truly 24/7 site, MySQL replication is a better answer than mysqlhotcopy. You leave your master running all the time, and replicate data off to another "slave" server, which you back up. For slave backups, you can use any of a few different schemes, such as mysqlhotcopy, shut down mysql server and copy files, dump using mysqldump, or the commercial InnoDB backup tool if you wanted.
I second that! I have a replication setup running and shell scripts that check the status of the slave once in a while and back it up to tarballs located at different places (USB Mass Storage, Hard Disk and Network Drive). The last major server crash was recovered in 15 minutes by switching the slave to master and changing a DNS entry, while we used the slave backups to restore the master, allowing for a swap later, returning everything to normal.
I used mysqlhotcopy at my last job to do backups and it worked very well - but it did mean a few minutes of locked databases every night. In my situation that was OK, but maybe it's not in yours. Also it doesn't work if you use InnoDB.
I'm a mysqldump fan, but there are lots of ways... Choose your own :) -- Daniel da Veiga Computer Operator - RS - Brazil -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ ------END GEEK CODE BLOCK------ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
