> BTW, I don't think you need the VXA resource in the director; just the
> one for "Auto".
>
It is not needed. It can be useful for changers with 2 or more drive
as in this case you can force operations (jobs, label barcodes ...) on
any tape drive in the archive.
John
Richard White wrote:
> and from bacula-dir.conf:
>
> Storage {
> Name = Auto
> Address = 10.1.0.17
> SDPort = 9103
> Password = "ourpassword"
> Device = "Auto"
> Media Type = VXA-3
Autochanger = yes
> }
>
> Storage {
> Name = VXA
> Address = 10.1.0.17
> SDPort = 9103
> Pas
Hi,
28.08.2007 00:31,, Richard White wrote::
> Bacula 2.2.0 running on SLES 10 with an Ecrix 1.10 autoloader. Here is the
> pertinent section of bacula-sd.conf:
>
> # Autochanger resource
> Autochanger {
> Name = "Auto"
> Device = VXA3
> Changer Device = /dev/sg1
> Changer Command = "/ba
> Yes. I was concerned about getting the backup running and finished this
> morning. I did not note the error messages, but here is a section of the log
> file:
>
> 26-Aug 00:10 bacula-sd: End of Volume "A004" at 224:7722 on device "VXA3"
> (/dev/nst0). Write of 64512 bytes got -1.
> 26-Aug
>> When the weekend backup ran it filled up the tape in the drive (A004
> from slot 4)and removed it, but it did not load the next tape. I could not
> get it to mount A005 with any bconsole command. This is the format I
> tried:
>>
> Do you have the exact error? Did you try a simple mou
On 8/27/07, Richard White <[EMAIL PROTECTED]> wrote:
> Bacula 2.2.0 running on SLES 10 with an Ecrix 1.10 autoloader. Here is the
> pertinent section of bacula-sd.conf:
>
> # Autochanger resource
> Autochanger {
> Name = "Auto"
> Device = VXA3
> Changer Device = /dev/sg1
> Changer Command
