Hi Leo,
Em Sex, 2014-09-12 às 15:17 -0300, Leo escreveu:
> Gean, you are using multiple catalogs?
No Leo, I've a single catalog, de default one. See the Ana's suggestion
above, that problably will help you.
Best regards,
Gean
-
Hi Ana,
Em Sex, 2014-09-12 às 23:10 -0300, Ana Emília M. Arruda escreveu:
> ... You can try to put a Run Script directive on job definition like
> this:
> RunScript {
> RunsWhen = After
> RunsOnFailure = yes
> Command = "/path/myscript.sh"
> }
> And you could do some kind of shell scr
Hi Gean,
Just an idea... Maybe it should work and do what you want. You can try to
put a Run Script directive on job definition like this:
RunScript {
RunsWhen = After
RunsOnFailure = yes
Command = "/path/myscript.sh"
}
And you could do some kind of shell script that could look for a
Dear Kern,
Em Ter, 2014-09-09 às 17:21 +0200, Kern Sibbald escreveu:
> ...If you want to clearly separate Volume by clients, jobs, or by
> some other criteria, you probably should be using different Pools.
> Different pools are the most reliable way to ensure that only
> particular jobs, clients
Hello,
The problem is basically because you have one idea about how to do
backups and Bacula has another idea. You want Bacula to put data
on the *exact* Volume that you specify. The whole logic of Bacula
is that Bacula will deal with what is on volumes a
Dear users,
I'm using file-based backups and configurated Bacula[bacula-dir Version:
5.2.13 (19 February 2013)] to write one volume per job, with an
exclusive label containing the client name, data and time as shown
bellow in the config files attached.
The problems is:
1º Why Bacula creates a v
