Yes I know. AND I have NOT intention to run two Directors same time,
they just sync, and if one machine crashes on site A, I got another
one warm on site B to recover in few seconds. But something gone wrong
and secondary started bacula director while primary still ok. After 4
years using bacula (and sync) it's first time this happen...
And what makes my problem not so obvious is because due the sync, name
of machines are the same, then, all logs look like erros and
scheduling, starting jobs, etc, have same director name.


2011/8/24 John Drescher <drescherjm AT gmail DOT com>:
> 2011/8/24 Carlos André <candrecn AT gmail DOT com>:
>> Thanks ppl, but I "SOLVED" this (stupid) problem :/.
>>
>> My Bacula cluster got a bug then secondary Bacula Director started up
>> (somehow - I've alot of checks to avoid this) with primary still
>> on-line >:/
>>
>> Since I canceled (restarted it) the jobs just in the primary Director,
>> my secondary still kept the schedule and pushed all those 'ghost jobs'
>> to SD.
>>
>> Damn, this f... thing almost drive me crazy O_o....
>>
>
> Bacula does not support using more than 1 director. The developers
> will tell you this.
>
> John
>

------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management 
Up to 160% more powerful than alternatives and 25% more efficient. 
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users