Hello,

On 08/08/2011 09:35 PM, Bob Hetzel wrote:
> Eric et al,
>
> I didn't mean that the installer broke anything, just that the .conf.new
> files it created (on windows) wouldn't work if I had used them since they
> weren't probably substituted.  But that's not a problem, just thought
> somebody might want to know.
>
> Those of us with a large bacula installation (>200 windows desktop/laptop
> clients) could really use the new Tray Monitor for end users to monitor
> their own backups.

The tray monitor is currently designed for small shops, for example, if 
a client isn't available, you will have a network timeout when 
refreshing the window.

> Apparently a lot of my Windows XP end-users were using
> the status applet built into previous windows bacula-fd versions and
> started to worry when they saw backups failing.  They actually do miss that
> functionality (lost when they were upgraded to Vista/Win7) so if we're
> headed toward restoring that it would be great.

This is the main goal of this new tool.

>  If the installer could be
> made to work for configuring the tray monitor that would be fantastic.

It works like that when installing the client for the first time.

> If they could trigger a manual backup with a GUI too that would be awesome!

It has this function, and it can be improved. The main goal is to have a 
Bacula interface for "End Users" and not Bacula Admin. For example, if 
they can restore a file on their PC, it would be great.

The tray monitor config looks like:
Monitor {
   Name = win2003-mon
   Password = xxx                   # password for the Directors
   RefreshInterval = 30 seconds
}

Client {
   Name = win2003-fd
   Address = localhost
   FDPort = 9102
   Password = "shouldbeautomatic"
}

Director {
   Name = 127.0.0.1-dir
   DIRport = 8101
   address = 192.168.0.12
}

The Console resource on the Director side is:

Console {
    Name = win2003-mon
    Password = "xxx"
    CommandACL = status, .clients, .jobs, .pools, .storage, .filesets, 
.messages, run
    ClientACL = *all*
    CatalogACL = *all*
    JobACL = *all*
    StorageACL = *all*
    ScheduleACL = *all*
    PoolACL = *all*
    FileSetACL = *all*
    WhereACL = *all*
}

You can change ACL to restrict what the client can run. This is a new 
feature, and I expect some problems with it.

Bye
-- 
Need professional help and support for Bacula ?
Visit http://www.baculasystems.com

------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts. 
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to