On Tuesday 2017-01-10 08:51:15 Lloyd Brown wrote:
> On 01/09/2017 01:11 PM, Josip Deanovic wrote:
> > I have never needed it but I have tested few minutes ago and I can
> > confirm that it works as expected.
> > In my test I have configured a restore job and added a line such as
> > this: ClientRun
On 01/09/2017 01:11 PM, Josip Deanovic wrote:
>
> I have never needed it but I have tested few minutes ago and I can
> confirm that it works as expected.
> In my test I have configured a restore job and added a line such as this:
> ClientRunAfterJob = "/etc/bacula/scripts/bla"
>
> It will run on t
On Monday 2017-01-09 09:56:54 Lloyd Brown wrote:
> On 01/09/2017 09:46 AM, Josip Deanovic wrote:
> > Hi!
> > Maybe you could make use of Verify jobs in case you are restoring the
> > most recent backup and you have fairly recent Verification job run.
>
> I considered a Verify job. I haven't done
On 01/09/2017 09:46 AM, Josip Deanovic wrote:
> Hi!
> Maybe you could make use of Verify jobs in case you are restoring the
> most recent backup and you have fairly recent Verification job run.
I considered a Verify job. I haven't done them much, but the trouble is
that my boss wants a full end-t
On Monday 2017-01-09 09:37:48 Lloyd Brown wrote:
> I hope this isn't something obvious I've missed, but ... well ... I
> missed it, at least so far. I'll keep looking but my google-fu seems to
> be missing something.
>
> Is there an easy way to run an external script (eg. a "RunAfterJob" or
> sim
I hope this isn't something obvious I've missed, but ... well ... I
missed it, at least so far. I'll keep looking but my google-fu seems to
be missing something.
Is there an easy way to run an external script (eg. a "RunAfterJob" or
similar) associated with a *restore* job? I'm trying to build a
