Hi Yvan,

If it is of any consolation, it took me one whole month to make Bacula
work but at the end of the day, it was time and effort well spent.

Now, back to the subject of your problems. It seems more to do with
the HW setting than Bacula. On the tape library, what settings do you
have? Following is what I have.

Library Mode : Random
Auto clean    : Disabled
Barcode label length Reported to host 6

Since my library is IBM original, the IBM web-based admin page might
be different from what you have for Dell.

At the OS level, use the generic st/nst drivers. DO NOT use the stuff
provided by IBM/Dell. Gave me nothing but head ache.

In my bacula-sd.conf file, I have the "Maximum Concurrent Jobs" set to
"2" since I have two tape drives.

In my bacula-dir.conf file, I have "Maximum Concurrent Jobs" set to "20".

Also, in my mtx-changer script, I added an extra function.

wait_for_drive() {
  i=0
  while [ $i -le 300 ]; do  # Wait max 300 seconds
    if mt -f $1 status | grep "${ready}" >/dev/null 2>&1; then
      break
    fi
    debug "Device $1 - not ready, retrying..."
    sleep 1
    i=`expr $i + 1`
  done
}

The function is called as follows which is inserted in part of the
"case $cmd in".

# Increase the sleep time if you have a slow device
# or remove the sleep and add the following:
      #sleep 15
      wait_for_drive $device    # Added this option WH. 2007-10-12
      exit $rtn
      ;;

HTH,

Win

> Message: 21
> Date: Tue, 12 May 2009 14:36:42 +0200
> From: yvan <yvan AT skywalker.is-a-chef DOT com>
> Subject: Re: [Bacula-users] Tape MTEOM error with Dell TL2000 (IBM >
>        TS3100)
> Cc: bacula-users AT lists.sourceforge DOT net
> Message-ID: <4A096D5A.6030803 AT skywalker.is-a-chef DOT com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hey!
>
> Unfortunatelly I already used that trick :), the firmware has been
> upgraded for both the drive and the autochanger... And it didn't change
> at all.
>
> I had a bunch of backup launched, and it seems that the further it has
> to seek on the take to position to append data, the more subject of
> errors it is. The 5 1st jobs on the tape are usually allright, but then
> it begins to be unpredictive.
>
> To go on, I've noticed that I can update the tape status and put it back
> from "Error" to "Append", and 50% of the time the job waiting for a new
> tape starts successfully.  I have a pack of 16 tapes, and it seems it's
> with all of them. Now I have a tape that is stuck to 100G, and can't
> write anything further, and one that has successfully gone to 130Gb
> (each test job is 12 Gb).
>
> I really like bacula and how it manage the pools, volumes, schedules and
> clients, and I 'll try to stay with. Now i'm trying to setup a
> workaround, to use the tapes only once : to write only full bakckups
> once a week, 'cause that machine is a dedicated backup server with loads
> of disc space, and incremental are done with "rsync" on disk. Then I can
> maybe just dump the local filesystem on 2 tapes (i need 1.5Tb for every
> full backup, so it means 2x LTO4 800Gb-1.6TB).
>
> For Hayden : the "cap" is a command of the "btape" utility, that shows
> every configuration option set in the storage config file for that
> device. Just type "cap" in  btape...
>
> Regards
> Yvan Broccard

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users