Veritas NetBackup™ Commands Reference Guide
- Introduction
- Appendix A. NetBackup Commands
Name
ltid — start or stop the Media Manager device daemon
SYNOPSIS
/usr/openv/volmgr/bin/
[-v] [-logmounts [minutes]] [-noverify]
DESCRIPTION
This command operates only on UNIX systems.
The ltid command starts the Media Manager device daemon (ltid) and Automatic Volume Recognition daemon (avrd). These daemons manage Media Manager devices. With both daemons started, an operator can initiate the operator display, observe the drive status, and control the assignment of requests to standalone drives. ltid can be placed in a system initialization script.
The Media Manager volume daemon, vmd, also starts with the ltid command. ltid also starts the appropriate robotic daemons, if robotic devices were defined in Media Manager.
The stopltid command stops ltid, avrd, and the robotic daemons.
You must have administrator privileges to run this command.
OPTIONS
- -v
Logs debug information using syslogd. This option is most informative when robotic devices are in use. This option starts robotic daemons and vmd in verbose mode.
- -logmounts minutes
If this option is specified, ltid logs mount requests using syslogd. The mount requests are still posted to Media Manager displays. The mount requests are only logged after a delay of the specified number of minutes.
If -logmounts is specified, the default number of minutes is 3. If -logmounts 0 is specified, ltid logs the mount request through syslogd immediately. If minutes is not zero and the mount request is satisfied before the number of minutes are up, the request is not logged through syslogd.
- -noverify
If this option is specified, ltid does not verify drive names. Normally, ltid verifies that the no rewind on close drive name has the correct minor number bits that relate to the following: no rewind, variable, berkeley-style, and so on. This option is normally not required, but may be helpful if you use non-standard platform device files. If this option is specified, make sure that the device files are correct.
ERRORS
Error messages are logged by using syslogd.