On 11/04/2013 04:17 PM, Phil Stracchino wrote:
...  In at least one of the
> cases I know about, though, the problem was not a failure of DRBD per
> se, it was that someone accidentally started up mysqld on the second
> node, which normally would not be allowed to happen because the second
> instance accessing the same filesystem would not be allowed to lock the
> InnoDB tablespace.  In the DRBD situation, though, there was nothing
> whatsoever locking the tablespace on the local machine, so it quite
> cheerfully allowed both mysqlds to write to their own local instances of
> the tablespace on the replicated filesystem, whereupon the two mysqlds
> proceeded to destroy the tablespace by making it internally inconsistent.

Ah, the "active-active" setup. I agree: avoid like plague.

The simple stupid (and bulletproof) setup is an active/passive cluster
with drbd, mysql, and floating ip. Unfortunately if it fails over your
bacula-dir is going to lost its connection to the db and kill the
running backup -- see my post from 2 days ago.

-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu

signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users