quantum superloader3 - Veritas Backup Exec

This is a discussion on quantum superloader3 - Veritas Backup Exec ; Hi, We have recently bought a quantum superloader3 but this does not get recognized bij backup exec as a robot. When I use scan all on the console netware sees the tape drive and autoloader on lun 0 and lun ...

+ Reply to Thread
Results 1 to 12 of 12

Thread: quantum superloader3

  1. quantum superloader3


    Hi,

    We have recently bought a quantum superloader3 but this does not get recognized
    bij backup exec as a robot.

    When I use scan all on the console netware sees the tape drive and autoloader
    on lun 0 and lun 1 the loader gets recognized as uhdl.

    When I use bediag /s /c none of the autoloader is seen.
    Also in backup exec no robot shows up.

    PSNW66-1:list storage adapters
    0x00 [V024-A0] Legacy FLOPPY Controller [slot 0]
    0x01 [V024-A0-D1:0] Legacy Floppy
    0x02 [V100-A100] USB UHCI Controller [slot 0]
    0x03 [V100-A101] USB UHCI Controller [slot 0]
    0x04 [V100-A102] USB EHCI Controller [slot 0]
    0x05 [V025-A1] Novell IDE/ATA/ATAPI/SATA Host Adapter Module [slot 0]
    0x11 [V025-A1-D0:0] TEAC DV-28E-N f/w:C.6B
    0x06 [V504-A2] HP Unified RAID Driver [slot 10017]
    0x08 [V504-A2-D0:0] HP Smart Array 6i Slot 0 ID 0 LUN 0
    0x07 [V358-A3] LSI_53C1030:00002 [slot 2]
    0x13 [V358-A3-D5:1] QUANTUM UHDL 0043
    0x12 [V358-A3-D5:0] QUANTUM DLT-V4 0800

    **** Start of BEDIAG results ****

    Fileserver Name: PSNW66-1

    CMD Host = BECDM.CDM
    Number of Host Adapters = 3

    Host Adapter 0 CPQRAID.HAM HP Unified RAID
    SCSI ID = 0 Lun = 2 HP LOGICAL VOLUME (2.58),

    Host Adapter 1 LSIMPTNW.HAM LSI_53C1030:0000
    SCSI ID = 5 Lun = 0 QUANTUM DLT-V4 (0800), *

    Host Adapter 2 Vetitas VirtHBA Vetitas VirtMGR

    Hope you can help or is it just not supported ?

    Regards,
    Bas



  2. Re: quantum superloader3

    Bas Smeelen wrote:

    >
    > Hi,
    >
    > We have recently bought a quantum superloader3 but this does not get
    > recognized bij backup exec as a robot.
    >
    > When I use scan all on the console netware sees the tape drive and
    > autoloader on lun 0 and lun 1 the loader gets recognized as uhdl.
    >
    > When I use bediag /s /c none of the autoloader is seen.
    > Also in backup exec no robot shows up.
    >
    > PSNW66-1:list storage adapters
    > 0x00 [V024-A0] Legacy FLOPPY Controller [slot 0]
    > 0x01 [V024-A0-D1:0] Legacy Floppy
    > 0x02 [V100-A100] USB UHCI Controller [slot 0]
    > 0x03 [V100-A101] USB UHCI Controller [slot 0]
    > 0x04 [V100-A102] USB EHCI Controller [slot 0]
    > 0x05 [V025-A1] Novell IDE/ATA/ATAPI/SATA Host Adapter Module [slot
    > 0] 0x11 [V025-A1-D0:0] TEAC DV-28E-N f/w:C.6B
    > 0x06 [V504-A2] HP Unified RAID Driver [slot 10017]
    > 0x08 [V504-A2-D0:0] HP Smart Array 6i Slot 0 ID 0 LUN 0
    > 0x07 [V358-A3] LSI_53C1030:00002 [slot 2]
    > 0x13 [V358-A3-D5:1] QUANTUM UHDL 0043
    > 0x12 [V358-A3-D5:0] QUANTUM DLT-V4 0800
    >
    > **** Start of BEDIAG results ****
    >
    > Fileserver Name: PSNW66-1
    >
    > CMD Host = BECDM.CDM
    > Number of Host Adapters = 3
    >
    > Host Adapter 0 CPQRAID.HAM HP Unified RAID
    > SCSI ID = 0 Lun = 2 HP LOGICAL VOLUME (2.58),
    >
    > Host Adapter 1 LSIMPTNW.HAM LSI_53C1030:0000
    > SCSI ID = 5 Lun = 0 QUANTUM DLT-V4 (0800), *
    >
    > Host Adapter 2 Vetitas VirtHBA Vetitas VirtMGR
    >
    > Hope you can help or is it just not supported ?
    >
    > Regards,
    > Bas


    First of all - is the drive on the HCL?

    http://support.veritas.com/docs/282348

    You should also try this:

    http://support.veritas.com/docs/278402


  3. Re: quantum superloader3


    "Chris" wrote:
    >Bas Smeelen wrote:
    >
    >>
    >> Hi,
    >>
    >> We have recently bought a quantum superloader3 but this does not get
    >> recognized bij backup exec as a robot.
    >>
    >> When I use scan all on the console netware sees the tape drive and
    >> autoloader on lun 0 and lun 1 the loader gets recognized as uhdl.
    >>
    >> When I use bediag /s /c none of the autoloader is seen.
    >> Also in backup exec no robot shows up.
    >>
    >> PSNW66-1:list storage adapters
    >> 0x00 [V024-A0] Legacy FLOPPY Controller [slot 0]
    >> 0x01 [V024-A0-D1:0] Legacy Floppy
    >> 0x02 [V100-A100] USB UHCI Controller [slot 0]
    >> 0x03 [V100-A101] USB UHCI Controller [slot 0]
    >> 0x04 [V100-A102] USB EHCI Controller [slot 0]
    >> 0x05 [V025-A1] Novell IDE/ATA/ATAPI/SATA Host Adapter Module [slot
    >> 0] 0x11 [V025-A1-D0:0] TEAC DV-28E-N f/w:C.6B
    >> 0x06 [V504-A2] HP Unified RAID Driver [slot 10017]
    >> 0x08 [V504-A2-D0:0] HP Smart Array 6i Slot 0 ID 0 LUN 0
    >> 0x07 [V358-A3] LSI_53C1030:00002 [slot 2]
    >> 0x13 [V358-A3-D5:1] QUANTUM UHDL 0043
    >> 0x12 [V358-A3-D5:0] QUANTUM DLT-V4 0800
    >>
    >> **** Start of BEDIAG results ****
    >>
    >> Fileserver Name: PSNW66-1
    >>
    >> CMD Host = BECDM.CDM
    >> Number of Host Adapters = 3
    >>
    >> Host Adapter 0 CPQRAID.HAM HP Unified RAID
    >> SCSI ID = 0 Lun = 2 HP LOGICAL VOLUME (2.58),
    >>
    >> Host Adapter 1 LSIMPTNW.HAM LSI_53C1030:0000
    >> SCSI ID = 5 Lun = 0 QUANTUM DLT-V4 (0800), *
    >>
    >> Host Adapter 2 Vetitas VirtHBA Vetitas VirtMGR
    >>
    >> Hope you can help or is it just not supported ?
    >>
    >> Regards,
    >> Bas

    >
    >First of all - is the drive on the HCL?
    >
    >http://support.veritas.com/docs/282348
    >

    Yep, it's a quantum DLT-V$ and functioning very well as a standalone drive
    only the hardware compression is not working

    >You should also try this:
    >
    >http://support.veritas.com/docs/278402
    >


    This looks more like it, I will try this option for the lsimptnw driver and
    see if it helps, hmm, I can unload it and load it with this option, can't
    I.

    THX in advance.



  4. Re: quantum superloader3


    "Bas" wrote:
    >
    >"Chris" wrote:
    >>Bas Smeelen wrote:
    >>
    >>>
    >>> Hi,
    >>>
    >>> We have recently bought a quantum superloader3 but this does not get
    >>> recognized bij backup exec as a robot.
    >>>
    >>> When I use scan all on the console netware sees the tape drive and
    >>> autoloader on lun 0 and lun 1 the loader gets recognized as uhdl.
    >>>
    >>> When I use bediag /s /c none of the autoloader is seen.
    >>> Also in backup exec no robot shows up.
    >>>
    >>> PSNW66-1:list storage adapters
    >>> 0x00 [V024-A0] Legacy FLOPPY Controller [slot 0]
    >>> 0x01 [V024-A0-D1:0] Legacy Floppy
    >>> 0x02 [V100-A100] USB UHCI Controller [slot 0]
    >>> 0x03 [V100-A101] USB UHCI Controller [slot 0]
    >>> 0x04 [V100-A102] USB EHCI Controller [slot 0]
    >>> 0x05 [V025-A1] Novell IDE/ATA/ATAPI/SATA Host Adapter Module [slot
    >>> 0] 0x11 [V025-A1-D0:0] TEAC DV-28E-N f/w:C.6B
    >>> 0x06 [V504-A2] HP Unified RAID Driver [slot 10017]
    >>> 0x08 [V504-A2-D0:0] HP Smart Array 6i Slot 0 ID 0 LUN 0
    >>> 0x07 [V358-A3] LSI_53C1030:00002 [slot 2]
    >>> 0x13 [V358-A3-D5:1] QUANTUM UHDL 0043
    >>> 0x12 [V358-A3-D5:0] QUANTUM DLT-V4 0800
    >>>
    >>> **** Start of BEDIAG results ****
    >>>
    >>> Fileserver Name: PSNW66-1
    >>>
    >>> CMD Host = BECDM.CDM
    >>> Number of Host Adapters = 3
    >>>
    >>> Host Adapter 0 CPQRAID.HAM HP Unified RAID
    >>> SCSI ID = 0 Lun = 2 HP LOGICAL VOLUME (2.58),
    >>>
    >>> Host Adapter 1 LSIMPTNW.HAM LSI_53C1030:0000
    >>> SCSI ID = 5 Lun = 0 QUANTUM DLT-V4 (0800), *
    >>>
    >>> Host Adapter 2 Vetitas VirtHBA Vetitas VirtMGR
    >>>
    >>> Hope you can help or is it just not supported ?
    >>>
    >>> Regards,
    >>> Bas

    >>
    >>First of all - is the drive on the HCL?
    >>
    >>http://support.veritas.com/docs/282348
    >>

    >Yep, it's a quantum DLT-V$ and functioning very well as a standalone drive
    >only the hardware compression is not working
    >
    >>You should also try this:
    >>
    >>http://support.veritas.com/docs/278402
    >>

    >
    >This looks more like it, I will try this option for the lsimptnw driver

    and
    >see if it helps, hmm, I can unload it and load it with this option, can't
    >I.
    >
    >THX in advance.
    >
    >

    hmm, unloading the driver caused a multiple abend althouh all backup software
    had been unloaded. The qtaggs=off option does not make backup exec see the
    library/loader

    it works perfect in sequential mode, but we bought the library expansion
    option to make use of the robot which does not work at the moment

    though netware detects all lun's perfectly

    I hope someone has the same setup and got the robot working.

    Regards,
    Bas


  5. Re: quantum superloader3

    Bas wrote:

    >
    > "Bas" wrote:
    > >
    > >"Chris" wrote:
    > > > Bas Smeelen wrote:
    > > >
    > >>>
    > >>> Hi,
    > >>>
    > >>> We have recently bought a quantum superloader3 but this does not

    > get >>> recognized bij backup exec as a robot.
    > >>>
    > >>> When I use scan all on the console netware sees the tape drive and
    > >>> autoloader on lun 0 and lun 1 the loader gets recognized as uhdl.
    > >>>
    > >>> When I use bediag /s /c none of the autoloader is seen.
    > >>> Also in backup exec no robot shows up.
    > >>>
    > >>> PSNW66-1:list storage adapters
    > >>> 0x00 [V024-A0] Legacy FLOPPY Controller [slot 0]
    > >>> 0x01 [V024-A0-D1:0] Legacy Floppy
    > >>> 0x02 [V100-A100] USB UHCI Controller [slot 0]
    > >>> 0x03 [V100-A101] USB UHCI Controller [slot 0]
    > >>> 0x04 [V100-A102] USB EHCI Controller [slot 0]
    > >>> 0x05 [V025-A1] Novell IDE/ATA/ATAPI/SATA Host Adapter Module

    > [slot >>> 0] 0x11 [V025-A1-D0:0] TEAC DV-28E-N f/w:C.6B
    > >>> 0x06 [V504-A2] HP Unified RAID Driver [slot 10017]
    > >>> 0x08 [V504-A2-D0:0] HP Smart Array 6i Slot 0 ID 0 LUN 0
    > >>> 0x07 [V358-A3] LSI_53C1030:00002 [slot 2]
    > >>> 0x13 [V358-A3-D5:1] QUANTUM UHDL 0043
    > >>> 0x12 [V358-A3-D5:0] QUANTUM DLT-V4 0800
    > >>>
    > >>> **** Start of BEDIAG results ****
    > >>>
    > >>> Fileserver Name: PSNW66-1
    > >>>
    > >>> CMD Host = BECDM.CDM
    > >>> Number of Host Adapters = 3
    > >>>
    > >>> Host Adapter 0 CPQRAID.HAM HP Unified RAID
    > >>> SCSI ID = 0 Lun = 2 HP LOGICAL VOLUME (2.58),
    > >>>
    > >>> Host Adapter 1 LSIMPTNW.HAM LSI_53C1030:0000
    > >>> SCSI ID = 5 Lun = 0 QUANTUM DLT-V4 (0800), *
    > >>>
    > >>> Host Adapter 2 Vetitas VirtHBA Vetitas VirtMGR
    > >>>
    > >>> Hope you can help or is it just not supported ?
    > >>>
    > >>> Regards,
    > >>> Bas
    > > >
    > > > First of all - is the drive on the HCL?
    > > >
    > > > http://support.veritas.com/docs/282348
    > > >

    > > Yep, it's a quantum DLT-V$ and functioning very well as a
    > > standalone drive only the hardware compression is not working
    > >
    > > > You should also try this:
    > > >
    > > > http://support.veritas.com/docs/278402
    > > >

    > >
    > > This looks more like it, I will try this option for the lsimptnw
    > > driver

    > and
    > > see if it helps, hmm, I can unload it and load it with this option,
    > > can't I.
    > >
    > > THX in advance.
    > >
    > >

    > hmm, unloading the driver caused a multiple abend althouh all backup
    > software had been unloaded. The qtaggs=off option does not make
    > backup exec see the library/loader
    >
    > it works perfect in sequential mode, but we bought the library
    > expansion option to make use of the robot which does not work at the
    > moment
    >
    > though netware detects all lun's perfectly
    >
    > I hope someone has the same setup and got the robot working.
    >
    > Regards,
    > Bas



    The qtags=off switch does not always work. Sometimes the LSI controller
    needs to be replaced by an Adaptec controller. Do you have CPQSCSA.NLM
    loaded? If so, try unloading this as it does cause problems.

    Also, what version/build of Backup Exec do you have? Check in
    install_volume\bkupexec\version.doc for details.

  6. Re: quantum superloader3


    "Chris" wrote:
    >Bas wrote:
    >
    >>
    >> "Bas" wrote:
    >> >
    >> >"Chris" wrote:
    >> > > Bas Smeelen wrote:
    >> > >
    >> >>>
    >> >>> Hi,
    >> >>>
    >> >>> We have recently bought a quantum superloader3 but this does not

    >> get >>> recognized bij backup exec as a robot.
    >> >>>
    >> >>> When I use scan all on the console netware sees the tape drive and
    >> >>> autoloader on lun 0 and lun 1 the loader gets recognized as uhdl.
    >> >>>
    >> >>> When I use bediag /s /c none of the autoloader is seen.
    >> >>> Also in backup exec no robot shows up.
    >> >>>
    >> >>> PSNW66-1:list storage adapters
    >> >>> 0x00 [V024-A0] Legacy FLOPPY Controller [slot 0]
    >> >>> 0x01 [V024-A0-D1:0] Legacy Floppy
    >> >>> 0x02 [V100-A100] USB UHCI Controller [slot 0]
    >> >>> 0x03 [V100-A101] USB UHCI Controller [slot 0]
    >> >>> 0x04 [V100-A102] USB EHCI Controller [slot 0]
    >> >>> 0x05 [V025-A1] Novell IDE/ATA/ATAPI/SATA Host Adapter Module

    >> [slot >>> 0] 0x11 [V025-A1-D0:0] TEAC DV-28E-N f/w:C.6B
    >> >>> 0x06 [V504-A2] HP Unified RAID Driver [slot 10017]
    >> >>> 0x08 [V504-A2-D0:0] HP Smart Array 6i Slot 0 ID 0 LUN 0
    >> >>> 0x07 [V358-A3] LSI_53C1030:00002 [slot 2]
    >> >>> 0x13 [V358-A3-D5:1] QUANTUM UHDL 0043
    >> >>> 0x12 [V358-A3-D5:0] QUANTUM DLT-V4 0800
    >> >>>
    >> >>> **** Start of BEDIAG results ****
    >> >>>
    >> >>> Fileserver Name: PSNW66-1
    >> >>>
    >> >>> CMD Host = BECDM.CDM
    >> >>> Number of Host Adapters = 3
    >> >>>
    >> >>> Host Adapter 0 CPQRAID.HAM HP Unified RAID
    >> >>> SCSI ID = 0 Lun = 2 HP LOGICAL VOLUME (2.58),
    >> >>>
    >> >>> Host Adapter 1 LSIMPTNW.HAM LSI_53C1030:0000
    >> >>> SCSI ID = 5 Lun = 0 QUANTUM DLT-V4 (0800), *
    >> >>>
    >> >>> Host Adapter 2 Vetitas VirtHBA Vetitas VirtMGR
    >> >>>
    >> >>> Hope you can help or is it just not supported ?
    >> >>>
    >> >>> Regards,
    >> >>> Bas
    >> > >
    >> > > First of all - is the drive on the HCL?
    >> > >
    >> > > http://support.veritas.com/docs/282348
    >> > >
    >> > Yep, it's a quantum DLT-V$ and functioning very well as a
    >> > standalone drive only the hardware compression is not working
    >> >
    >> > > You should also try this:
    >> > >
    >> > > http://support.veritas.com/docs/278402
    >> > >
    >> >
    >> > This looks more like it, I will try this option for the lsimptnw
    >> > driver

    >> and
    >> > see if it helps, hmm, I can unload it and load it with this option,
    >> > can't I.
    >> >
    >> > THX in advance.
    >> >
    >> >

    >> hmm, unloading the driver caused a multiple abend althouh all backup
    >> software had been unloaded. The qtaggs=off option does not make
    >> backup exec see the library/loader
    >>
    >> it works perfect in sequential mode, but we bought the library
    >> expansion option to make use of the robot which does not work at the
    >> moment
    >>
    >> though netware detects all lun's perfectly
    >>
    >> I hope someone has the same setup and got the robot working.
    >>
    >> Regards,
    >> Bas

    >
    >
    >The qtags=off switch does not always work. Sometimes the LSI controller
    >needs to be replaced by an Adaptec controller. Do you have CPQSCSA.NLM
    >loaded? If so, try unloading this as it does cause problems.
    >
    >Also, what version/build of Backup Exec do you have? Check in
    >install_volume\bkupexec\version.doc for details.


    cpqscsa.nlm is not loaded
    the version 9.2 build 1401.5

    Netware tells me this, scan all, it's quantum uhdl on lun 1:
    HBA ID LUN VENDOR PRODUCT REV SYNC WIDE QTAG IR P SCAN

    ----- -- --- --------- ----------------- ---- ---- ------ ---- ----- - ------

    2 5 0 QUANTUM DLT-V4 0800 F80 W16 No Y Refr

    2 5 1 QUANTUM UHDL 0043 F80 W16 No Y Refr

    2 7 LSI Logic LSI_53C1030 7 F160 W16 Refr


    The lsi logic controller is a add on card which is recommended by hp they
    did not have adaptec based cards for this at the reseller where we get hardware,
    I have read the document about DL360 servers and tape library and drives,
    maybe I should try a different card as last resort, but netare sees it all
    right and backup exec can use the drive alright.

    Maybe the library is not supported by the backup exec drivers and I have
    to wait for an update ?

    Also I noticed that hardware compression does not work on this drive, this
    was also the issue with backup exec for windows version 11 I think which
    got solved with an driver update, so I wonder how this is for Netware

    New server will all be Linux so I guess it all works then ?

    I still would like to see this as a robot in backup exec, but for now it
    just operates in sequential mode which means the device takes the next tape
    in the next slot as long as backup exec is accessing the device.

    Thanks for your time and help.


  7. Re: quantum superloader3

    Bas wrote:

    > Maybe the library is not supported by the backup exec drivers and I
    > have to wait for an update ?


    Is it on the HCL?

    Also, sequential mode is not supported:

    http://support.veritas.com/docs/252915


  8. Re: quantum superloader3


    "Chris" wrote:
    >Bas wrote:
    >
    >> Maybe the library is not supported by the backup exec drivers and I
    >> have to wait for an update ?

    >
    >Is it on the HCL?
    >
    >Also, sequential mode is not supported:
    >
    >http://support.veritas.com/docs/252915
    >

    Yes, it's on the HCL: Quantum DLT-V4
    It also works OK when set to sequential mode, the device then takes the tape
    out of the next slot until the backup is done, so it spans multiple tapes.

    It is just not getting detected as a robot, the library that is.

    The drive works fine but I would like to use the library expansion option
    function so that backup exec takes care of all the tape movements and not
    the loader itself.

    I don't understand why Netware sees the drive on lun 0 and the loader on
    lun 1and backup exec doesn't. When set to sequential mode Netware sees it
    as two drives one on lun 0 the other on lun 1



  9. Re: quantum superloader3


    Maybe I am wrong, Quantum DLT-V4 is on the HCL but under library with drive
    it's not. Superloader3 is on in but not for the DLT-V4! It's on it for DLT
    VS160.

    So am I in bad luck now or would it still get supported ?

    From the HCL:
    SuperLoader 3 QUANTUM^UHDL SCSI Multi LUN Quantum DLT VS160 QUANTUM^DLT^VS160
    SCSI DLT

    Only for LTO, SDLT and this one, no DLT-V4!
    Bummer.

    Though the inquiry string and addressing scheme are the same.

    I guess I just have to wait or let the device move the tapes around which
    doesn't always work right, but most of the time it does.


  10. Re: quantum superloader3

    Bas wrote:

    >
    > Maybe I am wrong, Quantum DLT-V4 is on the HCL but under library with
    > drive it's not. Superloader3 is on in but not for the DLT-V4! It's on
    > it for DLT VS160.
    >
    > So am I in bad luck now or would it still get supported ?
    >
    > From the HCL:
    > SuperLoader 3 QUANTUM^UHDL SCSI Multi LUN Quantum DLT VS160
    > QUANTUM^DLT^VS160 SCSI DLT
    >
    > Only for LTO, SDLT and this one, no DLT-V4!
    > Bummer.


    Looks like it isn't supported then... :-(

    > Though the inquiry string and addressing scheme are the same.
    >
    > I guess I just have to wait or let the device move the tapes around
    > which doesn't always work right, but most of the time it does.




    --


  11. Re: quantum superloader3


    "Chris" wrote:
    >Bas wrote:
    >
    >>
    >> Maybe I am wrong, Quantum DLT-V4 is on the HCL but under library with
    >> drive it's not. Superloader3 is on in but not for the DLT-V4! It's on
    >> it for DLT VS160.
    >>
    >> So am I in bad luck now or would it still get supported ?
    >>
    >> From the HCL:
    >> SuperLoader 3 QUANTUM^UHDL SCSI Multi LUN Quantum DLT VS160
    >> QUANTUM^DLT^VS160 SCSI DLT
    >>
    >> Only for LTO, SDLT and this one, no DLT-V4!
    >> Bummer.

    >
    >Looks like it isn't supported then... :-(
    >

    Do you have any idea if it gets supported ?
    Because if I could swap the drive for an LTO or DLT VS160 it would be supported.
    Quantum DLT-V4 is supported as a single drive and the library is the same
    hardware as in the LTO and others versions of this machine.

    Why is it not supported ?
    To new... maybe ?


  12. Re: quantum superloader3

    Bas wrote:

    >
    > "Chris" wrote:
    > > Bas wrote:
    > >
    > >>
    > >> Maybe I am wrong, Quantum DLT-V4 is on the HCL but under library

    > with >> drive it's not. Superloader3 is on in but not for the DLT-V4!
    > It's on >> it for DLT VS160.
    > >>
    > >> So am I in bad luck now or would it still get supported ?
    > >>
    > >> From the HCL:
    > >> SuperLoader 3 QUANTUM^UHDL SCSI Multi LUN Quantum DLT VS160
    > >> QUANTUM^DLT^VS160 SCSI DLT
    > >>
    > >> Only for LTO, SDLT and this one, no DLT-V4!
    > >> Bummer.

    > >
    > > Looks like it isn't supported then... :-(
    > >

    > Do you have any idea if it gets supported ?


    I have no idea I'm afraid.

    > Because if I could swap the drive for an LTO or DLT VS160 it would be
    > supported. Quantum DLT-V4 is supported as a single drive and the
    > library is the same hardware as in the LTO and others versions of
    > this machine.
    >
    > Why is it not supported ?
    > To new... maybe ?


    Maybe.

    --


+ Reply to Thread