Zack,

I'm using bacula 1.38.2. so I use the auto-changer resource. Here's what I have:

Autochanger {
 Name = "AutoPakChanger"
 Device = AutoPakDrive1
 Changer Device = /dev/sg2
 Changer Command = "/etc/bacula/mtx-changer %c %o %S %a %d"
}

Device {
  Name = AutoPakDrive1
  Media Type = AutoPakVXA17
  Archive Device = /dev/nst0
  AutomaticMount = yes;
  AlwaysOpen = yes;
  RemovableMedia = yes;
  RandomAccess = no;
  Drive Index = 0
  AutoChanger = yes
  Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
}

You may also need to edit the following part of the mtx-changer script...

# enable the following line if you need to eject the cartridge
#     mt -f $device offline

An easy way to test if the mtx-changer script works for your autoloader is to run it by hand. Or you can use 'btape autochanger'

You might want to double-check using /dev/nst0 vs /dev/st0 since I use nst0 and you have st0 since the VXA drives are non-autorewinding devices. Also, make sure that 'btape test' works. I got by without the "Hardware End of Medium and Fast Forward Space File directives.

If you haven't already I'd also recommend getting vxaTool from Exabyte, which lets you enable/disable hardware compression on the VXA drives.

I hope that helps,
Keith

Zachariah Mully wrote:

Hello all-
        I've got a new VXA2 packetloader that appears to have a problem
changing tapes. Can somebody else out there with one of these please
help me verify my settings? I'm running Bacula 1.36.2 on Debian 3.1.

Device {
      Name = VXA
      Media Type = 8mm
      Archive Device = /dev/st0
      Autochanger = Yes
      Changer Device = /dev/sg1
      Changer Command = "/etc/bacula/scripts/mtx-changer %c %o %S %a %
d"
      Maximum Changer Wait = 240 # seconds
      Alert Command = "sh -c 'tapeinfo -f %c | grep TapeAlert|cat'"
      Always Open = Yes
      AutomaticMount = Yes
      Removable media = Yes
      Random access = No
      Hardware End of Medium = Yes
      Fast Forward Space File = Yes
      Maximum Network Buffer Size = 65536
}
        My backups have begun to fail with:
07-Dec 01:13 backup-sd: mojojojo.2005-12-07_01.05.01 Fatal error: Cannot
write block. Device at EOM.

Many thanks,
Zack




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to