On 11/04/13 13:00, Josh Fisher wrote:
> I would add that it is critical (IMO) to place the DB storage on 
> different physical drives than those holding the Bacula spool area. At 
> the end of a job Bacula SD must read the spooled attributes and update 
> the catalog. If spooled attributes and catalog are on the same spindles, 
> then the disk thrashing negates the advantage of attribute spooling. I 
> might also add that placing the catalog on SSD resulted in a hefty 
> performance gain.

Seconded.  Wherever possible, you always want your DB either on separate
spindles or on solid-state media where seek latency is not an issue.

> As for clustering using DRBD, the catalog and spool area should still be 
> on different spindles.

Honestly, based upon experience as a DBA at a hosting company that hosts
MANY customers using MySQL, my first advice on using MySQL on top of
DRBD would be "Just don't."  I could cite lists of customers who have
had complete unrecoverable DB losses as a result of problems or
interactions involving DRBD, and had to rebuild from DB backups.  If
you're going to cluster MySQL, use a shared-nothing configuration if you
possibly can.


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric AT caerllewys DOT net   alaric AT metrocast DOT net   phil AT 
co.ordinate DOT org
  Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
                 It's not the years, it's the mileage.

------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users