Hi,
On Thursday 13 December 2007, Arno Lehmann wrote:
> 13.12.2007 09:54,, Bastian Friedrich wrote::
> >
> > the systems I am about to back up contain distinguished subsets of files
> > - imagine "data belonging to the e-mail system" vs. "home directories"
> > vs. "a network filesystem". To individually restore these subsets, it
> > seems sensible to use single filesets for each of these subsets. Thus, I
> > plan to use a config like this:
>
> Ok, I get it now... though I don't see the need to link these jobs
> like you want to do.
The primary reason for that is the possibility to execute them manually by a
single command.
> If you use the run= directive, even a manual start of the "main" job
> will trigger the additional jobs, which might be unwanted.
That is exactly what I want :)
[...]
> > Job {
> > Name = "MyBackup"
> > FileSet = "empty"
>
> This one could be an Admin job, avoiding some unneeded actions inside
> Bacula.
Good idea.
> >>> Unfortunately, the relevant low level/source structures don't allow for
> >>> a simple adding of such a reference, as far as I can see...
> >>>
> >>> Is there any chance to access the current file set name in a run
> >>> script?
> >>
> >> I think adding that to the job codes' interpretation should be
> >> reasonably easy. Have a look into src/lib/util.c and you'll find the
> >> function edit_job_codes(). That's where the work is done. Getting the
> >> name of the current file set might be a bit difficult; the JCR
> >> contains a pointer to a JOB object, which in turn contains a pointer
> >> to the fileset.
> >
> > The jcr class only contains the relevant pointers if compiled in the
> > director context (i.e. DIRECTOR_DAEMON is set); util.c needs to be
> > independent of that flag. Thus, I cannot find a reference to the job or
> > fileset ressources there:(
>
> Well, I'm a bit astonished, because I don't see how the DIR can *not*
> know the fileset for it's work. And the DIR does initiate the scripts.
The director consists of multiple binary object files, some of which
are "director alone", while others are library/infrastructure. The latter
have different views of some central structures -- in this case restricted
views, compared with the ones in the director :(
I'll probably head for the workaround: Add jobs for every fileset.
Thx again,
Bastian
--
Collax GmbH . Burkheimer Straße 3 . 79111 Freiburg . Germany
p: +49 (0) 761-45684-24
f: +49 (0) 761-45684-10 www.collax.com
Geschäftsführer: William K. Hite / Boris Nalbach
AG München HRB 158898 . Ust.-IdNr: DE 814464942
\ Let us live!!! Let us love!!!
\ Let us share the deepest secrets of our souls!!!
\ You first.
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
