Hi,
On 3/29/2006 12:21 PM, Turbo Fredriksson wrote:
Quoting Wolfgang Denk <[EMAIL PROTECTED]>:
In message <[EMAIL PROTECTED]> you wrote:
From looking at the Docs, and through the archives I think I can
disable a client's backup by commenting out the Schedule line like this:
We put all c
Quoting Wolfgang Denk <[EMAIL PROTECTED]>:
> In message <[EMAIL PROTECTED]> you wrote:
>> From looking at the Docs, and through the archives I think I can
>> disable a client's backup by commenting out the Schedule line like this:
>
> We put all client related definitions (Job, FileSet, S
On Monday 27 March 2006 18:26, Turbo Fredriksson wrote:
> Quoting Kern Sibbald <[EMAIL PROTECTED]>:
> > On Thursday 23 March 2006 20:35, Turbo Fredriksson wrote:
> >> Quoting "Dan Langille" <[EMAIL PROTECTED]>:
> >> > NOTE: any disabled jobs are renabled if you restart bacula-dir.
> >>
> >> That wa
Turbo Fredriksson wrote:
> config file require a restart of the server to take affect, and it's
> very possible that such a thing (downtime, even for a short time)
> isn't desired.
Erm, you don't have to restart a server just to make something
re-read a conf file - you can just ask the da
Turbo Fredriksson wrote:
Quoting Kern Sibbald <[EMAIL PROTECTED]>:
On Thursday 23 March 2006 20:35, Turbo Fredriksson wrote:
Quoting "Dan Langille" <[EMAIL PROTECTED]>:
NOTE: any disabled jobs are renabled if you restart bacula-dir.
That wasn't nice :) It can be, and probaby is in most cases
Quoting Kern Sibbald <[EMAIL PROTECTED]>:
> On Thursday 23 March 2006 20:35, Turbo Fredriksson wrote:
>> Quoting "Dan Langille" <[EMAIL PROTECTED]>:
>> > NOTE: any disabled jobs are renabled if you restart bacula-dir.
>>
>> That wasn't nice :) It can be, and probaby is in most cases but
>> I'd sti
Kern Sibbald wrote:
Hello,
Please turn off return-receipts -- you will never get one from me and they are
annoying.
Apologies - this is a work email account and I need to default return
receipts on. I will endeavour to disable them for messages posted here
:)
On Thursday 23 March 2006 21:5
On Thursday 23 March 2006 20:35, Turbo Fredriksson wrote:
> Quoting "Dan Langille" <[EMAIL PROTECTED]>:
> > NOTE: any disabled jobs are renabled if you restart bacula-dir.
>
> That wasn't nice :) It can be, and probaby is in most cases but
> I'd still would want a way to permanently disable a clien
Hello,
Please turn off return-receipts -- you will never get one from me and they are
annoying.
On Thursday 23 March 2006 21:55, Rowdy wrote:
> Dan Langille wrote:
> > On 23 Mar 2006 at 15:41, Kern Sibbald wrote:
> >> Correct. Until I slipped a new command to 1.38.6-beta6 (for my vacation)
> >>
Dan Langille wrote:
On 23 Mar 2006 at 15:41, Kern Sibbald wrote:
Correct. Until I slipped a new command to 1.38.6-beta6 (for my vacation) :-)
That would be the disable/enable command:
$ bconsole -c /usr/local/etc/bconsole.conf
Connecting to Director ngaio:9101
1000 OK: ngaio-dir Version: 1.
Quoting "Dan Langille" <[EMAIL PROTECTED]>:
> NOTE: any disabled jobs are renabled if you restart bacula-dir.
That wasn't nice :) It can be, and probaby is in most cases but
I'd still would want a way to permanently disable a client... How
about a third option 'permanent'?
--
Why can't programm
On 23 Mar 2006 at 15:41, Kern Sibbald wrote:
> On Thursday 23 March 2006 14:00, Dan Langille wrote:
> > On 23 Mar 2006 at 13:48, Turbo Fredriksson wrote:
> > > Quoting Rowdy <[EMAIL PROTECTED]>:
> > > >> I'd like to disable this client
> > > >
> > > > I found that I had to comment the Job and the
On Thursday 23 March 2006 14:00, Dan Langille wrote:
> On 23 Mar 2006 at 13:48, Turbo Fredriksson wrote:
> > Quoting Rowdy <[EMAIL PROTECTED]>:
> > >> I'd like to disable this client
> > >
> > > I found that I had to comment the Job and the Client sections for the
> > > machine to be excluded.
> >
On Thursday 23 March 2006 13:59, Martin Simmons wrote:
> > On Thu, 23 Mar 2006 10:22:02 + (GMT), Alan Brown
> > <[EMAIL PROTECTED]> said:
> >
> > On Wed, 22 Mar 2006, Craig Dupree wrote:
> > > From looking at the Docs, and through the archives I think I can
> > > disable a client's back
On Thursday 23 March 2006 13:48, Turbo Fredriksson wrote:
> Quoting Rowdy <[EMAIL PROTECTED]>:
> >> I'd like to disable this client
> >
> > I found that I had to comment the Job and the Client sections for the
> > machine to be excluded.
>
> Is there any way of disabling a client temporarily by mod
We put all client related definitions (Job, FileSet, Schedule,
Client) in a separate file (include-.conf) which we include
in bacula-dir.conf; with such a setup it is easy judt to comment out
the include statement.
And it makes the config file much more readable..
Solution like this rea
On 23 Mar 2006 at 13:48, Turbo Fredriksson wrote:
> Quoting Rowdy <[EMAIL PROTECTED]>:
>
> >> I'd like to disable this client
> >
> > I found that I had to comment the Job and the Client sections for the
> > machine to be excluded.
>
> Is there any way of disabling a client temporarily by modify
> On Thu, 23 Mar 2006 10:22:02 + (GMT), Alan Brown <[EMAIL PROTECTED]>
> said:
>
> On Wed, 22 Mar 2006, Craig Dupree wrote:
>
> > From looking at the Docs, and through the archives I think I can disable a
> > client's backup by commenting out the Schedule line like this:
> >
> > Job
Quoting Rowdy <[EMAIL PROTECTED]>:
>> I'd like to disable this client
>
> I found that I had to comment the Job and the Client sections for the
> machine to be excluded.
Is there any way of disabling a client temporarily by modifying the
database directly (i.e. via SQL command and NOT touch any f
On Wed, 22 Mar 2006, Craig Dupree wrote:
From looking at the Docs, and through the archives I think I can disable a
client's backup by commenting out the Schedule line like this:
Job {
Name = "frodo"
Type = Backup
Level = incremental
Client = frodo
FileSet =
Never mind. My bad. When I upgraded, I installed into a new version
specific directory. The original person who installed bacula used / as
the install prefix, so out of habit, I went to /etc/bacula/ to make the
config edits, rather than the version specific directory where I had
moved the co
Craig Dupree wrote:
From looking at the Docs, and through the archives I think I can
disable a client's backup by commenting out the Schedule line like this:
Job {
Name = "frodo"
Type = Backup
Level = incremental
Client = frodo
FileSet = "windows"
In message <[EMAIL PROTECTED]> you wrote:
> From looking at the Docs, and through the archives I think I can
> disable a client's backup by commenting out the Schedule line like this:
We put all client related definitions (Job, FileSet, Schedule,
Client) in a separate file (include-.conf)
From looking at the Docs, and through the archives I think I can
disable a client's backup by commenting out the Schedule line like this:
Job {
Name = "frodo"
Type = Backup
Level = incremental
Client = frodo
FileSet = "windows"
Storage = tape0
#
24 matches
Mail list logo
