Piotr Gbyliczek wrote:
> On Saturday 18 October 2008 15:30:46 T. Horsnell wrote:
>
> And in the RunAfter script I have
> echo "run job=BackupCatalog yes" | /usr/local/bacula/bin/bconsole
> echo "enable job=Job1" | /usr/local/bacula/bin/bconsole
>
That is reall
Alan Brown schrieb:
> I wonder if there's a more general way of doing this than having 1
> RunBefore/RunAfter per job.
You could put
RunScript {
RunsWhen = After
RunsOnClient = no
RunsOnFailure = yes
Command = "/path/to/script %c"
}
into your JobDefs resource so it gets included
On Saturday 18 October 2008 15:30:46 T. Horsnell wrote:
> >>>And in the RunAfter script I have
> >>> echo "run job=BackupCatalog yes" | /usr/local/bacula/bin/bconsole
> >>> echo "enable job=Job1" | /usr/local/bacula/bin/bconsole
> >>
> >>That is really, really clever trick. Thanks for tip, Terr
On Thu, 16 Oct 2008, Arno Lehmann wrote:
> > I had this problem from the start. I ended up with a line in my
> > RunBefore script which disabled the backup job:
> >
> >echo "disable job=Job1" | /usr/local/bacula/bin/bconsole
> >
> > This disables any further scheduling of Job1 but leaves the c
Scripsit T. Horsnell die 18.10.2008 16:30:
>> My only question is if the job fails for some reason doesn't that
>> leave it disabled because the Run After script does not get executed?
>
> Yes, this is a risk. I dont know whether the RunAfter script gets run if
> the actual backup itself fails -
John Drescher wrote:
> On Fri, Oct 17, 2008 at 5:54 AM, Piotr Gbyliczek <[EMAIL PROTECTED]> wrote:
>
>>On Thursday 16 October 2008 17:40:16 T. Horsnell wrote:
>>
>>
>>>I had this problem from the start. I ended up with a line in my
>>>RunBefore script which disabled the backup job:
>>>
>>> echo
On Fri, Oct 17, 2008 at 5:54 AM, Piotr Gbyliczek <[EMAIL PROTECTED]> wrote:
> On Thursday 16 October 2008 17:40:16 T. Horsnell wrote:
>
>> I had this problem from the start. I ended up with a line in my
>> RunBefore script which disabled the backup job:
>>
>>echo "disable job=Job1" | /usr/local
On Thursday 16 October 2008 17:40:16 T. Horsnell wrote:
> I had this problem from the start. I ended up with a line in my
> RunBefore script which disabled the backup job:
>
>echo "disable job=Job1" | /usr/local/bacula/bin/bconsole
>
> This disables any further scheduling of Job1 but leaves th
Hi,
16.10.2008 18:40, T. Horsnell wrote:
> Arno Lehmann wrote:
>> Hi,
>>
>> 16.10.2008 15:53, John Drescher wrote:
>>
> Does the first job take more than 1 day?
Yes, that is true in this case. But is this making any difference ?? With
running full backup there shouldn't be any next j
Arno Lehmann wrote:
> Hi,
>
> 16.10.2008 15:53, John Drescher wrote:
>
Does the first job take more than 1 day?
>>>
>>>Yes, that is true in this case. But is this making any difference ?? With
>>>running full backup there shouldn't be any next job upgraded to full prior to
>>>finish of first
Hi,
16.10.2008 15:53, John Drescher wrote:
>>> Does the first job take more than 1 day?
>> Yes, that is true in this case. But is this making any difference ?? With
>> running full backup there shouldn't be any next job upgraded to full prior to
>> finish of first one.
>>
> The reason I ask is whe
On Thursday 16 October 2008 15:22:39 John Drescher wrote:
> > On Thursday 16 October 2008 14:36:47 Piotr Gbyliczek wrote:
> >> I didn't called it huge. But it is quite big imho if you doing it over
> >> cloud, not through corporate network with stable 100Mb or even 1Tb
> >> connections.
> I have 1G
> On Thursday 16 October 2008 14:36:47 Piotr Gbyliczek wrote:
>> I didn't called it huge. But it is quite big imho if you doing it over
>> cloud, not through corporate network with stable 100Mb or even 1Tb
>> connections.
>
> Nice thing I've did here. I wish to have 1Tb connection somewhere... 1Gb
On Thursday 16 October 2008 14:36:47 Piotr Gbyliczek wrote:
> I didn't called it huge. But it is quite big imho if you doing it over
> cloud, not through corporate network with stable 100Mb or even 1Tb
> connections.
Nice thing I've did here. I wish to have 1Tb connection somewhere... 1Gb
should
>> Does the first job take more than 1 day?
>
> Yes, that is true in this case. But is this making any difference ?? With
> running full backup there shouldn't be any next job upgraded to full prior to
> finish of first one.
>
The reason I ask is when the next backup is scheduled to begin if the
pr
On Thursday 16 October 2008 14:21:40 John Drescher wrote:
> > I have few backups over network, which are quite big (50GB and 250GB for
> > example).
>
> I do not consider this a huge backup. I have done 2TB+ backups
> successfully with bacula.
I didn't called it huge. But it is quite big imho if y
> I have few backups over network, which are quite big (50GB and 250GB for
> example).
I do not consider this a huge backup. I have done 2TB+ backups
successfully with bacula.
>I'm expecting them to be quite long jobs, and I'm working on
> getting SD in same cabinet for them, but that ideal soluti
17 matches
Mail list logo
