Arcserve r16.5 backup server unable to detect mhvtl 1.4

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Arcserve r16.5 backup server unable to detect mhvtl 1.4

Richa
We have installed mhvtl 1.4 on linux server that has rhel 6.2. we have also installed ARCserve Linux/Unix data mover server on the same linux server.
We checked the mhvtl services and they are running properly as shown below:

# lsscsi -g
[1:0:0:0]    cd/dvd  NECVMWar VMware IDE CDR10 1.00  /dev/sr0   /dev/sg0
[2:0:0:0]    disk    VMware   Virtual disk     1.0   /dev/sda   /dev/sg1
[3:0:0:0]    mediumx STK      L700             0104  /dev/sch0  /dev/sg10
[3:0:1:0]    tape    IBM      ULT3580-TD5      0104  /dev/st0   /dev/sg2
[3:0:2:0]    tape    IBM      ULT3580-TD5      0104  /dev/st1   /dev/sg3
[3:0:3:0]    tape    IBM      ULT3580-TD4      0104  /dev/st2   /dev/sg4
[3:0:4:0]    tape    IBM      ULT3580-TD4      0104  /dev/st3   /dev/sg5
[3:0:8:0]    mediumx STK      L80              0104  /dev/sch1  /dev/sg11
[3:0:9:0]    tape    STK      T10000B          0104  /dev/st4   /dev/sg6
[3:0:10:0]   tape    STK      T10000B          0104  /dev/st5   /dev/sg7
[3:0:11:0]   tape    STK      T10000B          0104  /dev/st6   /dev/sg8
[3:0:12:0]   tape    STK      T10000B          0104  /dev/st7   /dev/sg9


# /etc/init.d/mhvtl start
mhvtl already running...

We have installed ARCserve 16.5 on windows 2008 R2 master server and added the above linux/unix data mover server . But we are not able to view the VTL tapes through ARCserve master server(backup server).

Any help on this topic is appreciated.
Reply | Threaded
Open this post in threaded view
|

Re: Arcserve r16.5 backup server unable to detect mhvtl 1.4

sbcedservice
Microsoft iSCSI Initiator Service ?
Reply | Threaded
Open this post in threaded view
|

Re: Arcserve r16.5 backup server unable to detect mhvtl 1.4

Richa
How do we configure iSCSI target on linux machine?? Can you please guide us??

We also need to know how to configure Microsoft iSCSI Initiator Service sos as to detect the mhvtl on linux machine.
We are new to this domain hence any help is greatly appreciated.
Reply | Threaded
Open this post in threaded view
|

Re: Arcserve r16.5 backup server unable to detect mhvtl 1.4

sbcedservice
If you have successefully installed mhvtl, you can use the gui (iSCSI (tgt) - Quick start) to have your target configured on unix.

On windows, you have to add the unix mhvtl server ip address on iSCSI initiator properties-Discovery and then log on on every device you can find on Targets tab.

Then you can find new medium changers and new controller and tape device (maybe as "Other devices") on device manager.

You mast restart the CA Tape Engine
Reply | Threaded
Open this post in threaded view
|

Re: Arcserve r16.5 backup server unable to detect mhvtl 1.4

Richa
WE are not using mhvtl gui. we have just installed mhvtl and all services related to it are running.
When we try to dicover targets from windows machine by giving the mhvtl server ip it gives "Connection failed" error.

Kindly let us know how to configure mhvtl tape drives as iSCSI targets for the windows initiator to be able to detect it.
We would prefer doing it through linux command line rather than mhvtl gui.

Any help on this topic is appreciated.
Reply | Threaded
Open this post in threaded view
|

Re: Arcserve r16.5 backup server unable to detect mhvtl 1.4

Mark Harvey
Administrator
i'm on leave until this coming Monday.. I'll provide more feedback then.

Any chance of starting mhVTL & providing the output of 'lsscsi -g'



Sent from my iPad

