Backup Central

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 instead of the really
specified size of 50 GB. Example log excerpt:
[..]
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 quite some time. However, until I saw your email I didn't correlate the max spool size reducing with each time a job crashes. I can also confirm that whenever a job crashes, the max spool size drops.

The only workaround I can see at the moment is restarting the SD...

Sean
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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 quite some time. However, until I saw your email I didn't correlate the max spool size reducing with each time a job crashes. I can also confirm that whenever a job crashes, the max spool size drops.

The only workaround I can see at the moment is restarting the SD...

Have you looked in the spool area to find orphan files?





------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

---------- Forwarded message ----------
From: John Drescher <drescherjm < at > gmail.com>
Date: Mon, May 28, 2012 at 1:20 PM
Subject: Re: [Bacula-users] SD Bug "User specified spool size reached"
To: Sean Cardus <scardus < at > zebrahosts.net>


On Mon, May 28, 2012 at 9:38 AM, Sean Cardus <scardus < at > zebrahosts.net> wrote:
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 instead of the really
specified size of 50 GB. Example log excerpt:
[..]
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 quite some time.  However, until I saw your email I didn't correlate the max spool size reducing with each time a job crashes.  I can also confirm that whenever a job crashes, the max spool size drops.

The only workaround I can see at the moment is restarting the SD...


I would be interested in seeing why jobs are crashing and possibly
submit bug reports for that. I have run 30 thousand or so jobs at work
and I do not see very many job crashes.

John


--
John M. Drescher

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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 behaviour here (CentOS 4.9, Bacula SD 5.0.3) for quite some time. However, until I saw your email I didn't correlate the max spool size reducing with each time a job crashes. I can also confirm that whenever a job crashes, the max spool size drops.

The only workaround I can see at the moment is restarting the SD...

Have you looked in the spool area to find orphan files?

As I already wrote, the spool area contained only two zero-sized files.

T.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users