Bacula-users

Re: [Bacula-users] incorrect "User specified spool size reached" message

2011-01-05 08:08:44
Subject: Re: [Bacula-users] incorrect "User specified spool size reached" message
From: Dan Langille <dan AT langille DOT org>
To: Tilman Schmidt <t.schmidt AT phoenixsoftware DOT de>
Date: Wed, 05 Jan 2011 08:06:21 -0500
On 1/5/2011 6:50 AM, Tilman Schmidt wrote:
> I'm running Bacula 3.0.2 to back up a dozen of Linux servers
> and a few Windows ones. Recently, messages like this started
> showing up in the backup logs:
>
> 04-Jan 22:10 vm-backup-sd JobId 11043: Spooling data ...
> 04-Jan 22:11 vm-backup-sd JobId 11043: User specified spool size reached.
> 04-Jan 22:11 vm-backup-sd JobId 11043: Writing spooled data to Volume. 
> Despooling 16,001,952 bytes ...
> 04-Jan 22:11 vm-backup-sd JobId 11043: Despooling elapsed time = 00:00:01, 
> Transfer rate = 16.00 M bytes/second
> 04-Jan 22:11 vm-backup-sd JobId 11043: Spooling data again ...
> 04-Jan 22:11 vm-backup-sd JobId 11043: User specified spool size reached.
> 04-Jan 22:11 vm-backup-sd JobId 11043: Writing spooled data to Volume. 
> Despooling 16,001,952 bytes ...
> 04-Jan 22:11 vm-backup-sd JobId 11043: Despooling elapsed time = 00:00:01, 
> Transfer rate = 16.00 M bytes/second
> 04-Jan 22:11 vm-backup-sd JobId 11043: Spooling data again ...
>
> The number of despooled bytes stays around the same during one
> backup run (all jobs of one day) but decreases substantially
> from one day to the next. For example:
>
> 03-Jan 22:29 vm-backup-sd JobId 11028: User specified spool size reached.
> 03-Jan 22:29 vm-backup-sd JobId 11028: Writing spooled data to Volume. 
> Despooling 364,044,395 bytes ...
> 03-Jan 22:29 vm-backup-sd JobId 11028: Despooling elapsed time = 00:00:24, 
> Transfer rate = 15.16 M bytes/second
> 03-Jan 22:29 vm-backup-sd JobId 11028: Spooling data again ...
>
> My storage configuration looks like this:
>
> Device {
>    Name = LTO1
>    Media Type = LTO1
>    Archive Device = /dev/nst0
>    AutomaticMount = yes;               # when device opened, read it
> # OfflineOnUnmount = yes;             # when unmounted, eject tape
>    AlwaysOpen = yes;
>    RemovableMedia = yes;
>    RandomAccess = no;
>    SpoolDirectory = /home/backup/spool;
>    MaximumSpoolSize = 50G;
> }
>
> So, taken literally, that message is just plain wrong. The 16 MB
> spooled are far less than my specified spool size of 50 GB.
>
> I checked the spool directory for stale files, and it is empty.
> The filesystem it resides on has 98 GB of free space.
> There are no concurrent jobs. ("Maximum Concurrent Jobs = 1")
>
> What other possible reasons are there for that message?

At one time, was MaximumSpoolSize set to 16GB?  If so, did you restat 
bacula-sd after making that change?

-- 
Dan Langille - http://langille.org/

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users