> Erm... unless I missed something the SD needs to be restarted for
> configuration changes to take effect.
Thanks. I did not think reload would on the director would reload the
config on the sd or not. I have always just restarted the sd when it
was not in use and only after releasing the tapes f
Hi,
12.02.2008 21:43, John Drescher wrote:
>> So if I could get these config-changes in, without interrupting current
>> running jobs.
>>
> Yes. You can modify the configs without affecting any jobs but they
> will not take effect until you issue the reload command or possibly
> restart the sd.
E
> So if I could get these config-changes in, without interrupting current
> running jobs.
>
Yes. You can modify the configs without affecting any jobs but they
will not take effect until you issue the reload command or possibly
restart the sd.
John
John Drescher wrote:
>> Can I make the storagedaemon reload it's configuration without
>> restarting like the Director?
>>
> Yes. As long as it is not in use you can restart the sd with the
> director running. There is also a reload command in the console that
> reloads the config, but I am not sur
r Krogh <[EMAIL PROTECTED]>
To: bacula-users
Sent: Tuesday, February 12, 2008 12:12:23 PM
Subject: Re: [Bacula-users] Spooling / Misconfiguration.
Arno
Lehmann
wrote:
>>
It
would
be
nice
if
the
Spool-limit
>>
was
pr.
job
or
something.
>
>
It's
in
the
ma
On Feb 12, 2008 3:12 PM, Jesper Krogh <[EMAIL PROTECTED]> wrote:
> Arno Lehmann wrote:
> >> It would be nice if the Spool-limit
> >> was pr. job or something.
> >
> > It's in the manual :-)
> >
> > At
> > http://www.bacula.org/manuals/en/install/install/Storage_Daemon_Configuratio.html#DeviceResour
Arno Lehmann wrote:
>> It would be nice if the Spool-limit
>> was pr. job or something.
>
> It's in the manual :-)
>
> At
> http://www.bacula.org/manuals/en/install/install/Storage_Daemon_Configuratio.html#DeviceResource
>
> there is "Maximum Job Spool Size = bytes".
Excellent.. I somehow ha
Hi Jesper,
12.02.2008 09:56, Jesper Krogh wrote:
> Hi.
>
> I'm runnning 2 concurrent jobs, and that works without any problems (after
> getting the 2 LTO3 drives on their own controller).
>
> Is it "by design" og a misconfiguraion that the two concurrent jobs hit
> the spooldata size at the same
Hi.
I'm runnning 2 concurrent jobs, and that works without any problems (after
getting the 2 LTO3 drives on their own controller).
Is it "by design" og a misconfiguraion that the two concurrent jobs hit
the spooldata size at the same time? It would be nice if the Spool-limit
was pr. job or someth
