On Monday 12 June 2006 21:50, Arno Lehmann wrote:
> Hello,
>
> On 6/12/2006 3:34 PM, Kern Sibbald wrote:
> > On Monday 12 June 2006 14:29, Arno Lehmann wrote:
> >>On 6/8/2006 10:08 AM, Chris Crowther wrote:
>
> ...
>
> >>Admittedly, the best solution would be 'Full Backup Storage=',
> >>'Differential Backup storage=' and 'Incremental Backup Storage='
> >>directives in the job resource.
> >
> > I think Pool Storage directives are probably better because they slow
> > down the proliferation of Bacula directives, and hopefully give the same
> > thing in a better way without using Run overrides. :-)
>
> Probably... they take away some of the flexibility I use (distributing
> pools over more than one media type and thus storage device), but they
> make management simpler.
>
> My personal preference would be the proliferation of directives... but
> then, I do get paid by people who don't want to work through the
> configuration themselves ;-)
Yea, but you seem to be able to stock a lot more things in your head than I
can, so that is why I am tending toward non-proliferation :-)
>
> Apart from that, trying to simplify the configuration seems a good goal
> to me, and linking pools with storage devices is even kind of logical.
>
> Anyway, having the necessary python hooks for all this sort of stuff
> would be really nice...
Yes, I agree, and the hooks will eventually get implemented (I recently
slipped in a few more variables in a 1.38.x release), but for the moment, the
user interest in Python is almost non-existant. So until I start hearing
more complaints about adding more Python features, it is not very high on my
priority list. I'm not worried about it though. In the early years of
Bacula I heard a lot of complaints about using SQL as the database, and look
what users are doing with it now (bacula-web, recover.pl, and
brestore.pl) !!! :-)
With a few more small hooks into Python, Eric and Marc could hook their Perl
GUI interface directly into Bacula via a Python call to Perl --- hmmm.
While I am wildly speculating, I should say that it seems to me that adding a
Python interpreter to bconsole could allow some really neat scripting of
Bacula commands -- even building "new intelligent" commands that are in fact
Python scripts.
--
Best regards,
Kern
(">
/\
V_V
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
