Re: [Bacula-users] Automated eject and automated mount of tapes

[Steven E. <el...@br...>]

Martin Schmid wrote:
> I have a DDS-3 DAT and it should eject as soon as a new tape is 
> requested and the new tape should be mounted automatically.
>
> I have a configuration that does all this except that it does not read 
> the fresh tape correctly. The tape is correctly ejected and the drive is 
> then polled at intervals. The new tape is then actually detected but 
> then the storage daemon falls into a status 'Device "DDS-2" (/dev/nst0) 
> open but no Bacula volume is currently mounted.'. But it actually _is_ a 
> bacula volume and a simple mount in bconsole makes the job continue.
>
> What is the correct combination of configurations to accomplish this - 
> if possible at all? I found some mails addressing versions 1.31 or 1.38 
> but I am using 2.0.3...
>
>   
I have a similar config that works for me, with 1.38 I used it on a DDS4 
drive, but now I'm using it with an LTO2.
> This is my config:
>
>   Automatic Mount = yes;               # when device opened, read it
>   Label Media = yes;                   # lets Bacula label unlabeled media
>   Always Open = no;
>   Volume Poll Interval = 5m
>   Close on Poll= Yes;
>   Removable Media = yes;
>   Random Access = no;
>   Maximum Open Wait = 3d          # 3 days in seconds
>   Offline On Unmount = Yes;          # keep this too
>
>   
The only obvious difference I see with my config is that I have "Always 
Open = Yes"--in case I've missed something, here is my device description:

Device {
  Name = LTO2
  Media Type = LTO2
  Archive Device = /dev/nst0
  Changer Device = /dev/sg0
  Automatic Mount = Yes
  Always Open = Yes
  Volume Poll Interval = 3 min
  Close On Poll = Yes
  Offline On Unmount = Yes
  Removable Media = Yes
  Random Access = No
  Maximum Job Spool Size = 21474836480
  Maximum Block Size = 262144
  Maximum Network Buffer Size = 262144
  Spool Directory = /backup/bacula/spool
  Alert Command = "sh -c 'smartctl -H -l error %c'"
  Label Media = Yes
}

The block size and network buffer size settings should be completely 
irrelevant--I did them to try to improve write performance (and at this 
point it is unclear if it helps).  I specify the changer device even 
though I don't have a changer just to make the Alert Command work--or so 
I recall--I don't actually have an LTO changer.

For me at least, this works as you suggest--if a tape is ejected either 
during a job due to a full, error or wrong tape condition, then when the 
correct tape is inserted it will just work.  On the other hand, if I 
explicitly unmount a tape, it will eject, but I'll have to explicitly 
mount the correct tape later.

Hope this helps,

-se