Bacula-users

Re: [Bacula-users] admin-job does not run on client

2008-05-22 17:19:09
Subject: Re: [Bacula-users] admin-job does not run on client
From: Martin Simmons <martin AT lispworks DOT com>
To: thomas AT ic3s DOT de
Date: Thu, 22 May 2008 22:18:47 +0100
>>>>> On Wed, 21 May 2008 12:21:48 +0200, Thomas  said:
> 
> Hi,
> 
> i tried to run an admin job on a client,
> the job terminates always with status OK,
> even if the client-fd is not running.
> 
> Config:
> 
> RunScript {
>    RunsOnClient = Yes
>    RunsWhen     = Before
>    FailJobOnError = Yes
>    Command = "/home/thomas/job.pl"
>    }
> 
> => JobStatus is always OK.
> 
> 
> changing Yes to No:
> 
> RunScript {
>    RunsOnClient = No
>    RunsWhen     = Before
>    FailJobOnError = Yes
>    Command = "/home/thomas/job.pl"
>    }
> 
> => the job failed as expecteted because of the invalid command.
> 
> 
> I also use some RunOnClientScripts for the normal
> backup jobs and there is no problem, it happens only
> with "Type = Admin"
> 
> 
> is it impossible to run an admin job on the client?

Yes, it is impossible -- an admin job runs entirely on the Director.  You
either need to use ssh in the script to log into the client machine or run a
backup job with no files.

__Martin

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>