On Jan 17, 2008, at 11:39 AM, Reynier Perez Mira wrote:
>> I don't know that feature. You get me a URL to read, and
>> I'll tell you.
>
> Well I found it in rel-bacula.pdf manual at page 117.
Found what? :)
I had to dig around in my deleted mail to find out what we were
talking about.
Stri
> I don't know that feature. You get me a URL to read, and
> I'll tell you.
Well I found it in rel-bacula.pdf manual at page 117.
Ing. Reynier Pérez Mira
-
This SF.net email is sponsored by: Microsoft
Defy all challenge
On Jan 17, 2008, at 9:52 AM, Reynier Perez Mira wrote:
> Hi every:
> I'm still reading the documentation and have a few questions:
> 1. Is the JobDefs mandatory?
No.
> 2. If the answer is yes then how much I can have in the same
> bacula-dir.conf file? (One or various for backup, one or var
On Tue, Aug 29, 2006 at 12:14:39PM +0200, Arno Lehmann wrote:
>
> No problem here, I think. This behaviour is well known to me, and I
> simply ignore it (but I don't really need the expected volume
> information). I suppose it's because Bacula will not do the whole
> routine of finding which volum
On Tue, Aug 29, 2006 at 11:04:33AM +0200, Uwe Schuerkamp wrote:
> From: Uwe Schuerkamp <[EMAIL PROTECTED]>
> To: "Masopust, Christian" <[EMAIL PROTECTED]>
> Cc: Bacula Users Mailing List
> Date: Tue, 29 Aug 2006 11:04:33 +0200
> Subject: Re: [Bacula-use
(Retry, due to mail provider being blaclisted by sf...)
Hi,
On 8/29/2006 10:07 AM, Uwe Schuerkamp wrote:
> Hi folks,
>
> I have defined the following jobdefs entry:
...
> Job {
> Name = "host01"
> Client = host01-fd
> JobDefs = "full_tuesday"
> Pool = Default
> Incremental Backup Pool
Hello folks,
sorry to follow up on myself, but it looks like removing the pool
overrides from the schedule definition fixed the problem like so:
Schedule {
Name = "FullMonday"
Run = Level=Full FullPool=Default Pool=Default Mon at 11:00
Run = Level=Incremental tue-sun at 19:05
}
Now, the h
On Tue, Aug 29, 2006 at 10:45:25AM +0200, Masopust, Christian wrote:
> From: "Masopust, Christian" <[EMAIL PROTECTED]>
> To: Uwe Schuerkamp <[EMAIL PROTECTED]>,
> Bacula Users Mailing List
> Date: Tue, 29 Aug 2006 10:45:25 +0200
> Subject: RE: [Bacula-
Hello Uwe,
I'm not totally sure but this also depends on the configuration of your
pools. So please could you also post it?
Chris
--
"I sense much NT in you, NT leads to Blue Screen.
Blue Screen leads to downtime, downtime leads to suffering. NT is the path to
the darkside."
- Unknown Unix
Because you can have a JobDef that references the client, or not, as you
choose. This way you could have a JobDef to help you generalize 6
different backup jobs on the same host, right?
Generalization permits flexibility.
On Thu, Aug 03, 2006 at 11:39:30AM +0100, Duarte Santos wrote:
> Yes, what
Yes, what i don't understand is why the Jobdefs don't work without a
Client option. If Jobdefs can work for every job of every client,
without putting the actual Clients on the Jobdefs option, why is there a
Client option?
On Thu, 2006-08-03 at 12:18 +0800, Troy Daniels wrote:
> Hi,
>
>
>
> Dua
Hi,
Duarte Santos wrote:
> Hello,
>
> Is it needed to have 1 JobDefs for each Job?
> Why is there a "client" option in JobDefs, when i can map a JobDefs on
> each Job definition.
>
> Duarte Santos
>
>
By definition, jobdefs is 'Job Defaults' and you set up defaults here
for all the jobs t
Andrew Paterson wrote:
> Hi All,
> Is it allowable in bacula-dir.conf to have one 'JobDefs' directive
> referencing another one?
> (I'm trying to tidy up my config files & remove some of th duplication).
On the one hand, the documentation of the JobDefs resource says:
"The JobDefs resource
13 matches
Mail list logo