Hi,

sometimes I just can't follow the decision bacula takes about which volume to
recycle (bacula 2.0.3 - update to 2.2.4 scheduled, debian etch, postgres 8.1). 

http://www.bacula.org/rel-manual/Automatic_Volume_Recycling.html#SECTION002530000000000000000

[...]
# Try recycling any purged Volumes. 
# Prune volumes applying Volume retention period (Volumes with VolStatus Full,
Used, or Append are pruned). Note, even if all the File and Job records are
pruned from a Volume, the Volume will not be marked Purged until the Volume
retention period expires.
# Search the Pool for a Volume with VolStatus=Purged
# If a Pool named "Scratch" exists, search for a Volume and if found move it to
the current Pool for the Job and use it. Note, when the Scratch Volume is moved
into the current Pool, the basic Pool defaults are applied as if it is a newly
labeled Volume (equivalent to an update volume from pool command). 
[...]

And this is what happened, btw: not for the first time:

07-Okt 11:03 VU0EM005-sd: End of medium on Volume "06D131L3"
             Bytes=687,798,171,648 Blocks=10,661,553 at 07-Okt-2007 11:03.
07-Okt 11:03 VU0EM005-dir: Pruned 1 Job on Volume "06D132L3" from catalog.
07-Okt 11:03 VU0EM005-dir: ua_purge.c:611 All records pruned from Volume
             "06D132L3"; marking it "Purged"
07-Okt 11:03 VU0EM005-dir: Recycled volume "06D136L3"
07-Okt 11:03 VU0EM005-dir: Using Volume "06D136L3" from 'Scratch' pool.


Why did bacula choose the volume from the scratch pool and not volume 06D132L3
which is in the Full-Pool and just was purged? Why didn't bacula recyle vol
06D132L3 right after purging it?

It seems bacula is not following the described recycling algorithm above.


Here's the volume status as of 2007-09-30:

Pool: Full
          mediaid: 13
       volumename: 06D132L3
             slot: 13
           poolid: 4
        mediatype: LTO3
     firstwritten: 2007-04-01 00:07:10
      lastwritten: 2007-04-01 04:33:27
        labeldate: 2007-04-01 00:07:10
          voljobs: 3
         volfiles: 293
        volblocks: 4,506,790
        volmounts: 1
         volbytes: 290,742,100,992
        volerrors: 0
        volwrites: 4,506,791
 volcapacitybytes: 0
        volstatus: Used
          enabled: 1
          recycle: 1
     volretention: 15,552,000
   voluseduration: 345,600
       maxvoljobs: 0
      maxvolfiles: 0
      maxvolbytes: 0
        inchanger: 1
          endfile: 292
         endblock: 4,333
         volparts: 0
        labeltype: 0
        storageid: 2
         deviceid: 0
       locationid: 0
     recyclecount: 0
     initialwrite: 
    scratchpoolid: 0
    recyclepoolid: 0
          comment: 


Pool: Scratch
          mediaid: 18
       volumename: 06D136L3
             slot: 17
           poolid: 7
        mediatype: LTO3
     firstwritten: 2007-07-01 05:48:40
      lastwritten: 2007-07-01 05:51:24
        labeldate: 2007-07-01 05:48:40
          voljobs: 1
         volfiles: 1
        volblocks: 8,265
        volmounts: 3
         volbytes: 533,256,192
        volerrors: 0
        volwrites: 11,733
 volcapacitybytes: 0
        volstatus: Purged
          enabled: 1
          recycle: 1
     volretention: 31,536,000
   voluseduration: 0
       maxvoljobs: 0
      maxvolfiles: 0
      maxvolbytes: 0
        inchanger: 1
          endfile: 0
         endblock: 8,265
         volparts: 0
        labeltype: 0
        storageid: 2
         deviceid: 0
       locationid: 0
     recyclecount: 1
     initialwrite: 
    scratchpoolid: 0
    recyclepoolid: 0
          comment:



Ralf

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to