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....

Thanks.


2011/8/24 Eric Pratt <eric.pratt AT etouchpoint DOT com>:
> 2011/8/23 Carlos André <candrecn AT gmail DOT com>:
>> Running Jobs:
>> Writing: Incremental Backup job SRV10 JobId=61090 Volume=""
>>    pool="MON" device="IBM_TL_LTO3-0" (/dev/IBM_TL_LTO3-0)
>>    spooling=0 despooling=0 despool_wait=0
>>    Files=0 Bytes=0 Bytes/sec=0
>>    FDSocket closed
>>
>> -----------------------
>> *cancel jobid=61090
>> JobId 61090 is not running. Use Job name to cancel inactive jobs. ##
>> BUT these m....f... keep showing and f.. with my routines :/
>> -----------------------
>
> Have you tried doing what bacula says to do there and cancel the job
> by name instead of id?  If so, what does it say then?
>
> Eric
>

------------------------------------------------------------------------------
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