Hi there.
Martin Lillepuu wrote:
> Next logical step would be simplifying bacula for admins. What do you
think?
Thanks to you.
I just tried to make work with Bacula convenient for sysadmins ;)
Those capabilities, which are now implemented in webacula (and will be
supplemented), I use most frequently in my work.
The emergence webacula caused by the fact that I was not able to run
(stable) to the none of the existing (at that time) web interfaces for
bacula. Also, I was not able to build the bat for Fedora (from src-rpm), and
how it works, I studied at the screenshots.
However, for further expansion of the functionality of different web
interfaces for bacula needed some changes in the Bacula.
For example, the more exactly interaction bacula-director and DB Catalog.
Instead of parse output from bconsole I could get relevant data directly
from the database Catalog.
And about scheduled Jobs it can be also get information from Catalog.
Or, for example, if the Catalog in the table File, it would be a small field
(small-smallint, specially for many web interfaces ;) for the storage of
information on the selected file for recovery or not, I would not have had
to be subverted to the copying of data from one database (bacula) to another
(webacula).
For example, some users webacula asked why information about Clients (which
I get from Catalog) does not match the data that shows bconsole.
In short there a lot of work for Bacula developers. ;)
---
with best regards.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
