Am 28.05.2012 17:44, schrieb Alan Brown:
> On 28/05/12 14:38, Sean Cardus wrote:
>
>>> Scanning the log it looks like the storage daemon decreases its
>>> spool size limit every time a backup job crashes. The last time
>>> it used the full 50 GB was here:
>>
>> I've been seeing exactly the same be
On 28/05/12 14:38, Sean Cardus wrote:
>> Scanning the log it looks like the storage daemon decreases its
>> spool size limit every time a backup job crashes. The last time
>> it used the full 50 GB was here:
>
> I've been seeing exactly the same behaviour here (CentOS 4.9, Bacula SD
> 5.0.3) for
Hi,
> On a Bacula installation with a CentOS 6.2 (64 bit) server
> running Bacula 5.2.6 director and SD with an HP LTO3 autoloader
> and backing up some twenty-odd machines of various platforms,
> all the jobs report "User specified spool size reached"
> much too early, currently after 1.45 GB ins
On a Bacula installation with a CentOS 6.2 (64 bit) server
running Bacula 5.2.6 director and SD with an HP LTO3 autoloader
and backing up some twenty-odd machines of various platforms,
all the jobs report "User specified spool size reached"
much too early, currently after 1.45 GB instead of the rea
