Hi Martin, >> I think we need to review your configuration > Apparently :) I have attached a stripped-down, sanitized example. Theoretical it should work.
I have a few comments. - Do you have really monolithic config files? They are bad to read and old school :-). - I didn't know that the construct JobDefs -> JobDefs -> Job works. - For me your configuration is more complex than needed. E.g. Storage definitions at Pools, Jobs and JobDefs is too much. Probably this complex configuration is the reason for your challenge. Personally I have one file for each client (with jobs and FileSet), one minimum JobDef, for each kind of pool one file (e.g. one for file backup and one for catalog) and one file for all storage definitions. Additionally files for e.g. director and each client. I extended the new bareos configuration a little to make it more handy for me. Regards, Stefan P.s. Think simple, not so complex ;-) -- *CaC, Computer and Communication* Inhaber Stefan Klatt End-2-End Senior Network Consultant CISSP / CISM / ISO27001 Lead Implementer / TOGAF9 Badges: https://www.youracclaim.com/users/stefan-klatt Triftstrasse 9 60528 Frankfurt Germany USt-IdNr.: DE260461592 Tel.: +49-(0)172-6807809 Tel.: +49-(0)69-67808-900 Fax: +49-(0)69-67808-837 Email: stefan.kl...@cac-netzwerk.de Profil: http://www.cac-netzwerk.de/profil -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
