Kern Sibbald wrote:
> On Tuesday 13 June 2006 17:09, Jeff Dickens wrote:
>
>> Is there ever any point in including the date or jobname in the label
>> for a disk volume? I had a pool defined as follows:
>>
>> Pool {
>> Name = xyz-pool-full
>> Pool Type = Backup
>> Recycle = yes
>> AutoPrune = yes
>> Volume Retention = 2 months
>> Use Volume Once = yes
>> LabelFormat = "${Level}-${JobName}"
>> }
>>
>> The volumes got labeled as expected with the Level and Job Name (which
>> includes the client name, date & time). But then when the volumes were
>> recycled, the volume label remained the same, referring to a job that
>> had been recycled and a date in the past.
>>
>
> Perhaps the word "LabelFormat" was poorly chosen. In fact it could better be
> called "NameFormat", and it defines how the volume will be named. Once the
> name has been chosen (by you), it will never be changed by Bacula. You must
> explicitly do that by deleting the volume and relabeling it.
>
> The actual Volume label does not contain the job name that wrote the label.
>
>
>> Does it make more sense in this case to just use the level and client
>> name and let it just number the volumes sequentially?
>>
>
> Your question sounds like you are pointing the finger at Bacula for having
> done something wrong, but it was you who (possibly because of a poorly chosen
> directive name) decided what to use for the volume name.
>
>
No finger pointing intended. My problems were clearly due to my
incomplete understanding of what was going on with volume labeling, and,
I see, with disk volume naming. I found the variable expansion facility
and got a little carried away, it seems.
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
