On 2012-07-19 13:11, Martin Simmons wrote:
>>>>>> On Thu, 19 Jul 2012 11:35:16 +0200, Tobias Dinse said:
>>
>> yesterday we have moved our old physical Servers to an esxi 5
>> Environment. I created an new VM with Debian 6 x64 - Hardware 
>> passtrough
>> for the Controller (h200 / IBM LTO3 Streamer) and bacula-sd-mysql
>> Version 5.2.6
>>
>> I can label / mount all Volumes fine. But if I start an Backup Job 
>> the
>> bacula-sd services crasehs with the follow messages:
>> ...
>> lx03-baculasd-ourcustomer-sd: job.c:95-0 >dird: 3915 Bad Job 
>> command. stat=-1 CMD: JobId=4143 
>> job=lx01-gw01-ourcustomer.2012-07-19_11.24.06_08 
>> job_name=lx01-gw01-ourcustomer client_name=lx01-gw01-ourcustomer-fd 
>> type=66 level=70 FileSet=Full
Set NoAttr=0 SpoolAttr=0 
>> FileSetMD5=uRUmnm122BMpY7QWJj/eCC SpoolData=1 WritePartAfterJob=1 
>> PreferMountedVols=1 SpoolSize=0 Resched=2616184
>
> Looks like you need to upgrade the version of Bacula that is running 
> the
> bacula-dir to 5.2.6 as well (or both to 5.2.10).

The issue: both bacula-dir and bacula-sd *MUST ALWAYS* be the same 
version.

The clue is the 'Bad Job command', which means the SD was asking to do 
something it did not understand.

Have you put both the SD and the DIR to the same version?

Did that fix the problem?

-- 
Dan Langille - http://langille.org/

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users