While scanning the drives through GUI device confiure wizard it shows as unusable.

[Amit_Pendse]

I am facing drives issue on one of my media server which is linux2.6 OS, my netbackup version is 6.5
While scanning the drives through GUI device confiure wizard it shows as unusable.

[root@PG9010 ~]# vmoprcmd -d
The Media Manager device daemon (ltid) is not active on host PG9010
 

[root@PG9010 ~]# scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
------------------------------------------------------------
Device Name  : "-"
Passthru Name: "/dev/sg336"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULTRIUM-TD3     8711"
Vendor ID  : "IBM     "
Product ID : "ULTRIUM-TD3     "
Product Rev: "8711"
Serial Number: "3479530063"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULTRIUM-TD3     3479530063              "
Device Type    : SDT_TAPE
NetBackup Drive Type: 16
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x10000
------------------------------------------------------------
Device Name  : "-"
Passthru Name: "/dev/sg325"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULTRIUM-TD3     8711"
Vendor ID  : "IBM     "
Product ID : "ULTRIUM-TD3     "
Product Rev: "8711"
Serial Number: "3479530059"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULTRIUM-TD3     3479530059              "
Device Type    : SDT_TAPE
NetBackup Drive Type: 16
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x10000
------------------------------------------------------------
Device Name  : "-"
Passthru Name: "/dev/sg337"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULTRIUM-TD3     8711"
Vendor ID  : "IBM     "
Product ID : "ULTRIUM-TD3     "
Product Rev: "8711"
Serial Number: "3479530064"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULTRIUM-TD3     3479530064              "
Device Type    : SDT_TAPE
NetBackup Drive Type: 16
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x

[root@PG9010 ~]# scan -changer
************************************************************
*********************** SDT_CHANGER ************************
************************************************************

root@PG9010 ~]# tpconfig -l
Device Robot Drive       Robot                    Drive  Device  Second
Type     Num Index  Type DrNum Status  Comment    Name  Path  Device Path
robot      6    -    TLD    -       -  -          -  PG995
robot     18    -    TLD    -       -  -          -  PG995

]# cd /usr/openv/volmgr/debug/ltid/

ltid logs
rce_Factory '-ORBProtocolFactory IIOP_Factory'" -ORBSvcConfDirective "static PBXIOP_Evaluator_Factory '-orb Default_CLIENT_Orb'" -ORBSvcConfDirective "static Resource_Factory '-ORBConnectionCacheMax 1024 '" -ORBSvcConf /dev/null -ORBSvcConfDirective "static Server_Strategy_Factory '-ORBMaxRecvGIOPPayloadSize 268435456'"(Orb.cpp:739)
20:46:57.670 [30980] <4> InitLtidDeviceInfo: RobotCount = 2
20:46:57.670 [30980] <4> InitLtidDeviceInfo: DriveCount = 0
20:46:57.670 [30980] <6> logstderrmsg:
No Entries in the Drive Database

Need help on this.

[mph999]

FIrst thing , do the drives wrk from the OS - use the mt command to test (you may ned to instal this )

What is the history of the problem - for example was this previously working ?

Is this server (PG9010) the root control host ?

scan shows x3 tape drives and no robot - is ths correct.   I suspect that the robot is controlled by a separate server (P995 ??)

We need to know exactly what devices are atached to which servers ...

Martin

[Amit_Pendse]

Yes it was working previously,PG9010 is media server and robot control host is PG995

Media server is linux 2.6

[Marianne]

Have a look 'scan' output - all OS Device names show up as "-".

Seems OS has lost connectivity to devices.

Check /var/log/messages for errors.
Try to reboot server.

[mph999]

Well spotted Marianne - it should look like this ...

Device Name  : "/dev/sg/c0t5l1"

Passthru Name: "/dev/sg/c0t5l1"

... for example

I would reboot everything, (power cycle)  tape drives + server

M

[Amit_Pendse]

one more thing i want to know in debug log for ltil it shows me

cd /usr/openv/volmgr/debug/ltid/

ltid logs
rce_Factory '-ORBProtocolFactory IIOP_Factory'" -ORBSvcConfDirective "static PBXIOP_Evaluator_Factory '-orb Default_CLIENT_Orb'" -ORBSvcConfDirective "static Resource_Factory '-ORBConnectionCacheMax 1024 '" -ORBSvcConf /dev/null -ORBSvcConfDirective "static Server_Strategy_Factory '-ORBMaxRecvGIOPPayloadSize 268435456'"(Orb.cpp:739)
20:46:57.670 [30980] <4> InitLtidDeviceInfo: RobotCount = 2
20:46:57.670 [30980] <4> InitLtidDeviceInfo: DriveCount = 0
20:46:57.670 [30980] <6> logstderrmsg:
No Entries in the Drive Database

Marianne we have already rebooted the server 9010

[Marianne · Accepted solution]

Correct. ltid can only start after drives have been configured.

You need to ensure drives are seen and are usable at OS level before trying to add/use them in NBU.

Don't try anything in NBU until such time as 'scan' reports OS device names.

What is in /dev/rmt?

If entries are present, what does 'mt -f /dev/rmt/nstX' display?

Please follow steps in Device Config Guide to check/verify devices at OS level.

[Amit_Pendse]

Yes Marianne,

Now th drives are visiable at os, OS team has installed the ST drivers.

Thanks for all your support.

[Marianne]

Can we assume all is well now and Device Wizard has picked up and added the drives? If problem is solved, please select the post that has helped you most and Mark as Solution.