On Tue, 25 Oct 2011 07:34:06 -0400
Phil Stracchino <alaric AT metrocast DOT net> wrote:

[...]
> MySQLdump is a valid technique, and the simplest working technique.
> You should not, as a rule, back up the MySQL data directory at
> filesystem level.  It is extremely unlikely to yield a consistent
> backup.  If you're going to attempt this, issue a FLUSH TABLES WITH
> READ LOCK, snapshot the MySQL directory, release the lock, then mount
> the snapshot and back up the snapshot.  Thanks to InnoDB's
> write-ahead logs and crash recovery features, this technique is
> generally safe *IF ALL YOUR DATABASES ARE IN INNODB TABLES*.
I'm not that sure regarging your claim: [1] does not indicate FTWRL
does not work for MyISAM databases and [2] directly contradicts your
claim by stating that certain things FTWRL does it's doing exactly to
accomodate MyISAM peculiarities.

Note that I do not use this technique myself so I cannot really judge
from my own experience, just I did not get the impression flush locking
cannot work with MyISAM--after all that's how mysqlhotcopy works, and
AFAIK it was designed specifically for the need to quickly back up
MyISAM databases.

1. http://dev.mysql.com/doc/refman/5.0/en/flush.html
2. 
http://mysqlha.blogspot.com/2009/10/be-careful-with-flush-tables-with-read.html

------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users