View Issue Details

IDProjectCategoryView StatusLast Update
0000364bareos-coredirectorpublic2015-01-26 16:21
Reporterirekpias Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionwon't fix 
PlatformLinuxOSCentOSOS Version5
Product Version14.2.1 
Summary0000364: Volume retention - the oldest volume are'nt pruning, even if log say so.
DescriptionI have pool. In this pool can be only 3 volumes. I set defs for this pool, so jobs are cycle over volumes. So when system want write to volume, but there isn't free volume, then should be the oldest volume pruning and recycled - thus ready to write (even if expiration time isn't came).

So - there is my pool config:

Pool {
  Name = Full-Client1
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Action On Purge = Truncate
  Recycle Oldest Volume = yes
  Volume Retention = 6 month
  Maximum Volume Bytes = 50G
  Maximum Volumes = 3
  Label Format = "Full-Client1-${NumVols}"
  Storage = posejdon-sd
  Maximum Volume Jobs = 1
}

There is log record for failed job:

#############
Log records for job 6
2014-11-11 16:47:48
posejdon-dir
Start Backup JobId 6, Job=Backup-Client1.2014-11-11_16.47.46_13


Pruning oldest volume "Full-Client1-0"
Using Device "FileStorage1" to write.
Pruning oldest volume "Full-Client1-0"
Pruning oldest volume "Full-Client1-0"
2014-11-11 16:47:48
posejdon-sd
Job Backup-Client1.2014-11-11_16.47.46_13 is waiting. Cannot find any appendable volumes.
Please use the "label" command to create a new Volume for:
    Storage: "FileStorage1" (/var/lib/bareos/storage)
    Pool: Full-Client1
    Media type: File1
############

And oputput from bconsole:

*list volumes
Pool: Full-Client1
+---------+----------------+-----------+---------+-------------+----------+--------------+---------+------+-----------+-----------+---------------------+
| MediaId | VolumeName | VolStatus | Enabled | VolBytes | VolFiles | VolRetention | Recycle | Slot | InChanger | MediaType | LastWritten |
+---------+----------------+-----------+---------+-------------+----------+--------------+---------+------+-----------+-----------+---------------------+
| 2 | Full-Client1-0 | Used | 1 | 267,896,011 | 0 | 15,552,000 | 1 | 0 | 0 | File1 | 2014-11-11 16:42:30 |
| 3 | Full-Client1-1 | Used | 1 | 267,896,011 | 0 | 15,552,000 | 1 | 0 | 0 | File1 | 2014-11-11 16:43:30 |
| 4 | Full-Client1-2 | Used | 1 | 267,896,011 | 0 | 15,552,000 | 1 | 0 | 0 | File1 | 2014-11-11 16:47:17 |
+---------+----------------+-----------+---------+-------------+----------+--------------+---------+------+-----------+-----------+---------------------+

So pruning isn't happend and bareos want to label next volume.

It is a bug, or i missing some options in pool defs ? I want to bareos cycle trough my volumes in automatic way.



Steps To ReproduceFull all volumes in pool, then system should use again the oldest tape.
TagsNo tags attached.

Activities

pstorz

pstorz

2014-11-11 23:40

administrator   ~0001058

Hello Irekpias,

Please use the mailinglists for basic configuration questions instead of filing bugreports.

Bugreports should only be created if you are sure that there is a bug, and not if you do not understand how something should work.

Please read our documentation:

http://doc.bareos.org/master/html/bareos-manual-main-reference.html#QQ2-1-303

You have configured Recycle Oldest Volume = yes , this means:

The Recycle Oldest Volume = yes record in the Pool resource tells Bareos to Prune the oldest volume in the Pool, and if all files were pruned to recycle this volume and use it.

Pruning means that all retention periods are respected. Thins means that of course your volumes will not be overwritten as your retention periods do not allow that

What you want seems to be Purge Oldest Volume.

The Purge Oldest Volume = yes record in the Pool resource permits a forced recycling of the oldest Volume when a new one is needed. N.B. This record ignores retention periods! We highly recommend not to use this record, but instead use Recycle Oldest Volume

Best regards,

Philipp

Issue History

Date Modified Username Field Change
2014-11-11 17:14 irekpias New Issue
2014-11-11 23:34 pstorz Assigned To => pstorz
2014-11-11 23:34 pstorz Status new => assigned
2014-11-11 23:40 pstorz Note Added: 0001058
2014-11-11 23:40 pstorz Status assigned => closed
2014-11-11 23:40 pstorz Resolution open => won't fix
2015-01-26 16:21 mvwieringen adm Assigned To pstorz =>