> 1) Reading TFM (http://dev.mysql.com/doc/mysql/en/flush.html) it appears > that I do not have to 'FLUSH TABLES WITH READ LOCK' for each individual > database. This statement flushes and locks all simultaneously. Am I > correct?
HI, to flush tables, you're right : flush table TOTO <= flushes only toto flush table TOTO,TITI <= flushes only toto and titi flush tables <= flushes ALL Have'nt you thought to a master-slave replication and cold backup from the slave ? Mathias Selon Martijn van den Burg <[EMAIL PROTECTED]>: > Hi, > > Our MySQL 4.1.10 environment runs on Solaris 8 and the data is stored on > a NetApp filer. The schemas contain a mix of MyISAM and InnoDB tables. > > To make a backup we lock all tables in all databases (USE database; > FLUSH TABLES WITH READ LOCK), and then tell NetApp to make a snapshot. > > We have approximately 45 databases, and depending on the amount of work > that is taking place in them, setting the READ LOCK on all of them > separately can take a long time (as in > 15 minutes). This is > unacceptable in a production environment. > > Now I have two questions: > > 1) Reading TFM (http://dev.mysql.com/doc/mysql/en/flush.html) it appears > that I do not have to 'FLUSH TABLES WITH READ LOCK' for each individual > database. This statement flushes and locks all simultaneously. Am I > correct? > > 2) If not, then I wonder whether it might be a Good Idea to do a 'SET > GLOBAL READ_ONLY=1' in stead of locking individual tables. What would be > the impact on queries that are being executed at the moment I set the > lock? > > > Kind regards, > > -- > Martijn van den Burg > ASML ITM&S Application Support / Webcenter > > > -- > The information contained in this communication and any attachments is > confidential and may be privileged, and is for the sole use of the intended > recipient(s). Any unauthorized review, use, disclosure or distribution is > prohibited. If you are not the intended recipient, please notify the sender > immediately by replying to this message and destroy all copies of this > message and any attachments. ASML is neither liable for the proper and > complete transmission of the information contained in this communication, nor > for any delay in its receipt. > > -- > 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]
