Bacula 1.36.3 on Fedora Core 4
Exabyte VXA Packetloader 1x10 1U
Bacula seems able to successfully query this autochanger if it's loaded, and I
can unload it using the unmount command in bconsole, but instead of loading the
drive when running a backup or restore job, it prompts for a manual mount:
20-Oct 13:59 sandy-sd: 3301 Issuing autochanger "loaded drive 0" command.
20-Oct 13:59 sandy-sd: 3302 Autochanger "loaded drive 0", result: nothing
loaded.
20-Oct 13:59 sandy-sd: RestoreFiles.2006-10-20_13.55.44 Warning: acquire.c:146
Couldn't rewind device "VXA-Drive" (/dev/nst0): ERR=dev.c:678 Rewind error on
"VXA-Drive" (/dev/nst0). ERR=No medium found.
20-Oct 13:59 sandy-sd: Please mount Volume "A0000001" on Storage Device
"VXA-Drive" (/dev/nst0) for Job RestoreFiles.2006-10-20_13.55.44
20-Oct 14:01 sandy-sd: 3301 Issuing autochanger "loaded drive 0" command.
20-Oct 14:01 sandy-sd: 3302 Autochanger "loaded drive 0", result: nothing
loaded.
20-Oct 14:01 sandy-sd: RestoreFiles.2006-10-20_13.55.44 Warning: acquire.c:146
Couldn't rewind device "VXA-Drive" (/dev/nst0): ERR=dev.c:678 Rewind error on
"VXA-Drive" (/dev/nst0). ERR=No medium found.
20-Oct 14:01 sandy-sd: Please mount Volume "A0000001" on Storage Device
"VXA-Drive" (/dev/nst0) for Job RestoreFiles.2006-10-20_13.55.44
Here are the storage definitions from my bacula-sd.conf:
Autochanger {
Name = "VXA-Library"
Device = "VXA-Drive"
Changer Command = "/etc/bacula/mtx-changer %c %o %S %a %d"
Changer Device = /dev/sg4
}
Device {
Maximum Changer Wait = 120
Name = "VXA-Drive"
Archive Device = /dev/nst0
Device Type = Tape
Media Type = "VXA-2"
Autochanger = Yes
Changer Device = /dev/sg4
Drive Index = 0
Autoselect = yes
AlwaysOpen = yes
Removable Media = yes
Random Access = no
Label Media = yes
Automatic Mount = yes;
}
Isn't that what autochangers are supposed to be for?
BTW, I can load, unload, and do any of the various tape library operations from
mtx-changer at the command line. The btape test and btape autochanger test
both pass. The btape multiple tape fill command also fails to load the drive,
but from what I've seen on the list that's a known btape bug, and shouldn't
prevent bacula from properly using the autochanger the way it doesn't seem to
be doing.
If I try unmount and mount commands from bconsole I get the following:
*unmount
Automatically selected Storage: VXA-Tape
Connecting to Storage daemon VXA-Tape at sandy.siderean.com:9103 ...
3301 Issuing autochanger "loaded drive 0" command.
3302 Autochanger "loaded drive 0", result is Slot 8.
3307 Issuing autochanger "unload slot 8, drive 0" command.
3001 Device "VXA-Drive" (/dev/nst0) unmounted.
*mount
Automatically selected Storage: VXA-Tape
3301 Issuing autochanger "loaded drive 0" command.
3302 Autochanger "loaded drive 0", result: nothing loaded.
3301 Issuing autochanger "loaded drive 0" command.
3302 Autochanger "loaded drive 0", result: nothing loaded.
3905 Device "VXA-Drive" (/dev/nst0) open but no Bacula volume is mounted.
If this is not a blank tape, try unmounting and remounting the Volume.
So bacula seems to know how to unload the drive but not how to load it, and
there doesn't seem to be any "load" command I can use to tell bconsole to load
the tape either.
Ideas, anyone?
John J. Felczak
Build & Integration Manager
Acting IT Manager
Siderean Software, Inc.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
