Re: [Bacula-users] Retention after migration

[Martin S. <ma...@li...>]

>>>>> On Thu, 23 Dec 2010 12:35:47 +0000, Dermot Beirne said:
> 
> Hello,
> I recently switched from copy jobs to migrate jobs functionality, and
> I am concerned about retention.
> 
> I am running Bacula 5.0.3 on Ubuntu 9.04
> 
> I have 4 disk pools (daily, weekly, monthly, yearly) and a matching 4
> tape pools.
> 
> The disk pool retentions are set to:
> 
> Daily-Disk-Pool: File, Job, Volume all 2 days
> Weekly-Disk-Pool: File, Job, Volume all 2 days
> Monthly-Disk-Pool: File and Job 3 days. Volume 4 days
> Yearly-Disk-Pool: File and Job 3 days. Volume 4 days
> 
> The tape pool retentions are set to:
> 
> Daily-Tape-Pool: File and Job are 12 days. Volume is 13 days
> Weekly-Tape-Pool: File and Job are 32 days. Volume is 33 days
> Monthly-Tape-Pool: File, Job and Volume all 1 year
> Yearly-Tape-Pool: File and Job 1 year. Volume 10 years
> 
> All client definitions have a job retention setting of 1 year.  My
> understanding is that this needs to be specified, but is overridden by
> the pool settings.  No other retentions periods are set in
> bacula-dir.conf
> ...snip...
> Yet if I run query in bconsole I get the following for this mediaid:
> 
>     13: List Jobs stored on a selected MediaId
>     14: List Jobs stored for a given Volume name
>     15: List Volumes Bacula thinks are in changer
>     16: List Volumes likely to need replacement from age or errors
> Choose a query (1-16): 13
> Enter MediaId: 896
> No results to list.
> ...snip...
> Can anyone explain what is wrong here, as it looks like I'll have to
> use bscan to restore anything from these volumes?

It is a bug: see http://www.mail-archive.com/bac...@li.../msg42297.html

I think it has been fixed in the (unreleased) 5.1 branch.

__Martin