Physically attach the drive to the
Media server and follow the specific configuration instructions specified
by the manufacturer and the OS vendor. Verify that you can give the drive
instructions at the OS level. Then you can use xdevadm, or the JAVA or
NT GUIs.
If using xdevadm,
select Add Drive
from the Drives
dialog menu.
If using the Java or NT GUIs, start
Media and Device Management and click on the Media Manager to which you~Rre
adding the drive. Select New | Drive from the Actions
dialog
menu.
Select the appropriate drive type and
give it a drive index number that will be unique for the media server the
drive is connected to as well as a drive name which should be unique for
the organization. If on Unix, specify the no-rewind device file for the
device using the Berkley style close and compression (if available). If
using Solaris, verify that the type of drive you are using is in the st.conf
file. Consult the Media Manager Device Configuration Guide for details.
If the drive and OS do not have native tape alert cleaning features (generally
Exabyte 8900 Mammoths, Quantum and Tandberg DLT2/4/7000s, Sony AIT SDX-300Cs,
STK ½ inch cartridge, and STK 9840s) select a frequency based cleaning
routine (in hours). Set the robot type and robot number that is feeding
the drive media.
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.