Forum Discussion

A_M_Ash_'s avatar
A_M_Ash_
Level 6
13 years ago

Robotic library is down

hi ,

 i have this problem now that i start to backup a directory  using symantec netbackup 7.0.1 on unix and the backup didnot start and there is a messaage in activity monitor said that "  Robotic Library is down on server  '

and in the left pane  at Devices> Robots >  the path or status of robot is disabled

 

i need urgent help , but in details  steps thanks

7.1.x and Earlier
Backup and Recovery
NetBackup
  • mph999's avatar
    mph999
    13 years ago

    OK, you have x4 libraries on this server, scan sees all of them.

      TLD(1)     robotic path = /dev/rchgr/autoch4
      TLD(2)     robotic path = /dev/rchgr/autoch3
      TLD(3)     robotic path = /dev/rchgr/autoch5
      TLD(9)     robotic path = /dev/rchgr/autoch10

    You have not said which library is down ?

    In tpconfig -d I see there are drives configured on all x4 libraries.

    In scan tld(1) /2 /9 look fine, they all look like this ..

    Device Name  : "/dev/rchgr/autoch3"

    Passthru Name: "/dev/rchgr/autoch3"
    Volume Header: ""
    Port: -1; Bus: -1; Target: -1; LUN: -1
    Inquiry    : "EMC     Disk Library    2.00"
    Vendor ID  : "EMC     "
    Product ID : "Disk Library    "
    Product Rev: "2.00"
    Serial Number: "02QIW7PU00"
    WWN          : ""
    WWN Id Type  : 0
    Device Identifier: "EMC     Disk Library    02QIW7PU00  "
    Device Type    : SDT_CHANGER
    NetBackup Robot Type: 8
    Removable      : Yes
    Device Supports: SCSI-3
    Number of Drives : 20
    Number of Slots  : 600
    Number of Media Access Ports: 20
    Drive 1 Serial Number      : "02QIW7PU01"
    Drive 2 Serial Number      : "02QIW7PU02"
    Drive 3 Serial Number      : "02QIW7PU03"
    Drive 4 Serial Number      : "02QIW7PU04"
    Drive 5 Serial Number      : "02QIW7PU05"
    Drive 6 Serial Number      : "02QIW7PU06"
    Drive 7 Serial Number      : "02QIW7PU07"
    Drive 8 Serial Number      : "02QIW7PU08"
    Drive 9 Serial Number      : "02QIW7PU09"
    Drive 10 Serial Number      : "02QIW7PU0A"
    Drive 11 Serial Number      : "02QIW7PU0B"
    Drive 12 Serial Number      : "02QIW7PU0C"
    Drive 13 Serial Number      : "02QIW7PU0D"
    Drive 14 Serial Number      : "02QIW7PU0E"
    Drive 15 Serial Number      : "02QIW7PU0F"
    Drive 16 Serial Number      : "02QIW7PU0G"
    Drive 17 Serial Number      : "02QIW7PU0H"
    Drive 18 Serial Number      : "02QIW7PU0I"
    Drive 19 Serial Number      : "02QIW7PU0J"
    Drive 20 Serial Number      : "02QIW7PU0K"
    Flags : 0x0
    Reason: 0x0

    But if you look at  "/dev/rchgr/autoch5"   ( tld(3) ) can you see that iit does not show any drives listed.

     

    Device Name  : "/dev/rchgr/autoch5"

    Passthru Name: "/dev/rchgr/autoch5"
    Volume Header: ""
    Port: -1; Bus: -1; Target: -1; LUN: -1
    Inquiry    : "STK     SL3000          3.00"
    Vendor ID  : "STK     "
    Product ID : "SL3000          "
    Product Rev: "3.00"
    Serial Number: "571000200358"
    WWN          : ""
    WWN Id Type  : 0
    Device Identifier: ""
    Device Type    : SDT_CHANGER
    NetBackup Robot Type: 8
    Removable      : Yes
    Device Supports: SCSI-5
    Number of Drives : 18
    Number of Slots  : 400
    Number of Media Access Ports: 26
    Flags : 0x0
    Reason: 0x0

    I think tld(3) is the library that is down. This is a issue with the library, in scan a scsi_command is sent to the library to ask , what are your details, what drives do you have .  This library has responded, but has not listed any drives.  It does show there are 18 drives, but it is not listing them.  Therefore there may be  a fault with the library, or, the library configeration is not correct.  

     

    If I am correct, and this is the library that is down, then there is nothing that can be done in NBU, the issue is "why is the library not displaying the drives".

    To correct this, I recommend you contact the vendor you use for library support.

    Regards,

    Martin

     

     

     

     

     

  • A_M_Ash_'s avatar
    A_M_Ash_
    Level 6
    13 years ago
    output of '/usr/openv/netbackup/bin/bpps -x' NB Processes ------------ root 20846 1 0 Mar 21 ? 16:31 /usr/openv/netbackup/bin/nbstserv root 20760 1 0 Mar 21 ? 10:51 /usr/openv/netbackup/bin/nbaudit root 20841 20838 0 Mar 21 ? 0:17 /usr/openv/netbackup/bin/nbproxy dblib nbpem root 20888 1 0 Mar 21 ? 748:09 /usr/openv/netbackup/bin/nbsl root 11454 11452 0 May 14 ? 0:00 /usr/openv/netbackup/bin/bpjava-susvc root -1 -1 C /usr/openv/java/auth.conf 1 -1 11449 noUserCredentialsFile root 24148 20838 0 Mar 22 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup root 20834 1 0 Mar 21 ? 12:15 /usr/openv/netbackup/bin/bpdbm root 11518 11517 0 May 13 ? 0:01 /usr/openv/netbackup/bin/nbproxy dblib -mgrIORFile -PolicyManager-107.ior.mgr root 11831 11826 0 May 14 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib -mgrIORFile -StorageService-117.ior.mgr root 20908 1 0 Mar 21 ? 1:47 /usr/openv/netbackup/bin/bmrd root 14902 14899 0 May 13 ? 0:10 /usr/openv/netbackup/bin/nbproxy dblib -mgrIORFile -CatalogManager-107.ior.mgr root 20930 1 0 Mar 21 ? 0:21 /usr/openv/netbackup/bin/nbvault root 20894 1 0 Mar 21 ? 8:23 /usr/openv/netbackup/bin/nbars root 11808 11804 0 May 14 ? 0:02 /usr/openv/netbackup/bin/nbproxy dblib -mgrIORFile -PolicyManager-117.ior.mgr root 23395 20856 0 16:40:42 ? 0:01 /usr/openv/netbackup/bin/admincmd/bpstsinfo -DPSPROXY root 20801 20793 0 Mar 21 ? 0:04 /usr/openv/netbackup/bin/nbproxy dblib nbjm root 20763 1 0 Mar 21 ? 231:34 /usr/openv/netbackup/bin/nbemm root 11578 11452 0 11:06:25 ? 0:01 /usr/openv/netbackup/bin/bpjava-susvc root -1 -1 C /usr/openv/java/auth.conf 1 -1 11449 noUserCredentialsFile root 20698 1 0 Mar 21 ? 2:26 /usr/openv/netbackup/bin/vnetd -standalone root 11452 1 0 May 14 ? 0:00 /usr/openv/netbackup/bin/bpjava-susvc root -1 -1 C /usr/openv/java/auth.conf 1 -1 11449 noUserCredentialsFile root 11456 11452 0 May 14 ? 0:06 /usr/openv/netbackup/bin/bpjava-susvc root -1 -1 C /usr/openv/java/auth.conf 1 -1 11449 noUserCredentialsFile root 11501 20888 0 May 13 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib -mgrIORFile -StorageService-107.ior.mgr root 20838 1 0 Mar 21 ? 5:24 /usr/openv/netbackup/bin/nbpem root 20749 1 0 Mar 21 ? 773:24 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/global/databases.conf -hn 7 root 20835 20834 0 Mar 21 ? 28:44 /usr/openv/netbackup/bin/bpjobd root 20793 1 0 Mar 21 ? 65:15 /usr/openv/netbackup/bin/nbjm root 11388 11354 0 May 14 pts/3 8:15 /usr/openv/java/jre/bin/IA64W/java -Dvrts.NBJAVA_CONF=/usr/openv/java/nbj.conf -showversion -Dvrts.common.server.LCCTYPE="C" -D root 15061 20888 0 May 13 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib -mgrIORFile -ClientManager-107.ior.mgr root 20781 1 0 Mar 21 ? 10:50 /usr/openv/netbackup/bin/bprd root 20701 1 0 Mar 21 ? 2:52 /usr/openv/netbackup/bin/bpcd -standalone root 20856 1 0 Mar 21 ? 20:10 /usr/openv/netbackup/bin/nbrmms root 22946 20838 0 Mar 21 ? 0:02 /usr/openv/netbackup/bin/nbproxy dblib nbpem_email root 11826 20888 0 May 14 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib -mgrIORFile -StorageService-117.ior.mgr root 11804 20888 0 May 14 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib -mgrIORFile -PolicyManager-117.ior.mgr root 15063 15061 0 May 13 ? 0:16 /usr/openv/netbackup/bin/nbproxy dblib -mgrIORFile -ClientManager-107.ior.mgr root 20787 1 0 Mar 21 ? 2:14 /usr/openv/netbackup/bin/bpcompatd root 20753 1 0 Mar 21 ? 44:35 /usr/openv/netbackup/bin/nbevtmgr root 11502 11501 0 May 13 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib -mgrIORFile -StorageService-107.ior.mgr root 20949 1 0 Mar 21 ? 0:30 /usr/openv/netbackup/bin/nbsvcmon root 20767 1 0 Mar 21 ? 57:32 /usr/openv/netbackup/bin/nbrb root 11517 20888 0 May 13 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib -mgrIORFile -PolicyManager-107.ior.mgr root 14899 20888 0 May 13 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib -mgrIORFile -CatalogManager-107.ior.mgr MM Processes ------------ root 20779 1 0 Mar 21 ? 1:54 vmd root 10917 1 0 11:03:29 ? 0:00 /usr/openv/volmgr/bin/ltid root 11044 10917 0 11:03:42 ? 0:00 tldd root 11061 1 0 11:03:47 ? 0:00 tldcd root 11048 10917 0 11:03:44 ? 0:04 avrd Shared Symantec Processes ------------------------- root 3861 1 0 Mar 13 ? 6:14 /opt/VRTSpbx/bin/pbx_exchange
  • mph999's avatar
    mph999
    Level 6
    13 years ago

    No, my post asked you to run stopltid first, then ltid -v after a minute.

    The NetBackup commands we have asked you to run are in /usr/openv/volmgr/bin

     

    Other NBU commands (not needed at the moment) are mainly in /usr/openv/netbackup/bin and /usr/openv/netbackup/bin/admincmd

    You should set these paths in the unix profile so you do not need to keep looking for them.

     

     

  • Omar_Villa's avatar
    Omar_Villa
    Level 6
    13 years ago

    Which robot is the one you see down?

     

    Currently defined robotics are:
      TLD(1)     robotic path = /dev/rchgr/autoch4
      TLD(2)     robotic path = /dev/rchgr/autoch3
      TLD(3)     robotic path = /dev/rchgr/autoch5
      TLD(9)     robotic path = /dev/rchgr/autoch10

     

    Have you try to robtest to the library just to check communication is healthy enough? how the silo doing, normaly this is on the robot site and needs vendor attention.

  • mph999's avatar
    mph999
    Level 6
    13 years ago

    OK, you have x4 libraries on this server, scan sees all of them.

      TLD(1)     robotic path = /dev/rchgr/autoch4
      TLD(2)     robotic path = /dev/rchgr/autoch3
      TLD(3)     robotic path = /dev/rchgr/autoch5
      TLD(9)     robotic path = /dev/rchgr/autoch10

    You have not said which library is down ?

    In tpconfig -d I see there are drives configured on all x4 libraries.

    In scan tld(1) /2 /9 look fine, they all look like this ..

    Device Name  : "/dev/rchgr/autoch3"

    Passthru Name: "/dev/rchgr/autoch3"
    Volume Header: ""
    Port: -1; Bus: -1; Target: -1; LUN: -1
    Inquiry    : "EMC     Disk Library    2.00"
    Vendor ID  : "EMC     "
    Product ID : "Disk Library    "
    Product Rev: "2.00"
    Serial Number: "02QIW7PU00"
    WWN          : ""
    WWN Id Type  : 0
    Device Identifier: "EMC     Disk Library    02QIW7PU00  "
    Device Type    : SDT_CHANGER
    NetBackup Robot Type: 8
    Removable      : Yes
    Device Supports: SCSI-3
    Number of Drives : 20
    Number of Slots  : 600
    Number of Media Access Ports: 20
    Drive 1 Serial Number      : "02QIW7PU01"
    Drive 2 Serial Number      : "02QIW7PU02"
    Drive 3 Serial Number      : "02QIW7PU03"
    Drive 4 Serial Number      : "02QIW7PU04"
    Drive 5 Serial Number      : "02QIW7PU05"
    Drive 6 Serial Number      : "02QIW7PU06"
    Drive 7 Serial Number      : "02QIW7PU07"
    Drive 8 Serial Number      : "02QIW7PU08"
    Drive 9 Serial Number      : "02QIW7PU09"
    Drive 10 Serial Number      : "02QIW7PU0A"
    Drive 11 Serial Number      : "02QIW7PU0B"
    Drive 12 Serial Number      : "02QIW7PU0C"
    Drive 13 Serial Number      : "02QIW7PU0D"
    Drive 14 Serial Number      : "02QIW7PU0E"
    Drive 15 Serial Number      : "02QIW7PU0F"
    Drive 16 Serial Number      : "02QIW7PU0G"
    Drive 17 Serial Number      : "02QIW7PU0H"
    Drive 18 Serial Number      : "02QIW7PU0I"
    Drive 19 Serial Number      : "02QIW7PU0J"
    Drive 20 Serial Number      : "02QIW7PU0K"
    Flags : 0x0
    Reason: 0x0

    But if you look at  "/dev/rchgr/autoch5"   ( tld(3) ) can you see that iit does not show any drives listed.

     

    Device Name  : "/dev/rchgr/autoch5"

    Passthru Name: "/dev/rchgr/autoch5"
    Volume Header: ""
    Port: -1; Bus: -1; Target: -1; LUN: -1
    Inquiry    : "STK     SL3000          3.00"
    Vendor ID  : "STK     "
    Product ID : "SL3000          "
    Product Rev: "3.00"
    Serial Number: "571000200358"
    WWN          : ""
    WWN Id Type  : 0
    Device Identifier: ""
    Device Type    : SDT_CHANGER
    NetBackup Robot Type: 8
    Removable      : Yes
    Device Supports: SCSI-5
    Number of Drives : 18
    Number of Slots  : 400
    Number of Media Access Ports: 26
    Flags : 0x0
    Reason: 0x0

    I think tld(3) is the library that is down. This is a issue with the library, in scan a scsi_command is sent to the library to ask , what are your details, what drives do you have .  This library has responded, but has not listed any drives.  It does show there are 18 drives, but it is not listing them.  Therefore there may be  a fault with the library, or, the library configeration is not correct.  

     

    If I am correct, and this is the library that is down, then there is nothing that can be done in NBU, the issue is "why is the library not displaying the drives".

    To correct this, I recommend you contact the vendor you use for library support.

    Regards,

    Martin

     

     

     

     

     

  • Andy_Welburn's avatar
    Andy_Welburn
    Level 6
    13 years ago

    I think tld(3) is the library that is down. This is a issue with the library, in scan a scsi_command is sent to the library to ask , what are your details, what drives do you have .  This library has responded, but has not listed any drives.  It does show there are 18 drives, but it is not listing them.  Therefore there may be  a fault with the library, or, the library configeration is not correct.  

     

    If I am correct, and this is the library that is down, then there is nothing that can be done in NBU, the issue is "why is the library not displaying the drives".

    To correct this, I recommend you contact the vendor you use for library support.

    https://www-secure.symantec.com/connect/forums/robotic-library-down#comment-7138851

  • Marianne's avatar
    Marianne
    Level 6
    13 years ago

    We need YOU to help us in order to help you...

    Martin has asked you to start ltid with -v option.
    This would start Media Manager processes in VERBOSE mode.

    It seems this was NOT done as none of the media manager processes are running in verbose mode (-v):

    root 20779 1 0 Mar 21 ? 1:54 vmd
    root 10917 1 0 11:03:29 ? 0:00 /usr/openv/volmgr/bin/ltid
    root 11044 10917 0 11:03:42 ? 0:00 tldd
    root 11061 1 0 11:03:47 ? 0:00 tldcd
    root 11048 10917 0 11:03:44 ? 0:04 avrd

     

    If processes are running in verbose mode, Media Manager activities and errors will be logged in the OS syslog: var/adm/syslog/syslog.log.

    Please see if any errors can be seen in syslog.log, even though processes are not running in verbose mode.

    Another way to ensure that MM is running in verbose mode, add
    VERBOSE
    to /usr/openv/volmgr/vm.conf and restart NBU.

    If you want assistance with reading syslog, rename the file to syslog.txt and post as attachment.

     

  • mph999's avatar
    mph999
    Level 6
    13 years ago

     

    Yes, please read my post.

     

    TLD(3) is the library I think was having the problem - you confirmed this.

    If you look at the scan output, you will see this library is not listing any drives.  This is incorrect, and is a problem with either the configeration, or a fault, on that library.

    It is all explained in my other post.

     

    It might be work power cycling the library, that can sometimes fix issues like this.

    Martin