Re: [Bacula-users] bacula: Keyword Name not permitted in this resource

2010-12-30 Thread Jeremy Maes
Op 20:59, Robert Garza schreef: Hello, Try removing the spaces in between the Run After Job and Run After Failed Job directive blocks. http://bacula.org/5.0.x-manuals/en/main/main/Configuring_Director.html#SECTION00183 Maybe a bit late (original poster's problem has

Re: [Bacula-users] bacula: Keyword Name not permitted in this resource

2010-12-29 Thread Michel Meyers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27/12/2010 21:00, der_Angler wrote: Hello, I've got a serious problem with my bacula configuration. I've changed my bacula configuration and put all the job , clients and so on in extra files. At this point, I've got 6 jobs und with 2 of them

[Bacula-users] bacula: Keyword Name not permitted in this resource

2010-12-29 Thread der_Angler
@Steve Ellis You are my hero :) the problem is solved with your tip to change: File=C:\ to File=C:/ Thank you very much. +-- |This was sent by bo...@linux-media-systems.de via Backup Central. |Forward SPAM to

Re: [Bacula-users] bacula: Keyword Name not permitted in this resource

2010-12-28 Thread Robert Garza
Hello, Try removing the spaces in between the Run After Job and Run After Failed Job directive blocks. http://bacula.org/5.0.x-manuals/en/main/main/Configuring_Director.html#SECTION00183 On Mon, Dec 27, 2010 at 2:00 PM, der_Angler bacula-fo...@backupcentral.comwrote:

[Bacula-users] bacula: Keyword Name not permitted in this resource

2010-12-27 Thread der_Angler
Hello, I've got a serious problem with my bacula configuration. I've changed my bacula configuration and put all the job , clients and so on in extra files. At this point, I've got 6 jobs und with 2 of them i have the problems. But let me explain with an example. This is the last part of

Re: [Bacula-users] bacula: Keyword Name not permitted in this resource

2010-12-27 Thread Steve Ellis
I believe the error is in the file that you had previously commented out (as I suspect you also believe). Below I've snipped what I think is the problematic line in the pc-agenda_full.conf file: On 12/27/2010 12:00 PM, der_Angler wrote: pc-agenda_full.conf ... FileSet { Name =