On Jan 24, 2014, at 15:06, "Richa [via mhVTL - A Linux Virtual Tape Library]" <[hidden email]> wrote:

WE are not using mhvtl gui. we have just installed mhvtl and all services related to it are running.
When we try to dicover targets from windows machine by giving the mhvtl server ip it gives "Connection failed" error.

Kindly let us know how to configure mhvtl tape drives as iSCSI targets for the windows initiator to be able to detect it.
We would prefer doing it through linux command line rather than mhvtl gui.

Any help on this topic is appreciated.


To start a new topic under mhVTL - A Linux Virtual Tape Library, email [hidden email]
To unsubscribe from mhVTL - A Linux Virtual Tape Library, click here.
NAML
Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|

Re: Arcserve r16.5 backup server unable to detect mhvtl 1.4

Richa
We were able to resolve the iscsi initiator issue and now arcserve detects mhvtl tape drive as shown in screenshot


mhvtl tape drive

But now the problem is ARCserve displays "No media in drive" error for the configured tape. Hence backups to mhvtl are not possible.
 when taking backups we get the following error

 "Pleae mount a blank media or media not belonging to any pool media"


Can you please provide some solutioin on this?

We are using ARCserve 16.5.
Reply | Threaded
Open this post in threaded view
|

Re: Arcserve r16.5 backup server unable to detect mhvtl 1.4

sbcedservice
This post was updated on .
Something is wrong ....

With the device manager I think you must view:


something like "Medium Changers" (The tape library)

something like "SCSI Array device controller"

something like "SCSI Sequential tape device"

In your screenshot I can see only the tape ....
 
