Arno Lehmann napsal(a): > Hi, > > 01.11.2007 15:51,, Ondrej Planka wrote:: > >> ---------- Original Message ---------------------------------- >> From: Kern Sibbald <[EMAIL PROTECTED]> >> Date: Thu, 1 Nov 2007 11:36:55 +0100 >> >> >>> On Thursday 01 November 2007 11:20, Ondrej Planka wrote: >>> >>>>>> Dear list, >>>>>> >>>>>> after installing new version of Bacula (2.2.5 + nextvol patch) and start >>>>>> up Jobs(each Job has different Pool) numbering of new label Volumes >>>>>> growing up regardless Pools. >>>>>> >>>>>> It is quite problem, any advice? >>>>>> >>>>> Well, from your explanation, sorry, but I don't have any idea what the >>>>> >>>>>> problem you are trying to describe is. :-( >>>>>> >>>> For example: I have 3 clients for backup (for each client different Job, >>>> FileSet, Storage and Pool configuration). As storage device I use disk >>>> area. In previous version of Bacula (1.38.11, 2.2.4) when Jobs started and >>>> label new volume name and numbering of this volume growing up in sequence, >>>> e.g. >>>> >>>> Pool1: (For client 1) >>>> VolumeClient1-0001 >>>> VolumeClient1-0002 >>>> >>>> Pool2: (For client 2) >>>> VolumeClient2-0001 >>>> VolumeClient2-0002 >>>> >>>> --It is very good. >>>> >>>> But now, Bacula 2.2.5 + nextvol patch, numbering of these volumes are >>>> without regard pool, e.g. >>>> >>>> Pool1: (For client 1) >>>> VolumeClient1-0001 >>>> VolumeClient1-0002 >>>> >>>> Pool2: (For client 2) >>>> VolumeClient2-0003 >>>> VolumeClient2-0004 >>>> >>>> --It is quite problem. >>>> >>> With the prior code there was the possibility of failures if the user >>> created >>> holes in his Volume numbers by deleting them. The new code assigns a >>> unique >>> number. If you absolutely need sequential volume numbers, then you will >>> need to find another method of numbering them -- either do it with >>> Variables, >>> Python, or manually (you can pre-label as many volumes as you want). >>> >>> >> Thanks for a advice, but for better Volume management is sequential volume >> numbers. >> > > I disagree here... (those of you reading the list a bit longer > probably noticed that before :-) > > In my experience, Bacula can handle the volume management quite > reliably. The need for telling names is usually necessary to male life > easier for the operators (and with barcode-labeled tapes, that can be > a bit difficult, too). > > If you need to handle the volumes manually, it might be best to write > the necessary support functions into a script of your own (which > reminds me of something...) > > >> Problem with relabeling volumes are that these volumes MUST BE Purged or >> Recycled before relabeling :( >> >> Any advice? >> > > Either implement the necessary function as a sql query to be executed > by the 'query' command (which *I* wouldn't do, add the necessary > functionality to the core Bacula code (which I *can't* do), or add > some script externally (which is *my* solution, usually). It might be > a great idea to use Baculas embedded python capabilities, but I > haven't tried that yet. > > In your situation, as you seem to want volumes names numbered > sequentially per pool, I think the python hook for new volume creation > would be the simplest approach (and a good reason to not drop python > from Bacula :-) > > Arno >
Kern and Arno thanks for advice. But my last question - why new version of Bacula changed this volumes names numbered sequentially per pool? Any reason? Thanks in advance, Ondrej. > >> Thanks a lot Kern. >> >> >>> I personally don't see the problem, since Bacula knows quite well what >>> Volumes >>> contain what, and in the prior scheme one was not always guaranteed of >>> having >>> sequential volume numbers, though out of sequence numbers only happened >>> when >>> you deleted volumes. >>> >>> Best regards, >>> >>> Kern >>> >>> >> ------------------------------------------------------------------------- >> 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-devel mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/bacula-devel >> >> > > ------------------------------------------------------------------------- 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
