On Wednesday 11 April 2007 23:24, Ralf Gross wrote:
> Martin Simmons schrieb:
> > >>>>> On Wed, 11 Apr 2007 20:28:48 +0200, Ralf Gross said:
> > >
> > > Kern Sibbald schrieb:
> > > > > The main question is, why did bacula mark volumes 06D124L3 as used
> > > > > right > after the first job started when the voluseduration is set
> > > > > to 4 days?
> > > >
> > > > I'm not sure that recycling a volume resets its use duration. Perhaps
the use
> > > > duration expired at about the time or just after when the volume was
> > > > recycled.
> > >
> > > The volume use duration is 4 days, 2007-02-25 was the first and last
> > > time the volume was in use (weekly diff. backup) before the diff.
> > > backup last sunday night.
> > >
> > > <http://www.bacula.org/rel-manual/FileSet_Resource.html#PoolResource>
> > > The Volume Use Duration directive defines the time period that the
> > > Volume can be written beginning from the time of first data write to
> > > the Volume. If the time-period specified is zero (the default), the
> > > Volume can be written indefinitely. Otherwise, the next time a job
> > > runs that wants to access this Volume, and the time period from the
> > > first write to the volume (the first Job written) exceeds the
> > > time-period-specification, the Volume will be marked Used, which means
> > > that no more Jobs can be appended to the Volume, but it may be
> > > recycled if recycling is enabled. Using the command status dir
> > > applies algorithms similar to running jobs, so during such a command,
> > > the Volume status may also be changed. Once the Volume is recycled, it
> > > will be available for use again.
> > >
> > >
> > > If I understand the last sentence correct, the volume use duration
> > > should be reset after the volume was recycled. Otherwise the volume
> > > could never be used again after the max volume use duration expired.
> >
> > That is almost correct.
> >
> > The volume use duration itself is never reset, because it holds the
difference
> > between two times. Instead, the volume has a "firstwritten" timestamp,
which
> > is updated when the first job is written.
>
> Ok, then something seems to be wrong with the firstwritten time of this
volume.
> It's still the date/time when the first differential job was written to
> the tape.
Sorry, I cannot tell if anything is wrong. You snipped out critical data,
thus I have no comment.
>
> *llist volume pool=Differential
> mediaid: 5
> volumename: 06D124L3
> slot: 5
> poolid: 5
> mediatype: LTO3
> firstwritten: 2007-02-24 23:45:04
> lastwritten: 2007-04-08 00:12:44
> labeldate: 2007-04-08 00:07:08
> [...]
>
> This is an example of an old tape from my 1.38.5 server:
>
> *llist volumes pool=Bang
> mediaid: 25
> volumename: Bang1
> slot: 1
> poolid: 1
> mediatype: AIT-2
> firstwritten: 2007-02-18 02:59:10
> lastwritten: 2007-02-18 03:12:47
> labeldate: 2007-02-18 02:59:10
> [snip]
>
> This tape was reused every 2 weeks.
>
> > "Max configured use duration exceeded" means that the firstwritten + use
> > duration time is in the past, so as Kern said, this could happen if Bacula
> > fails to update the firstwritten because of a bug.
> >
> > Do you know when 06D124L3 was marked as recycled? Look for Director
messages
> > like
> >
> > Pruned nnn Jobs on Volume "06D124L3" from catalog.
> > There are no Jobs associated with Volume "06D124L3". Marking it purged.
> > Recycled volume "06D124L3"
>
> I can't find any message about this in the log file. There are only
messages
> about pruned files. Nothing about pruned volumes...
Well, I tend to use "pruned volumes" to mean purged. Once the Volume is
pruned of all its Jobs, then it will be marked as purged, and available for
recycling.
>
> 11-Apr 00:09 VU0EM005: Pruned Files from 1 Jobs for client VU0EM003 from
catalog
>
> This is very differnt from my old 1.38.5 install, where I can find the
expected
> messages about pruned volumes.
>
>
> pool config:
>
> Pool {
> Name = Differential
> Pool Type = Backup
> Recycle = yes
> AutoPrune = yes
> Recycle Oldest Volume = yes
> Volume Use Duration = 96 hours
> Volume Retention = 31 days
> }
I see you have "Recycle Oldest Volume" set. If I am not mistaken (I sometimes
confuse these options), this is one of the options I recommend against using
because it allows you to shoot yourself in the foot. In in fact forces or
overrides Bacula's normal recycling algorithm, and may be the source of your
problems. I suggest you read up on it, and if it is not absolutely
necessary to your setup, eliminate it.
>
> double check:
>
> poolid: 5
> name: Differential
> numvols: 5
> maxvols: 0
> useonce: 0
> usecatalog: 1
> acceptanyvolume: 0
> volretention: 2,678,400
> voluseduration: 345,600
> maxvoljobs: 0
> maxvolbytes: 0
> autoprune: 1
> recycle: 1
> pooltype: Backup
> labelformat: *
> enabled: 1
> scratchpoolid: 0
> recyclepoolid: 0
> labeltype: 0
>
>
> > Note that the "all previous data lost" message comes from the SD, not the
> > Director.
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/bacula-users
