Hi,

have you changed anything on the pool resource since you have first used "full_admt-0006"? The volume retention is saved on a per volume basis in the database. If you update the pool resource in the conf file the changes are not updated on existing volumes.
check the volume retention with
list volumes

Regards

Helmut

Patrick Van der Veken schrieb:
Hi,

Running bacula 1.38.5 on SLES 9 we have following problem when running a
backup  last night:

10-Mar 23:00 admt-sd: full_backup.2006-03-10_23.00.00 Warning: Director
wanted Volume "full_admt-0017".
    Current Volume "full_admt_0006" not acceptable because:
    1998 Volume "full_admt_0006" status is Used, but should be Append,
Purged or Recycle (cannot automatically recycle current volume, as it
still contains unpruned data).
10-Mar 23:00 admt-sd: Please mount Volume "full_admt-0017" on Storage
Device "DDS-5" (/dev/nst0) for Job full_backup.2006-03-10_23.00.00

The volume full_admt_0006 was last written on 22-Feb and has a retention
time of 10 days. By 10-Mar it was thus well and truly expired. We are
using following DIR settings for the media pool:

Pool {
  Name = full
  Pool Type = Backup
  Maximum Volumes = 50
  Maximum Volume Jobs = 0               # unlimited
  Maximum Volume Files = 0              # unlimited
  Maximum Volume Bytes = 0              # unlimited
  Catalog Files = yes                   # catalog in database
  Recycle = yes                         # automatically recycle Volumes
  AutoPrune = yes                       # Prune expired volumes
  Volume Retention = 10d
  Volume Use Duration = 12h
  Accept Any Volume = yes               # write on any volume in the pool
  Recycle Current Volume = yes
  LabelFormat = "full_admt-"
}

*llist pools
Using default Catalog name=default DB=bacula
          PoolId: 1
            Name: full
         NumVols: 19
         MaxVols: 50
         UseOnce: 0
      UseCatalog: 1
 AcceptAnyVolume: 1
    VolRetention: 864,000
  VolUseDuration: 43,200
      MaxVolJobs: 0
     MaxVolBytes: 0
       AutoPrune: 1
         Recycle: 1
        PoolType: Backup
     LabelFormat: full_admt-
         Enabled: 1
   ScratchPoolId: 0
   RecyclePoolId: 0
       LabelType: 0

After receiving a mount request I executed a manual "prune" command on the
volume which correctly expired all jobs of the volume. The backup then
continued after issuing a "mount" command.

Q: why didn't Bacula automatically prune the volume data even though
AutoPrune, Recyle and 'Recycle Current Volume', 'Accept Any Volume' are
all set?

Regards,



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to