Hmm. Bummer.  So what you're telling me is that for the 50 boxes I have 
I'll need to set up 50 different jobs?


Yes.  You can specify JobDefaults.  Then just change the client name 
on each job.

This discussion relates to a question or an idea for bacula use with many clients.  For some linux programs, config files are sometimes being organized as nested folders.   The current method of a single configuration file for each (dir, sd, and fd) seems very reasonable.The dir.conf file may get pretty big when one would be trying to use bacula with 25-50+ clients.   However, when the number of clients grows up to numbers like suggested above I start to wonder about a folder based alternative or an 'include /etc/bacula/dir/jobs/*' idea.  Each client could have a separate file for it client specific info (job etc...).   Bacula-dir would read in the standard dir.conf and then append any text data in a file in a given or specified folder. Perhaps it is just a preference to deal with one big text file or many small text files...

I hate to suggest something I don't have the skills to implement but it was something I have been wondering about. Our science dept is thinking of using bacula for 40+ faculty computers and that got me wondering. 

Sorry if this is an old recycled idea / previously discussed idea.  

Dean
-- 

------------------------------------------------------------------------

Dean Waldow, Professor               (253) 535-7533

Department of Chemistry              (253) 536-5055 (FAX)

Pacific Lutheran University          [EMAIL PROTECTED]

Tacoma, WA  98447   USA              http://www.chem.plu.edu/waldow/

------------------------------------------------------------------------

---> CIRRUS and the Chemistry homepage: <http://www.chem.plu.edu/> <----

------------------------------------------------------------------------



Reply via email to