Adrian Reyer:
> 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
On 3/10/2012 4:35 PM, Adrian Reyer wrote:
> Hi Matt,
>
> On Fri, Mar 09, 2012 at 04:11:17PM +, Matthew Macdonald-Wallace (lists)
> wrote:
>
>> 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 an
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 +, Matthew Macdonald-Wallace
> (lists) wrote:
>> From previous email threads on this list, I've come to the
>> conclusion
>> that the primary b
On Sat, Mar 10, 2012 at 10:35:49PM +0100, Adrian Reyer wrote:
> same server. There are a few inices in Baculas database layout that
> contain other inices. MySQL has to do seperate indices for those,
That is 'indices', other typos are somewhat easy to understand.
Regards,
Adrian
--
LiHAS
Hi Matt,
On Fri, Mar 09, 2012 at 04:11:17PM +, 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 lie
acula-users] Scaling Bacula
To:bacula-users@lists.sourceforge.net;
Hi all,
I'm working on a platform at the moment which has several hundred
servers (potentially thousands eventually) being backed up across
various data centers using Bacula (managed via Chef).
We've got a prototype
Hi all,
I'm working on a platform at the moment which has several hundred
servers (potentially thousands eventually) being backed up across
various data centers using Bacula (managed via Chef).
We've got a prototype in place and it seems to work well, however
before I deploy I'd like to try an