Forum Discussion

robertoaxity's avatar
robertoaxity
Moderator
5 years ago

Drives are "Scan mode" in control and robot are not Enable

Hello,

I have a robot (TLD0) say no in "Enable tab", in activity monitor in Drive tab, the Drives ara in Scan mode, i put 2 media in this library that i need to restore, however, after 2 hours the job keep saying mount xxxx media.

I try:

- reset demons for the robot

- use wizard to add (i dont delete the robot), just overwriting

- reboot the library

[root@lprpmedia01 bin]# ./robtest
Configured robots with local control supporting test utilities:
TLD(0) robotic path = /dev/sg133

Robot Selection
---------------
1) TLD 0
2) none/quit
Enter choice: 1

Robot selected: TLD(0) robotic path = /dev/sg133

Invoking robotic test utility:
/usr/openv/volmgr/bin/tldtest -rn 0 -r /dev/sg133

Opening /dev/sg133
MODE_SENSE complete
Enter tld commands (? returns help information)

Can you help me.

Regards

 

8
Linux
  • Marianne's avatar
    Marianne
    5 years ago

    SCAN host is normal in a shared environment where one media server controls the drive assignment.
    Although the drives are not shared with any other media server(s), the drives were configured as SHARED.

    I would do the following:
    Delete ALL devices configured for lprpmedia01. If you do it from the master sever GUI, it will prompt you for a restart of Device Management services. Answer Yes.
    Else, run nbemmcmd -deletealldevices -machinename <media-server-name> -machinetype media

    Run the device config wizard, select lprpmedia01 (or lprpmedia01.derco.cl) and complete the wizard. 

    When done, you will need to Inventory the robot as all tapes are moved to standalone when you delete the robot.

    Next, check the Storage Unit config for this media server. Double-check hostname and attributes.

    When done, reset the Resource Broker for this media server:
    nbrbutil -resetMediaServer <media-server-name>

    Test a backup or restore for this media server.

  • quebek's avatar
    quebek
    Moderator
    5 years ago

    Hmm

    Did you run robot inventory - in order to tell NBU new tapes did appear in the library? To do so run this command:

    vmupdate -rt tld -rn 0 -empty_map 

    Or you can use equivallent from GUI - right click on media/robot inventory...

    Once done your restore should proceed further...

    • robertoaxity's avatar
      robertoaxity
      Moderator
      5 years ago

      Hello,

      Yes i run invetory and update inventory and then run fine.

      --------------------------------------------------------------------
      05-10-2020 11:47:20
      Robot: TLD(0) on lprpmedia01.derco.cl
      Operation: Inventory
      --------------------------------------------------------------------

      Robot Contents

      Slot Tape Barcode
      ==== ==== ============
      1 Yes DE0036L6
      2 Yes DER375L6
      3 Yes DE0067L6
      4 Yes DER227L6
      5 Yes DER342L6
      6 Yes DER152L6
      7 No
      8 Yes DE0053L6
      9 Yes DER052L6
      10 No
      11 Yes DER230L6
      12 Yes DER164L6
      13 Yes DER305L6
      14 No
      15 Yes DER527L6
      16 Yes DE0031L6
      17 No
      18 No
      19 Yes DE0028L6
      20 Yes DE0030L6
      21 Yes DER196L6
      22 No
      23 No
      24 No
      25 No
      26 No
      27 No
      28 Yes DER113L6
      29 Yes DE0063L6
      30 Yes DE00556
      31 Yes DER314L6
      32 Yes DER204L6
      33 Yes DE0027L6
      34 Yes DER438L6
      35 Yes DER017L6
      36 No
      37 Yes CLN069CU
      38 No
      39 No
      40 No
      41 No
      42 No
      43 No
      44 No
      45 No

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

      Regards

  • Marianne's avatar
    Marianne
    Level 6
    5 years ago

    robertoaxity 

    What was the purpose of running robtest?
    Did you perhaps check drive and slot status?

    Please remember to quit out of robtest before you do anything in NBU - robtest holds control of the robot and will prevent NBU from managing the robot.

    Please tell us more about the robot and drives on media server lprpmedia01.
    Is it in every day use for backups?
    Are the drives shared with other media servers?
    Is comms fine between the master and this media server?

    If you run 'vmoprcmd -d' on the media server, does the output correspond with Device Monitor?
    Have you checked Device Monitor (not Devices tab in Avtivity Monitor) for pending mount request?

    • robertoaxity's avatar
      robertoaxity
      Moderator
      5 years ago

      Marianne 

      What was the purpose of running robtest? Test for know the robot is ok

      Did you perhaps check drive and slot status? the web show the robot is ok, attached image

      Please remember to quit out of robtest before you do anything in NBU - robtest holds control of the robot and will prevent NBU from managing the robot., Oh ok, thanks for this 

      Please tell us more about the robot and drives on media server lprpmedia01.
      Is it in every day use for backups?, Yes

      Are the drives shared with other media servers? No
      Is comms fine between the master and this media server? Yes

      If you run 'vmoprcmd -d' on the media server, does the output correspond with Device Monitor?

      [root@lprpmedia01 bin]# ./vmoprcmd -d
      Could not connect to vmd on host lprpmedia01.derco.cl (70)

      But, in the GUI show are running.

      Have you checked Device Monitor (not Devices tab in Avtivity Monitor) for pending mount request?

      I dont see pending.

       

      • EthanH's avatar
        EthanH
        Level 4
        5 years ago

        [root@lprpmedia01 bin]# ./vmoprcmd -d
        Could not connect to vmd on host lprpmedia01.derco.cl (70)

        That's why robtest works but NBU is having issues. Run bpps -x to see what NBU processes are running on the media server.

        In your initial post, you said you rebooted the library, but didn't say anything about restarting NBU services. Run bp.kill_all on the media server, wait for everything to be terminated, then restart them with bp.start_all. Make sure that the vmd and ltid processes start properly, then check if the drive status has changed.

        If you're still experiencing issues, stop NBU services on the media (bp.kill_all or netbackup stop), run bpps -x to make sure everything was terminated, reboot the library, then restart NBU services on the media server.