Troubleshooting guide

Appendix A, Functional Overview 255
Media Manager Functional Description
◆ Barcode Operations
◆ Media Manager Components
Note In this section, the term Media Manager refers to the media and device management
software that is part of NetBackup on either a UNIX or Windows NT/2000
NetBackup server.
Startup Process
Media Manager is part of NetBackup but, on UNIX, can also be run independently and
used by other applications, such as Storage Migrator. The easiest way to start Media
Manager is to initiate all the necessary processes during system startup on all servers that
have devices under control of Media Manager.
ltid automatically starts other daemons and programs as necessary. Figure 14 shows the
Media Manager daemons that should be running after initial startup. In the case of robotic
daemons, such as ts8d and rsmd, the associated robot must also be configured for the
daemon to run. See Table 10 for other ways to start and stop these daemons.
As shown on Figure 14, the LMF, TL8, TLH, and TLD, require two types of daemons:
robotic and robotic control.
◆ Each host with a drive attached must have a robotic daemon. These daemons provide
the interface between ltid and the robot or, if different drives within a robot can
attach to different hosts, the robotic daemon communicates with a robotic-control
daemon (see below).
◆ Robotic-control daemons centralize the control of robots when drives within a robot
can connect to different hosts. A robotic-control daemon receives mount and
unmount requests from the robotic daemon on the host to which the drive is attached
and then communicates these requests to the robot.
You must know the hosts involved in order to start all the daemons for a robot.