Physically attach the library to
the Media server and follow the specific configuration instructions specified
by the manufacturer and the OS vendor. Verify that you can give the robot
instructions at the OS level. This can be done with xdevadm, the Java GUI,
or the NT GUI.
If using xdevadm,
select
Add
Robot from the Robot
dialog menu.
If using the Java or NT GUIs, start
Media
and Device Management
and
click on the Media Manager that you wish to add the robot to and select
New
| Robot from the Actions
dialog menu.
Select the appropriate robot type by
consulting the Release Notes document ~V Supported Peripherals (release_notes.pdf).
Specify a unique robot number that will not be used within the rest of
the organization, and specify the volume database host that will store
the client indexes (it is recommended that you always specify your master
server). If your robot is being controlled by another system, specify the
host that is controlling it. If your robot is locally controlled, specify
the specify the robot control file. Consult the Media Manager Device Configuration
Guide for additional details.
The JAVA and NT GUIs will then prompt
you to restart the media manager daemon, and do it for you automatically.
If you are using xdevadm, you must restart the media manager daemon (ltid)
when you are ready for NetBackup to see the robot. To do this, use the
command /usr/openv/volmgr/bin/stopltid
followed by /usr/openv/volmgr/bin/ltid
to restart it. Any backups that are in progress at that time may fail.