Arno Lehmann wrote: > Hi, > > 23.10.2007 12:14,, Rich wrote:: > >> On 2007.10.23. 11:40, Arno Lehmann wrote: >> >>> Hello, >>> >> ... >> >>>> My only solution for this right now is to estimate how much space the >>>> Backup will use, and label the Volumes >>>> before the Job runs, but as you can imagine thats annoying ... >>>> >>> Yes. >>> >>> >>>> is there anything i'm missing that this happens ? >>>> thanks for any hint ... >>>> >>> I'd first suggest to drop the "LabelFormat" directive. It's deprecated >>> and will vanish some day. >>> >>> Instead, use a python event to provide names for new volumes. >>> >> umh. i must have missed this... will it really be dropped ? as i am >> using it, i don't fancy learning python just to replicate its functionality. >> > > Well... it won't be dropped anytime soon, but I recall Kern stating > that he won't touch that code anymore, so once he needs to rework the > code related to automatic volume labeling, it might be gone. > > I couldn't say how likely that is, though - might be tomorrow, or in > ten years. > > >> i am using this parameter to create single file per backup job and give >> them meaningful names - would it indeed at some point get replaced by a >> requirement to script in python ? >> > > That requirement, by the way, is not very problematic. The sample > given in the manual should almost work out of the box, and python is > easier to learn than Baculas variable substitution language :-) > > >>> This is described in the manual, for example >>> http://www.bacula.org/dev-manual/Python_Scripting.html#SECTION003560000000000000000 >>> >> ... >> > > Anyway - I'm operating Bacula installations using the LabelFormat > option as well, and those work correctly. But then, these > installations haven't labeled a volume for more than a year now, as > their pools have reached their maximum number of volumes by now. It > might be that there is a bug somewhere, which noone noticed yet. > > You could try to set up a test pool and job, where you limit the > volumes to, say, 10MB, use the most simple form of LabelFormat, i.e. > "Label-" or something, and assign a newly created storage device to it. > > Then, run a job, preferrably with debug output enabled, and see what > happens. > > That should eliminate the chance that some misconfiguration crept into > your catalog, and it should give a good set of debug files to analyze > quickly. > dont shoot, but ill try to use the python way you recommended :) but thanks anyway.
Greetz mIke > Arno > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
