Forum Discussion

liamf91's avatar
liamf91
Level 3
8 years ago

Windows - Netback 7.0 Reboot issues

Currently have a server which is Windows Server 2003 running Netbackup 7.0.

I have a robot with two drives - Dell PowerVault 132T.

I have been having a problem readding the Robot to Netbackup, when i am running the scan it is only picking up the two drives.

I have had the robot on the netbackup before but i had to readd the drives which i had accidently removed the robot as well.

It is on a NDMP set up but i dont have the full info to manually add it in.

The medium changer can be seen in Device Manger. and the device can be accessed through its webGUI.

I know this is out of support officially but any help would be much appreciated?

 

7.1.x and Earlier
NetBackup 7.0
Windows 2003 End of Support
Windows Server 2003
  • quebek's avatar
    quebek
    Moderator
    8 years ago

    Hi

    What is being returened by

    tpautoconf -report_disc

    tpautoconf -r

    tpautoconf -t

    tpconfig -d

    vmglob -listall

    Is this library SCSI or FC connected. I would have stopped NBU and restarted it...

     

    • liamf91's avatar
      liamf91
      Level 3
      8 years ago

      FC i believe (assuming you mean fibre)

      I have restarted the device management multiple times. Do you mean to restart the whole services?

      tpautoconf -report_disc

      C:\VERITAS\Volmgr\bin>tpautoconf -report_disc
      ======================= New Device (Drive) =======================
       Inquiry = "IBM     ULTRIUM-TD3     6B20"
       Serial Number = 1210101036
       Drive Path = Tape0
      ======================= New Device (Drive) =======================
       Inquiry = "IBM     ULTRIUM-TD3     6B20"
       Serial Number = F09E8BD000
       Drive Path = Tape1

      tpautoconf -r

      Blank

      tpautoconf -t

      C:\VERITAS\Volmgr\bin>tpautoconf -t
      TPAC60 IBM     ULTRIUM-TD3     6B20 1210101036 3 0 0 0 Tape0 - -
      TPAC60 IBM     ULTRIUM-TD3     6B20 F09E8BD000 3 0 1 0 Tape1 - -

      tpconfig -d

      C:\VERITAS\Volmgr\bin>tpconfig -d
      Id  DriveName           Type   Residence
            SCSI coordinates/Path                                            Status
      ****************************************************************************

      Currently defined robotics are:

      EMM Server = ac2bckcov01

      vmglob -listall

      C:\VERITAS\Volmgr\bin>vmglob -listall
      =====================================================================

      • quebek's avatar
        quebek
        Moderator
        8 years ago

        Hi

        Rescan this server under device manager, if possible reboot it. Please restart this library - power cycle. Double check on which drive the robot LUN is being assigned to - is this drive zoned with you media server? Check with some HBA native utility if the robotic arm LUN is there

Related Content