Troubleshooting guide

Media Manager Functional Description
262 NetBackup Troubleshooting Guide - UNIX
Caution DO NOT under any circumstances attempt to modify the Media Manager
databases. These files are for internal program use only and changing them will
result in program failure and possible loss of data. It is also recommended that
you do not move them to another host.
Programs and Daemons
Table 10 describes the Media Manager programs and daemons. The explanations include
what starts and stops the program or daemon, and the log (if any) where it records its
activities. On UNIX, all of the components discussed in this table reside under
/usr/openv/volmgr/bin. On Windows NT/2000, they reside under
install_path\volmgr\bin.
Table 9. Media Manager Directories and Files
File or Directory Contents
bin Commands, scripts, programs, daemons, and files required for
Media Manager operation and administration. There are two
subdirectories under bin.
driver: Contains SCSI drivers used on various platforms to control
robotics.
format: Disk format information for optical platters on Solaris
platforms.
goodies: Contains Motif interfaces (xdevadm, xvmadm) on UNIX
platforms where Java is supported.
database Media Manager databases contain information about the drives,
robots, and media that are under Media Manager control.
The volume database that usually resides on the master server
contains volume information for multiple media servers.
debug Debug logs for the Media Manager volume daemon, vmd, and all
requesters of vmd. The administrator must create these directories
(daemon and reqlib) for debug logging to occur.
help Help files used by Media Manager programs. These files are in
ASCII format.
version Version and release date of the software.
vm.conf Media manager configuration options.
misc Lock files and temporary files required by various components of
Media Manager.