Thanks Adrian, that's really useful.
Kind regards,
Matt
On 10/03/2012 21:35, Adrian Reyer wrote:
> Hi Matt,
>
> On Fri, Mar 09, 2012 at 04:11:17PM +0000, Matthew Macdonald-Wallace
> (lists) wrote:
>> From previous email threads on this list, I've come to the
>> conclusion
>> that the primary bottle neck is the Back-end database, not Bacula
>> itself.
>
> This is my experience as well, though bacula-sd liekes to have quite
> some CPU and eventually RAM as well, depending on your jobs.
>
>> We have taken the design decision to place both the Director and the
>> MySQL instance on the same server - we figure that if the database
>> or
>> the bacula-daemons are down, we can't backup either way. This
>> server
>> has 48G RAM and 10K SAS Disks so there is some flexibility
>> surrounding
>> how it is configured.
>
> I suggest you plan and do you Director and *Postgresql* instance on
> the
> same server. There are a few inices in Baculas database layout that
> contain other inices. MySQL has to do seperate indices for those,
> postgres can use a single index for these. This results in way less
> writes and compared to most other applications that use databases,
> Bacula maily writes.
> I moved from 4GB + MyISAM to 16GB + MyISAM to 16GB + InnoDB and now I
> am
> happy at 8GB + Postgres. I always changed the database/backend when
> backups didn't finish anymore.
>
> bacula=# select count(*) from path;
> count
> --------
> 855516
>
> bacula=# select count(*) from filename;
> count
> ---------
> 4772037
>
> bacula=# select count(*) from file;
> count
> -----------
> 260460301
>
> bacula=# select count(*) from jobmedia;
> count
> -------
> 35267
>
> I plan and keep the filelists within the database for 13 months, the
> problems started at month 3 and I switched database backends every
> month till I reached the current setup. This is now running for 6
> month.
>
>> second HW RAID-1 array (possibly even RAID-0 if it gives us more
>> performance!) - from there I would concentrate on MySQL turning as
>> opposed to anything else.
>
> Make sure you have cache ram on your raid controller and a battery
> backup unit installed. MySQL and Postgres like to write in sync. With
> BBU+cache the write is completed as soon as the controller has the
> data,
> no need to wait for disks. I doubt RAID0 would gain you much if any.
>
> Regards,
> Adrian
--
Matthew Macdonald-Wallace
Green And Secure IT Limited
3 Maddox Close, Osbaston, Monmouth, NP25 3BG
Registered in England and Wales. Company Number: 06769520
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
