cancel
Showing results for 
Search instead for 
Did you mean: 

Tape Drive Error

abhas_mangal
Level 3
Hi Guys,

I am facing below errors when tape is trying to mount in tape drives:
Jul  4 11:53:09 backup-1 ltid[15809]: [ID 187945 daemon.error] Request for media ID 0590L3 is being rejected because mount requests are disabled (reason = robotic daemon going to DOWN state)
Jul  4 11:53:09 backup-1 ltid[15809]: [ID 964571 daemon.error] Request for media ID J312L3 is being rejected because mount requests are disabled (reason = robotic daemon going to DOWN state)
Jul  4 11:55:32 backup-1 tldd[15843]: [ID 947739 daemon.notice] TLD(0) going to UP state
Jul  4 12:12:41 backup-1 ltid[15809]: [ID 265732 daemon.warning] Sending shutdown to tldcd daemon...
Jul  4 12:12:41 backup-1 tldcd[15859]: [ID 312429 daemon.notice] TERMINATION requested from backup-1
Jul  4 12:12:43 backup-1 vmd[15817]: [ID 631293 daemon.notice] terminating - successful (0)
Jul  4 12:12:43 backup-1 vmd[15817]: [ID 715111 daemon.error] volume daemon terminating because it received a signal (15)
Jul  4 12:12:43 backup-1 vmd[15817]: [ID 164182 daemon.error] terminating - daemon terminated (7)
Jul  4 12:13:21 backup-1 vmd[10663]: [ID 617826 daemon.notice] ready for connections
Jul  4 12:13:29 backup-1 tldd[10697]: [ID 947739 daemon.notice] TLD(0) going to UP state
Jul  4 12:13:30 backup-1 avrd[10711]: [ID 316786 daemon.notice] st.conf configuration for HP.ULTRIUM3-SCSI.000 (device 0), name [HP Ultrium LTO 3], vid [HP      Ultrium 3*], type 0x3b, block size 0, options 0x18619 (see st(7D) man page)
Jul  4 12:13:30 backup-1 avrd[10711]: [ID 558928 daemon.notice] st.conf configuration for HP.ULTRIUM3-SCSI.001 (device 1), name [HP Ultrium LTO 3], vid [HP      Ultrium 3*], type 0x3b, block size 0, options 0x18619 (see st(7D) man page)

Tape Drive is HCART3 and below are its details:
                                PENDING REQUESTS
                                     <NONE>
                                  DRIVE STATUS
Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId
  0 hcart3   TLD                -                     No       -         0
  1 hcart3   TLD                -                     No       -         0
                             ADDITIONAL DRIVE STATUS
Drv DriveName            Shared    Assigned        Comment
  0 HP.ULTRIUM3-SCSI.000  No       -
  1 HP.ULTRIUM3-SCSI.001  No       -


I have not faced such errors before. I think the error is with the tape drive as backup server is able to detect tape drives & also media before this error were able to mount in the tape drives.
Can someone please guide me how to resolve such errors?
1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

sgscan sees the robot fine:

dev/sg/c1t0l0: Changer: "QUANTUM PX500"

Please test with robtest - it does not use or need tldcd. It can even be used with NBU completely down.

Also, when adding VERBOSE to vm.conf, create the following log directories:
(Extract from http://seer.entsupport.symantec.com/docs/243778.htm - old, but most of it still valid)

  • /usr/openv/volmgr/debug/daemon - Debug information on the vmd, oprd, and rdevmi daemons (vmd handles authentication for shared storage option (SSO) drive registration by other media servers, in addition to global device database synchronization events, such as using the Device Auto-Discovery Wizard).
  • /usr/openv/volmgr/debug/ltid - Debug information for the ltid daemon.
  • /usr/openv/volmgr/debug/reqlib - Debug information of the tldd, tldcd, and related daemons.

If /var/adm/messages does not give info, reqlib log should help with troubleshooting.

Please also confirm your NBU patch level?

View solution in original post

5 REPLIES 5

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Which NBU version? O/S version?

Seems there's a problem with robot comms.
Please add VERBOSE entry to /usr/openv/volmgr/vm.conf and restart NBU.
All device type errors will be logged to syslog (if Solaris - /var/adm/messages).

abhas_mangal
Level 3

Netbackup version is 6.0 & OS version is Solaris 10.
 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Hopefully 6.0 with recent patching (such as MP7)?? 6.0 (unpatched) was not the best NBU version...

The errors you are seeing sounds like a robotic problem or connectivity/comms problem.
Does 'sgscan' pick up the robot?
Can you use robtest to do test mounts/dismounts? http://seer.entsupport.symantec.com/docs/274063.htm

See if there are any errors in /var/adm/messages. Also add VERBOSE entry to vm.conf and restart NBU to increase device level logging.

****EDIT****

Apologies - I can see that there are errors logged in messages..........
See if increasing logging level (VERBOSE in vm.conf) gives more info in messages.


abhas_mangal
Level 3
Currently, I am performing a restart of TL to see any error messages on its console.
I dont think that mount/unmount using robtest will work as error messages suggest that robot has tried to do the same.

Also, sgscan is able to scan the Tape Drives.
#WARNING: detected StorEdge Network Foundation connected devices not in
#         SG configuration file:
#
#    Device World Wide Port Name 200600a0b8299631
#    Device World Wide Port Name 200600a0b8299632
#
#    See /usr/openv/volmgr/NetBackup_DeviceConfig_Guide.txt chapter
#    "Special configuration for "Sun StorEdge Network Foundation" HBA/Driver"
#    for information on how to use sg.build and sg.install to
#    configure these devices
#
/dev/sg/c0t0l0: Disk (/dev/rdsk/c0t0d0): "FUJITSU MAY2073RCSUN72G"
/dev/sg/c0t1l0: Disk (/dev/rdsk/c0t1d0): "FUJITSU MAY2073RCSUN72G"
/dev/sg/c1t0l0: Changer: "QUANTUM PX500"
/dev/sg/c1t1l0: Tape (/dev/rmt/0): "HP      Ultrium 3-SCSI"
/dev/sg/c1t2l0: Tape (/dev/rmt/1): "HP      Ultrium 3-SCSI"#

Some warning message is displayed though at the beginning of the output. Can the message be a clue to this problem?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

sgscan sees the robot fine:

dev/sg/c1t0l0: Changer: "QUANTUM PX500"

Please test with robtest - it does not use or need tldcd. It can even be used with NBU completely down.

Also, when adding VERBOSE to vm.conf, create the following log directories:
(Extract from http://seer.entsupport.symantec.com/docs/243778.htm - old, but most of it still valid)

  • /usr/openv/volmgr/debug/daemon - Debug information on the vmd, oprd, and rdevmi daemons (vmd handles authentication for shared storage option (SSO) drive registration by other media servers, in addition to global device database synchronization events, such as using the Device Auto-Discovery Wizard).
  • /usr/openv/volmgr/debug/ltid - Debug information for the ltid daemon.
  • /usr/openv/volmgr/debug/reqlib - Debug information of the tldd, tldcd, and related daemons.

If /var/adm/messages does not give info, reqlib log should help with troubleshooting.

Please also confirm your NBU patch level?