on the director:

ii  bacula-director-common                   
5.0.2-2.2+b1                        network backup, recovery and 
verification - Director common files
ii  bacula-director-mysql                    
5.0.2-2.2+b1                        network backup, recovery and 
verification - MySQL storage for Director

on sd:

ii  bacula-common                       5.2.6+dfsg-1~bpo60+1         
network backup, recovery and verification - common support files
ii  bacula-common-mysql                 5.2.6+dfsg-1~bpo60+1         
network backup, recovery and verification - MySQL common files
ii  bacula-sd                           5.2.6+dfsg-1~bpo60+1         
network backup, recovery and verification - storage daemon
ii  bacula-sd-mysql                     5.2.6+dfsg-1~bpo60+1         
network backup, recovery and verification - MySQL SD tools

It was my own fail. I tried to use an newer Version of bacula-sd to 
avoid the segmentation error. The true Error Msg of bacula-dir with the 
same versions on both side:


20-Jul 09:35 lx02-oracle-ourcustomer-dir JobId 4147: Start Backup JobId 
4147, Job=lx01-gw01-ourcustomer.2012-07-20_09.35.31_18
20-Jul 09:35 lx02-oracle-ourcustomer-dir JobId 4147: Fatal error:
      Storage daemon didn't accept Device "IBM-LTO3-sd" command.
20-Jul 09:35 lx02-oracle-ourcustomer-dir JobId 4147: Error: Bacula 
lx02-oracle-ourcustomer-dir 5.0.2 (28Apr10): 20-Jul-2012 09:35:33
   Build OS:               i486-pc-linux-gnu debian squeeze/sid
   JobId:                  4147
   Job:                    lx01-gw01-ourcustomer.2012-07-20_09.35.31_18
   Backup Level:           Full
   Client:                 "lx01-gw01-ourcustomer-fd" 5.0.2 (28Apr10) 
i486-pc-linux-gnu,debian,squeeze/sid
   FileSet:                "Full Set" 2007-05-22 17:14:12
   Pool:                   "DonnerstagPool" (From User input)
   Catalog:                "MyCatalog" (From Client resource)
   Storage:                "IBM-LTO3-dir" (From Job resource)
   Scheduled time:         20-Jul-2012 09:35:27
   Start time:             20-Jul-2012 09:35:33
   End time:               20-Jul-2012 09:35:33
   Elapsed time:           0 secs
   Priority:               10
   FD Files Written:       0
   SD Files Written:       0
   FD Bytes Written:       0 (0 B)
   SD Bytes Written:       0 (0 B)
   Rate:                   0.0 KB/s
   Software Compression:   None
   VSS:                    no
   Encryption:             no
   Accurate:               no
   Volume name(s):
   Volume Session Id:      1
   Volume Session Time:    1342769650
   Last Volume Bytes:      64,512 (64.51 KB)
   Non-fatal FD errors:    0
   SD Errors:              0
   FD termination status:
   SD termination status:
   Termination:            *** Backup Error ***


Syslog on sd:

Jul 20 09:35:30 lx03-baculasd-ourcustomer bacula-sd: Bacula interrupted 
by signal 11: Segmentation violation

after getting this error Msg the sd-service crashing down

ps xa|grep bacula-sd
3897 pts/1    S+     0:00 grep bacula-sd

regards

Tobias

Am 19.07.2012 21:35, schrieb Dan Langille:
> 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?
>


-- 
# Stegbauer Datawork
# Tobias Dinse
# +49 (8571) 922213
# Oberjulbachring 9, 84387 Julbach


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