NBU Howto Site

Robot inventory failed: Unable to open robotic path (201)

20 April 2009 – 13:09

If you are facing with an error:

“Robot inventory failed: Unable to open robotic path (201).”

The causes can be: (Reference: http://seer.entsupport.symantec.com/docs/269409.htm)

1. Because the library door is left open
2. The is library is not connected, offline, shutdown or in the middle of a scan
3. The library is not in SCSI mode
4. Some other software has locked the SCSI path (Like robtest)
5. SCSI path has changed.

Solutions:
1. Check that the library door is closed.
2. Check that the library is running, online and connected.
3. Check that the library is in SCSI mode.
4. Run: /usr/openv/netbackup/bin/bpps (UNIX) or <install_path>veritasnetbackupbinbpps (windows)

Check that this command does not list any robtest/robtest.exe (UNIX/windows) process. If exists, kill the process

5. Open the Device Manager on windows and try to see if the “Medium Changer” is listed. It should exist for Netbackup to work.
6.  Run : /usr/openv/volmgr/bin/tpautoconf -r (UNIX) or <install_path>veritasvolmgrbintpautoconf -r (windows)

and try to see if robot is still communicating with the Operating System.
C:Program FilesVERITASVolmgrbin>tpautoconf -r
TPAC45 M4 DATA MagFile         3.05 RBD12A0007 2 0 0 0 Changer0 - -

7. If “tpautoconf -r” works, use the NetBackup Administration Console to re-browse for the robot on the Robot Control Host.

If you liked this site, please support NetBackupHowto

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>