Re: [Bacula-users] using different fileset for Base job

[Eric B. <eri...@ba...>]

Hello,

>> Indeed, I now confirmed that:
>>   - I could browse for files for restore after bscanning the Full backup
>> volume
>>   - even though I bscanned also Base backup volume these files could not
>> be restored (still getting "Error: file_create.c:382 Unknown file type
>> 24; not restored:")
>>
>> So it seems that for these pools that Base job volumes end up residing
>> in, the File Retention parameters needs to be set to "forever".
>>
>> It's a bit strange that restores don't consider Base jobs in this case.
>> Is it because something gets deleted from catalog in a way that it is
>> not recovered by bscan?
>>
>> --
>> Silver
> 
> Hi.
> 
> So any thoughts about Base job and bscan? Shall I submit a bug report?
> 

The volume doesn't have complete information for Base jobs, so I doubt
that bscan will ever be able to recover all file records in the catalog
in such situation. A BSR might be more convenient here as last resort
solution.

For the File type error, I would advise you to test a recent version, I
think that it's no longer a restriction in 7.0.x. If not, you can open a
bug report for that.

For the retention, I personally always use
  Volume Retention < File Retention <= Job Retention

Delete File records permit to save catalog space, but has a high cost
when it's time to restore files. Delete Job records might end up to
prune volumes before the expected time (Volume Retention + LastWritten).
As the catalog can contain billions of records, it's usually OK.

Best Regards,
Eric

-- 
Need professional help and support for Bacula ?
Visit http://www.baculasystems.com