>>>>> 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. "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" Note that the "all previous data lost" message comes from the SD, not the Director. __Martin ------------------------------------------------------------------------- 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 Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
