Funny thing, this mailing-list, I usually find an answer or hint 5 
minutes after sending out for information.

Now this clue: ..."is a good idea put Pools, Clients and Storage 
Resources declarations in different files."

Yet, at http://wiki.bacula.org/doku.php?id=sample_configs shows a clear 
example of more than Pools/Clients/Storage. Specific example is 
schedule.conf (@/etc/bacula/conf.d/schedule.conf)

Yet again, at http://wiki.bacula.org/doku.php?id=sample_configs shows 
WAY more than Pools/Clients/Storage conf files:

# Include below all yours jobs configuration files (remember add '@' at 
beginning)
@/etc/bacula/conf.d/test.conf
@/etc/bacula/conf.d/mails.conf
@/etc/bacula/conf.d/server2.conf
@/etc/bacula/conf.d/monitor.conf
@/etc/bacula/conf.d/debian.conf

# Clients definition files
@/etc/bacula/conf.d/clients.conf

# Storages definition file
@/etc/bacula/conf.d/storages.conf

# Pools definition files
@/etc/bacula/conf.d/pools.conf

So my Question now becomes what exactly can be included  "In the Debian 
manner" ?


JJ aka Habitual

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users