è To Check Robots with missing path
o Java GUI
n Under Media and Device Mgmt àUnder Devices àSelect Robots
o Command
n /usr/openv/volmgr/bin/tpconfig –d
80 Drive161 hcart3 TLD(6) DRIVE=7 /dev/nst27 UP
81 Drive162 hcart3 TLD(6) DRIVE=8 /dev/nst28 UP
82 Drive108 hcart3 TLD(6) DRIVE=9 /dev/nst29 UP
Currently defined robotics are:
TLD(1) robotic path = /dev/sg291
TLD(3) robotic path = /dev/sg76
TLD(4) robotic path = /dev/sg52
TLD(5) robotic path = /dev/sg98
TLD(6) robotic path = /dev/sg87
TLD(7) robotic path = /dev/sg74
EMM Server = usvhvoilms001
or
/usr/openv/volmgr/bin/tpconfig -l
èDelete the robot with missing path either java GUI or Command
o Java GUI (Recommended)
n Under Media and Device Mgmt àUnder Devices àSelect Robots àSelect the robot with missing path àRight Click and Select Delete
o Command
n /usr/openv/volmgr/bin/tpconfig –delete -robot <robot number>
èRestart Media Manager processes.
èIf received any error while deleting robot, please follow this steps
o Please check any resource holding this robot using this command
n /usr/openv/netbackup/bin/admincmd/nbrbutil –dump
n If you see any resource holding this robot please use this command to release it nbrbutil -resetMediaServer <media server name>
or
nbrbutil -releaseMDS
nbrbutil -releaseMedia
èCheck the robot at Operating System Level
o /usr/openv/volmgr/bin/scan
o /usr/openv/volmgr/bin/tpautoconf –r
o cat /proc/scsi/scsi
If found robot at OS level, please run Device Config Wizard on Master server and rescan the devices on master server and follow the on screen steps to add the robot.
èRestart Media Manager processes.
èTo Confirm Robot is added
o Java GUI
n Under Media and Device Mgmt àUnder Devices àSelect Robots
o Command
n /usr/openv/volmgr/bin/tpconfig –d or
/usr/openv/volmgr/bin/tpconfig -l
èTo Test the robot
o Use /usr/openv/volmgr/bin/robtest.
