Bacula-users

Re: [Bacula-users] question about volume naming

2009-08-06 19:53:16
Subject: Re: [Bacula-users] question about volume naming
From: John Drescher <drescherjm AT gmail DOT com>
To: Brian Clarkson <brianc AT lnstar DOT com>
Date: Thu, 6 Aug 2009 19:48:43 -0400
On Thu, Aug 6, 2009 at 4:32 PM, Brian Clarkson<brianc AT lnstar DOT com> wrote:
> Hello again ...
>
>
> I've read and re-read the Basic Volume Management section of the bacula
> manual today but I can't figure out why my scheduled jobs report one
> volume name while my configuration indicates a different volume name.
>
> bconsole -> status -> director gives me the following list of jobs
>
>
> Scheduled Jobs:
> Level          Type     Pri  Scheduled          Name
> Volume
> ===================================================================================
> Differential   Backup    10  07-Aug-09 01:05    Backup Nibbler
> Backup_Nibbler.2009-08-06_01.05.02-Differential-17635
> Differential   Backup    10  07-Aug-09 01:05    Backup Zapp
> Backup_Nibbler.2009-08-06_01.05.02-Differential-17635
> Differential   Backup    10  07-Aug-09 01:05    Backup Hypnotoad
> Backup_Nibbler.2009-08-06_01.05.02-Differential-17635
>
> All three scheduled jobs are using the same volume.  My Pool definition,
> though, looks like this:
>
> Pool {
>  Name = LSIPool
>  Label Format = "${JobName}-${Level}-${NumVols}"
>  Pool Type = Backup
>  Recycle = no
>  AutoPrune = yes
>  Use Volume Once = yes
>  Volume Retention = 25 days
>  # Accept Any Volume = yes
>  MaximumVolumeBytes = 512m
>  Maximum Volume Jobs = 1
> }
>
> My Job definitions all look like this:
>
> Job {
>  Name = "Backup Leela"
>  Type = Backup
>  Client = leela-fd
>  FileSet = "Full Set Leela"
>  Schedule = "WeeklyCycle"
>  Storage = BenderStorage
>  Messages = Standard
>  Pool = LSIPool
>  Write Bootstrap = "/usr/local/bacula/var/bacula/working/leela.bsr"
> }
>
>  That backup job should use the LSIPool pool.  The LSIPool pool says
> volumes should follow a naming convention that uses jobname as part of
> the filename.  ( jobname, in this case, would be "Backup Leela" ).
>
>
> I've tried stopping and starting the director then checking the status
> but the job list (and the volume list) remains unchanged.
>
> Separate volumes per job were being used in previous jobs.  I've
> apparently changed something but I can't seem to determine *what* has
> made the difference.  The Pool and Job definitions look OK to me.
>
>
> Thanks for any assistance.  I've already put a dent in the desk where my
> head keeps hitting it.
>

I believe this is normal. The volume is not known until the job has
started. And the rules like Use volume once only get executed after
the tape has been used once.

John

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
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>