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 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. Dan On 11/17/06, James Tu <[EMAIL PROTECTED]> wrote:
We're working on a site that will most likely be up 24 hours a day. What is the best backup strategy for the database? The client will be using hosting services, but they haven't' picked anyone yet. I've been playing around with mysqlimport (pretty straightforward) and mysqlhotcopy (haven't been able to run it...don't have the appropriate Perl modules.) We'll probably just take a daily 'snapshot' of the database. What is the best way to do this? Am I safe with writing my own shell scripts that essentially just calls mysqlimport? Does that handle a live database w/o any issues? -James -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