(I'm using win2003 and Arcserve 16.1)

By the way: on my first experiences with mhvtl I found that best config for my situation was IBM ULT3582 library and IBM ULT3580 TD5 devices; I remember some problems with STK medium .....
Reply | Threaded
Open this post in threaded view
|

Re: Arcserve r16.5 backup server unable to detect mhvtl 1.4

Richa
We are using Arcserve 16.5 with win 2008 R2 as backup server

we have configured the target as follows:

lsscsi -g
[1:0:0:0]    cd/dvd  NECVMWar VMware IDE CDR10 1.00  /dev/sr0   /dev/sg0
[2:0:0:0]    disk    VMware   Virtual disk     1.0   /dev/sda   /dev/sg1
[2:0:1:0]    disk    VMware   Virtual disk     1.0   /dev/sdb   /dev/sg2
[2:0:2:0]    disk    VMware   Virtual disk     1.0   /dev/sdc   /dev/sg3
[3:0:0:0]    mediumx STK      L700             0104  /dev/sch0  /dev/sg12
[3:0:1:0]    tape    IBM      ULT3580-TD5      0104  -         /dev/sg4
[3:0:2:0]    tape    IBM      ULT3580-TD5      0104  -         /dev/sg5
[3:0:3:0]    tape    IBM      ULT3580-TD4      0104  -         /dev/sg6
[3:0:4:0]    tape    IBM      ULT3580-TD4      0104  -         /dev/sg7
[3:0:8:0]    mediumx STK      L80              0104  /dev/sch1  /dev/sg13
[3:0:9:0]    tape    STK      T10000B          0104  /dev/st4   /dev/sg8
[3:0:10:0]   tape    STK      T10000B          0104  /dev/st5   /dev/sg9
[3:0:11:0]   tape    STK      T10000B          0104  /dev/st6   /dev/sg10
[3:0:12:0]   tape    STK      T10000B          0104  /dev/st7   /dev/sg11


tgtadm --lld iscsi --op show --mode target
Target 1: iqn.2008-09.in.co.persistent:vm-tsmca9.target1
    System information:
        Driver: iscsi
        State: ready
    I_T nexus information:
        I_T nexus: 1
            Initiator: iqn.1994-05.com.redhat:85fdd9772c99
            Connection: 0
                IP Address: 10.244.192.31
        I_T nexus: 2
            Initiator: iqn.1991-05.com.microsoft:tsmcawinms
            Connection: 1
                IP Address: 10.244.192.21
    LUN information:
        LUN: 0
            Type: controller
            SCSI ID: IET     00010000
            SCSI SN: beaf10
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: null
            Backing store path: None
            Backing store flags:
        LUN: 1
            Type: disk
            SCSI ID: IET     00010001
            SCSI SN: beaf11
            Size: 21475 MB, Block size: 512
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: rdwr
            Backing store path: /dev/sdb
            Backing store flags:
        LUN: 2
            Type: passthrough
            SCSI ID: IET     00010002
            SCSI SN: beaf12
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: sg
            Backing store path: /dev/sg4
            Backing store flags:
        LUN: 3
            Type: passthrough
            SCSI ID: IET     00010003
            SCSI SN: beaf13
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: sg
            Backing store path: /dev/sg8
            Backing store flags:
    Account information:
    ACL information:
        ALL

Hence it is able to detect the tape drives under device manager. Also it can be detected in arcserve but the slots are not visible and gives "No media in drive" message.

1. Let us know how to configure Medium changers so as to detect the tape drives correctly.
2. Is it because of the Windows OS that we are seeing the device list differently ??
3. Do we need to allocate space to LUNs created for example /dev/sg4 ?
Reply | Threaded
Open this post in threaded view
|

Re: Arcserve r16.5 backup server unable to detect mhvtl 1.4

sbcedservice
Maybe you can try this our working config (1 medium and 2 drives):

/etc/mhvtl/mhvtl.conf

# Home directory for config file(s)
MHVTL_CONFIG_PATH=/etc/mhvtl

# Default media capacity (500 M)
CAPACITY=409600

# Set default verbosity [0|1|2|3]
VERBOSE=1

# Set kernel module debuging [0|1]
VTL_DEBUG=0





/etc/mhvtl/device.conf

Library: 110 CHANNEL: 9 TARGET: 00 LUN: 00
 Vendor identification: IBM
 Product identification: ULT3582-TL
 Product revision level: 205B
 Unit serial number: 10000110
 NAA: 110:11:22:33:ab:9:00:00

Drive: 111 CHANNEL: 9 TARGET: 00 LUN: 01
 Library ID: 110 Slot: 01
 Vendor identification: IBM
 Product identification: ULT3580-TD5
 Product revision level: A3K6
 Unit serial number: 10000111
 NAA: 110:11:22:33:ab:9:00:01
 Compression: factor 1 enabled 0
 Compression type: lzo

Drive: 112 CHANNEL: 9 TARGET: 00 LUN: 2
 Library ID: 110 Slot: 2
 Vendor identification: IBM
 Product identification: ULT3580-TD5
 Product revision level: A3K6
 Unit serial number: 10000112
 NAA: 110:11:22:33:ab:9:00:2
 Compression: factor 1 enabled 0
 Compression type: lzo



/etc/mhvtl/library_contents.110


Drive1:
Drive2:

MAP 1:
MAP 2:

Picker 1:

Slot 1: TP2001L5
Slot 2: TP2002L5
Slot 3: TP2003L5
Slot 4: TP2004L5
Slot 5: TP2005L5
Slot 6: TP2006L5
Slot 7: TP2007L5
Slot 8: TP2008L5
Slot 9: TP2009L5
Slot 10: TP2010L5
Slot 11: TP2011L5
Slot 12: TP2012L5
Slot 13: TP2013L5
Slot 14: TP2014L5
Slot 15: TP2015L5
Slot 16: TP2016L5
Slot 17: TP2017L5
Slot 18: TP2018L5
Slot 19: TP2019L5
Slot 20: CLN020L5



/etc/tgt/targets.conf


default-driver iscsi

<target iqn.2001-04.com.example:sbvtl3:mhvtl:stgt:1>
        backing-store /dev/sg5
        backing-store /dev/sg3
        backing-store /dev/sg4
        bs-type sg
        device-type pt
</target>
Reply | Threaded
Open this post in threaded view
|

Re: Arcserve r16.5 backup server unable to detect mhvtl 1.4

Mark Harvey
Administrator
In reply to this post by Richa
You are only exporting two tape drives via the iSCSI target driver..

/dev/sg4 & /dev/sg8

export /dev/sg12 as well..

Note: the 2nd tape drive requires tape drivers available from oracle.com (if you want to use it from Windows)


Sent from my iPad

On Jan 28, 2014, at 1:39, "Richa [via mhVTL - A Linux Virtual Tape Library]" <[hidden email]> wrote:

We are using Arcserve 16.5 with win 2008 R2 as backup server

we have configured the target as follows:

lsscsi -g
[1:0:0:0]    cd/dvd  NECVMWar VMware IDE CDR10 1.00  /dev/sr0   /dev/sg0
[2:0:0:0]    disk    VMware   Virtual disk     1.0   /dev/sda   /dev/sg1
[2:0:1:0]    disk    VMware   Virtual disk     1.0   /dev/sdb   /dev/sg2
[2:0:2:0]    disk    VMware   Virtual disk     1.0   /dev/sdc   /dev/sg3
[3:0:0:0]    mediumx STK      L700             0104  /dev/sch0  /dev/sg12
[3:0:1:0]    tape    IBM      ULT3580-TD5      0104  -         /dev/sg4
[3:0:2:0]    tape    IBM      ULT3580-TD5      0104  -         /dev/sg5
[3:0:3:0]    tape    IBM      ULT3580-TD4      0104  -         /dev/sg6
[3:0:4:0]    tape    IBM      ULT3580-TD4      0104  -         /dev/sg7
[3:0:8:0]    mediumx STK      L80              0104  /dev/sch1  /dev/sg13
[3:0:9:0]    tape    STK      T10000B          0104  /dev/st4   /dev/sg8
[3:0:10:0]   tape    STK      T10000B          0104  /dev/st5   /dev/sg9
[3:0:11:0]   tape    STK      T10000B          0104  /dev/st6   /dev/sg10
[3:0:12:0]   tape    STK      T10000B          0104  /dev/st7   /dev/sg11


tgtadm --lld iscsi --op show --mode target
Target 1: iqn.2008-09.in.co.persistent:vm-tsmca9.target1
    System information:
        Driver: iscsi
        State: ready
    I_T nexus information:
        I_T nexus: 1
            Initiator: iqn.1994-05.com.redhat:85fdd9772c99
            Connection: 0
                IP Address: 10.244.192.31
        I_T nexus: 2
            Initiator: iqn.1991-05.com.microsoft:tsmcawinms
            Connection: 1
                IP Address: 10.244.192.21
    LUN information:
        LUN: 0
            Type: controller
            SCSI ID: IET     00010000
            SCSI SN: beaf10
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: null
            Backing store path: None
            Backing store flags:
        LUN: 1
            Type: disk
            SCSI ID: IET     00010001
            SCSI SN: beaf11
            Size: 21475 MB, Block size: 512
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: rdwr
            Backing store path: /dev/sdb
            Backing store flags:
        LUN: 2
            Type: passthrough
            SCSI ID: IET     00010002
            SCSI SN: beaf12
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: sg
            Backing store path: /dev/sg4
            Backing store flags:
        LUN: 3
            Type: passthrough
            SCSI ID: IET     00010003
            SCSI SN: beaf13
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: sg
            Backing store path: /dev/sg8
            Backing store flags:
    Account information:
    ACL information:
        ALL

Hence it is able to detect the tape drives under device manager. Also it can be detected in arcserve but the slots are not visible and gives "No media in drive" message.

1. Let us know how to configure Medium changers so as to detect the tape drives correctly.
2. Is it because of the Windows OS that we are seeing the device list differently ??
3. Do we need to allocate space to LUNs created for example /dev/sg4 ?



To start a new topic under mhVTL - A Linux Virtual Tape Library, email [hidden email]
To unsubscribe from mhVTL - A Linux Virtual Tape Library, click here.
NAML
Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|

Re: Arcserve r16.5 backup server unable to detect mhvtl 1.4

Richa
Thsi is the default configuration of mhvtl on our linux machine.

/etc/mhvtl/mhvtl.conf
# Home directory for config file(s)
MHVTL_CONFIG_PATH=/etc/mhvtl

# Default media capacity (500 M)
CAPACITY=500

# Set default verbosity [0|1|2|3]
VERBOSE=1

# Set kernel module debuging [0|1]
VTL_DEBUG=0

/etc/mhvtl/device.conf

Library: 10 CHANNEL: 00 TARGET: 00 LUN: 00
 Vendor identification: STK
 Product identification: L700
 Unit serial number: XYZZY_A
 NAA: 10:22:33:44:ab:00:00:00
 Home directory: /opt/mhvtl
 PERSIST: False
 Backoff: 400
# fifo: /var/tmp/mhvtl

Drive: 11 CHANNEL: 00 TARGET: 01 LUN: 00
 Library ID: 10 Slot: 01
 Vendor identification: IBM
 Product identification: ULT3580-TD5
 Unit serial number: XYZZY_A1
 NAA: 10:22:33:44:ab:00:01:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
 fifo: /var/tmp/mhvtl

Drive: 12 CHANNEL: 00 TARGET: 02 LUN: 00
 Library ID: 10 Slot: 02
 Vendor identification: IBM
 Product identification: ULT3580-TD5
 Unit serial number: XYZZY_A2
 NAA: 10:22:33:44:ab:00:02:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
 fifo: /var/tmp/mhvtl

Drive: 13 CHANNEL: 00 TARGET: 03 LUN: 00
 Library ID: 10 Slot: 03
 Vendor identification: IBM
 Product identification: ULT3580-TD4
 Unit serial number: XYZZY_A3
 NAA: 10:22:33:44:ab:00:03:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
# fifo: /var/tmp/mhvtl

Drive: 14 CHANNEL: 00 TARGET: 04 LUN: 00
 Library ID: 10 Slot: 04
 Vendor identification: IBM
 Product identification: ULT3580-TD4
 Unit serial number: XYZZY_A4
 NAA: 10:22:33:44:ab:00:04:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
# fifo: /var/tmp/mhvtl

Library: 30 CHANNEL: 00 TARGET: 08 LUN: 00
 Vendor identification: STK
 Product identification: L80
 Unit serial number: XYZZY_B
 NAA: 30:22:33:44:ab:00:08:00
 Home directory: /opt/mhvtl
 PERSIST: False
 Backoff: 400
# fifo: /var/tmp/mhvtl

Drive: 31 CHANNEL: 00 TARGET: 09 LUN: 00
 Library ID: 30 Slot: 01
 Vendor identification: STK
 Product identification: T10000B
 Unit serial number: XYZZY_B1
 NAA: 30:22:33:44:ab:00:09:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
# fifo: /var/tmp/mhvtl

Drive: 32 CHANNEL: 00 TARGET: 10 LUN: 00
 Library ID: 30 Slot: 02
 Vendor identification: STK
 Product identification: T10000B
 Unit serial number: XYZZY_B2
 NAA: 30:22:33:44:ab:00:10:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
# fifo: /var/tmp/mhvtl

Drive: 33 CHANNEL: 00 TARGET: 11 LUN: 00
 Library ID: 30 Slot: 03
 Vendor identification: STK
 Product identification: T10000B
 Unit serial number: XYZZY_B3
 NAA: 30:22:33:44:ab:00:11:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
# fifo: /var/tmp/mhvtl

Drive: 34 CHANNEL: 00 TARGET: 12 LUN: 00
 Library ID: 30 Slot: 04
 Vendor identification: STK
 Product identification: T10000B
 Unit serial number: XYZZY_B4
 NAA: 30:22:33:44:ab:00:12:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
# fifo: /var/tmp/mhvtl



/etc/mhvtl/library_contents.10

Drive 1:
Drive 2:
Drive 3:
Drive 4:

Picker 1:

MAP 1:
MAP 2:
MAP 3:
MAP 4:

# Slot 1 - ?, no gaps
# Slot N: [barcode]
# [barcode]
# a barcode is comprised of three fields: [Leading] [identifier] [Trailing]
# Leading "CLN" -- cleaning tape
# Leading "W" -- WORM tape
# Leading "NOBAR" -- will appear to have no barcode
# If the barcode is at least 8 character long, then the last two characters are Trailing
# Trailing "S3" - SDLT600
# Trailing "X4" - AIT-4
# Trailing "L1" - LTO 1, "L2" - LTO 2, "L3" - LTO 3, "L4" - LTO 4, "L5" - LTO 5
# Trailing "LT" - LTO 3 WORM, "LU" -  LTO 4 WORM, "LV" - LTO 5 WORM
# Trailing "L6" - LTO 6, "LW" - LTO 6 WORM
# Trailing "TA" - T10000+
# Trailing "TZ" - 9840A, "TY" - 9840B, "TX" - 9840C, "TW" - 9840D
# Trailing "TV" - 9940A, "TU" - 9940B
# Trailing "JA" - 3592+
# Trailing "JB" - 3592E05+
# Trailing "JW" - WORM 3592+
# Trailing "JX" - WORM 3592E05+
# Trailing "D7" - DLT7000 media (DLT IV)
#
Slot 1: E01001L4
Slot 2: E01002L4
Slot 3: E01003L4
Slot 4: E01004L4
Slot 5: E01005L4
Slot 6: E01006L4
Slot 7: E01007L4
Slot 8: E01008L4
Slot 9: E01009L4
Slot 10: E01010L4
Slot 11: E01011L4
Slot 12: E01012L4
Slot 13: E01013L4
Slot 14: E01014L4
Slot 15: E01015L4
Slot 16: E01016L4
Slot 17: E01017L4
Slot 18: E01018L4
Slot 19: E01019L4
Slot 20: E01020L4
Slot 21:
Slot 22: CLN101L4
Slot 23: CLN102L5
Slot 24:
Slot 25:
Slot 26:
Slot 27:
Slot 28:
Slot 29:
Slot 30: F01030L5
Slot 31: F01031L5
Slot 32: F01032L5
Slot 33: F01033L5
Slot 34: F01034L5
Slot 35: F01035L5
Slot 36: F01036L5
Slot 37: F01037L5
Slot 38: F01038L5
Slot 39: F01039L5

/etc/mhvtl/library_contents.30

Drive 1:
Drive 2:
Drive 3:
Drive 4:

Picker 1:

MAP 1:
MAP 2:
MAP 3:
MAP 4:

# Slot 1 - ?, no gaps
# Slot N: [barcode]
# [barcode]
# a barcode is comprised of three fields: [Leading] [identifier] [Trailing]
# Leading "CLN" -- cleaning tape
# Leading "W" -- WORM tape
# Leading "NOBAR" -- will appear to have no barcode
# If the barcode is at least 8 character long, then the last two characters are Trailing
# Trailing "S3" - SDLT600
# Trailing "X4" - AIT-4
# Trailing "L1" - LTO 1, "L2" - LTO 2, "L3" - LTO 3, "L4" - LTO 4, "L5" - LTO 5
# Trailing "LT" - LTO 3 WORM, "LU" -  LTO 4 WORM, "LV" - LTO 5 WORM
# Trailing "L6" - LTO 6, "LW" - LTO 6 WORM
# Trailing "TA" - T10000+
# Trailing "TZ" - 9840A, "TY" - 9840B, "TX" - 9840C, "TW" - 9840D
# Trailing "TV" - 9940A, "TU" - 9940B
# Trailing "JA" - 3592+
# Trailing "JB" - 3592E05+
# Trailing "JW" - WORM 3592+
# Trailing "JX" - WORM 3592E05+
# Trailing "D7" - DLT7000 media (DLT IV)
#
Slot 1: G03001TA
Slot 2: G03002TA
Slot 3: G03003TA
Slot 4: G03004TA
Slot 5: G03005TA
Slot 6: G03006TA
Slot 7: G03007TA
Slot 8: G03008TA
Slot 9: G03009TA
Slot 10: G03010TA
Slot 11: G03011TA
Slot 12: G03012TA
Slot 13: G03013TA
Slot 14: G03014TA
Slot 15: G03015TA
Slot 16: G03016TA
Slot 17: G03017TA
Slot 18: G03018TA
Slot 19: G03019TA
Slot 20: G03020TA
Slot 21: G03021TA
Slot 22: G03022TA
Slot 23: G03023TA
Slot 24: G03024TA
Slot 25: G03025TA
Slot 26: G03026TA
Slot 27: G03027TA
Slot 28: G03028TA
Slot 29: G03029TA
Slot 30: G03030TA
Slot 31: G03031TA
Slot 32: G03032TA
Slot 33: G03033TA
Slot 34: G03034TA
Slot 35: G03035TA
Slot 36: G03036TA
Slot 37: G03037TA
Slot 38: G03038TA
Slot 39: G03039TA
Slot 40: CLN303TA

/etc/tgt/targets.conf

<target iqn.2008-09.in.co.persistent:vm-tsmca9.target1>
backing-store /dev/sdb
backing-store /dev/sg4
backing-store /dev/sg6
backing-store /dev/sg12
bs-type sg
device-type pt
</target>

tgtadm --lld iscsi --op show --mode target
Target 1: iqn.2008-09.in.co.persistent:vm-tsmca9.target1
    System information:
        Driver: iscsi
        State: ready
    I_T nexus information:
        I_T nexus: 1
            Initiator: iqn.1994-05.com.redhat:85fdd9772c99
            Connection: 0
                IP Address: 10.244.192.31
        I_T nexus: 2
            Initiator: iqn.1991-05.com.microsoft:tsmcawinms
            Connection: 1
                IP Address: 10.244.192.21
    LUN information:
        LUN: 0
            Type: controller
            SCSI ID: IET     00010000
            SCSI SN: beaf10
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: null
            Backing store path: None
            Backing store flags:
        LUN: 1
            Type: disk
            SCSI ID: IET     00010001
            SCSI SN: beaf11
            Size: 21475 MB, Block size: 512
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: rdwr
            Backing store path: /dev/sdb
            Backing store flags:
        LUN: 2
            Type: passthrough
            SCSI ID: IET     00010002
            SCSI SN: beaf12
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: sg
            Backing store path: /dev/sg4
            Backing store flags:
        LUN: 3
            Type: passthrough
            SCSI ID: IET     00010003
            SCSI SN: beaf13
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: sg
            Backing store path: /dev/sg8
            Backing store flags:
        LUN: 4
            Type: passthrough
            SCSI ID: IET     00010004
            SCSI SN: beaf14
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: sg
            Backing store path: /dev/sg12
            Backing store flags:
    Account information:
    ACL information:
        ALL


But ARCserve doesnt detect library devices. When tried to add through device configuration we see the following.



Library devices are not visible. We are unable to se slots and 'no media in drive appears in arcserve.




No media in drive error



Reply | Threaded
Open this post in threaded view
|

Re: Arcserve r16.5 backup server unable to detect mhvtl 1.4

Richa
The problem is resolved now.

We had to configure IBM robot for IBM tape drives. The default was set to STK.
Thanks for suggesting your configuration. We tried that out and it worked!!

Now we have IBM ULT3582-TL with 2 tape drive ULT3580-TD5 and ULT3580-TD4
Similarly STK  L80 with  T10000B

Let us know if we need to configure similarly for STK.
Any help on this is highly appreciated.