I restarted all 3 daemons many times, but no I didn't 'update pool from 
resource'
What I did do was move all of my configs aside, and install the default 
configs and configure a bare-bones setup that would do auto-labelling 
correctly and then merged my customizations into the default, working 
config while testing along the way.  I think what may have been the 
culprit was defining a Storage resource within the pool definition.   
When I moved the Storage definition to the job level and leave it out of 
the pool, auto-labelling seems to work.

Does that sound reasonable or was it a side-effect?

Thanks,
Barak

On 2013-07-25 07:11, Uwe Schuerkamp wrote:
> On Wed, Jul 24, 2013 at 11:22:21AM -0500, Barak Griffis wrote:
>> For some reason, bacula insists on autolabeling with a format of
>> 'TestA-n' where n is the incrementing number.  Any ideas why doesn't 
>> is
>> like my Label Format?
>> 
> 
> Did you issue an "update pool from resource" in bconsole after
> changing the pool definition?
> 
> All the best, Uwe

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users