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
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
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
