Bacula-users

Re: [Bacula-users] Storage Daemon Directives

2009-04-14 17:34:18
Subject: Re: [Bacula-users] Storage Daemon Directives
From: Arno Lehmann <al AT its-lehmann DOT de>
To: bacula-users AT lists.sourceforge DOT net
Date: Tue, 14 Apr 2009 23:29:31 +0200
Moin,

14.04.2009 22:09, Hannes Gruber wrote:
> Juche List,

(as we're in dialect here :-)

> 
> I am just going through the documentation of Bacula.
> In the Documentation for the Device Resource of the Storage Daemon
> Configuration:
> 
> http://www.bacula.org/manuals/en/install/install/Storage_Daemon_Configuratio.html#DeviceResource
> 
> The two Directives:
> 
>     LabelMedia = yes
>     AutomaticMount = no

Hmm... seems to be an omission.

Someone correct me if I'm wrong (I have these settings from the start 
of all my Bacula installations and never verified what they actually 
do ;-)...
Label Media: Allows automatic labeling of volumes.

Automatic Mount: Allows automatic (i.e., non-manual) mounting of 
volumes, for example after a label command.

> I found in an example for a FIFO Device on the same page, and in the
> Sample SD-Configuration for a File Storage Device that came with my
> Bacula Gentoo Installation version 2.4.1-r1.
> 
> I could not find a description for those two Directives in the
> documentation of the Device Resource.
> 
> Can anyone help me and explain the meaning of those two Directives?

Hopefully I was right!

> 
> And another question about the Spool Directory.
> If the Spool sice is not limited and the Spool Directory Partition is
> filled up and does not take any more files will this Job fail?

Not necessarily. If *only* the spool area is affected, Bacula will 
simply decide it's time to despool, then truncate the spool file, and 
happily cycle.

If your working directory is on the same, now full, filesystem, 
attribute spooling will also fail and that is fatal to the jobs. You 
won't even get a message, as the message is also spooled in that 
location. If even your log file is there, you won't even see the 
problem in the log...

So, my recommendations:
- use a separate file system for spool space
- limit spool sizes by setting the respective directives
- write the log to another file system
- monitor spool space availability
- manually check for orphaned spool files from time to time
(Monitoring and checking can happen automatically if you use a tool 
like Nagios.)

Arno

> Hannes
> 
> PS.: am I right, the sourceforge.net Email Archive does not have a
> search functionality?
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
> 

-- 
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
www.its-lehmann.de

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>