Kern Sibbald wrote: > On Monday 09 March 2009 18:39:49 Graham Keeling wrote: >> On Mon, Mar 09, 2009 at 05:56:36PM +0100, Kern Sibbald wrote: >>> On Monday 09 March 2009 17:40:15 Graham Keeling wrote: >>>> Hello, >>>> >>>> I have come across some problems involving a single client, a single >>>> fileset, and more than one job definition. >>>> >>>> My setup... >>>> >>>> Client: myclient >>>> FileSet: myfileset >>>> >>>> Job: myjob1 >>>> Job: myjob2 >>> Bacula does not support this option. >> I don't believe that this is made very clear in the documentation. > > Yes, that is very likely the case, but with a program as complex as Bacula > and > already 800 pages of free documentation ... > >> It does appear to be *trying* to support it, as some parts of the code that >> figure out dependent jobs take note of the job name, though others do not. > > I wouldn't exactly say that it is trying to support it, but rather that since > the program is so complicated, and I try not to restrict it too much, there > are places where it can seem to work, but it is just not designed to do so > (at least at the moment), and thus it will not work. It isn't that I don't > want it to work, but there is only so much that the developers can do in the > time we have. > > Unfortunate what you are trying to do is simply not possible in the way you > are trying to do it with the current code.
What the original poster could do to achieve the same result: Have two FileSets with identical content but different names. I am pretty sure the goal is to manage just one FileSet. I suspect you can do this with the existing Bacula directives. -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ ------------------------------------------------------------------------------ _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
