On 11/14/2017 08:46 AM, Radosław Korzeniewski wrote:
Hello Kern,

2017-11-13 20:13 GMT+01:00 Kern Sibbald <k...@sibbald.com>:

Well it is actually the Bacula File Daemon which initiates the backup at the request of the user.

:) We can interpret it in many different ways.

It is an actually a bconsole which connects to the Bacula File Daemon which talks to the Director. The bconsole and the Bacula FD are the proxy tools in this case. They are required but they not make the event happen.

Yes you are right.  However, there is another part as well.  bconsole (at least by us) is used for testing.  The "real" interface for the user to the Client Initiated Backup is the Tray-Monitor -- i.e. a GUI tool.  Consequently either the tray-monitor or bconsole can be used.


To call it a Client (File Daemon) Initiated Backup the client has to do it yourself, no external tools or user who initiate the job.

Client can have two meanings and we play on that a bit in this definition: 1. Client can mean the File Daemon.  2. More commonly client (at least in the enterprise edition) means the customer (user).

I perfectly understand this is a functionality which is on Roadmap and needs more development and currently is not ready. But someday will be and it will use the already available code.

best regards
--
Radosław Korzeniewski
rados...@korzeniewski.net

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to