Hi Pierre -
You're correct, mysqlhotcopy will no longer work when you switch to InnoDB.
One option you could pursue is using mysqldump instead, which will write out
full SQL files needed to restore your databases. It will write these to a
filesystem.
It is generally slower than mysqlhotcopy to
Are you currently dumping raw SQL? If so, how? One table at a time, or by
obtaining a lock on all tables?
If you're getting a lock on all tables now, I don't think anything would
change if you switched to a transactional engine like InnoDB and did the
same thing. The database is frozen for a
Did you get a chance to look at mysqlhotcopy?
http://dev.mysql.com/doc/refman/5.0/en/mysqlhotcopy.html
?
M-
- Original Message -
From: P. Evans [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Friday, February 15, 2008 11:50 AM
Subject: [EMAIL PROTECTED] locations
Greetings,
I've
Greetings,
I've got a retail operation with mysql 5.0.22 on linux pc's across the
country, and i need some input on setting up a backup strategy, preferrably
without purchasing a package. We're currently using MyISAM, with the databases
being dumped to a filesystem on a separate drive, in
