On 10/25/11 10:41, Konstantin Khomoutov 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.
I'm not for a moment asserting that FLUSH ... doesn't work on MyISAM.
It actually works more reliably on MyISAM than on InnoDB. My point is
that should you get a glitch - perhaps something wasn't fully flushed to
disk before your snapshot - InnoDB has built-in features to recover from
the error. MyISAM does not. MyISAM is, in fact, very vulnerable to
data corruption from any of a number of causes.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
