Veritas NetBackup™ Commands Reference Guide
- Introduction
- Appendix A. NetBackup Commands
- acsd
- add_media_server_on_clients
- backupdbtrace
- backuptrace
- bmrc
- bmrconfig
- bmrepadm
- bmrprep
- bmrs
- bmrsrtadm
- bp
- bparchive
- bpbackup
- bpbackupdb
- bpcatarc
- bpcatlist
- bpcatres
- bpcatrm
- bpcd
- bpchangeprimary
- bpclient
- bpclimagelist
- bpclntcmd
- bpclusterutil
- bpcompatd
- bpconfig
- bpdbjobs
- bpdbm
- bpdgclone
- bpdown
- bpduplicate
- bperror
- bpexpdate
- bpfis
- bpflist
- bpgetconfig
- bpgetdebuglog
- bpimage
- bpimagelist
- bpimmedia
- bpimport
- bpinst
- bpkeyfile
- bpkeyutil
- bplabel
- bplist
- bpmedia
- bpmedialist
- bpminlicense
- bpnbat
- bpnbaz
- bppficorr
- bpplcatdrinfo
- bpplclients
- bppldelete
- bpplinclude
- bpplinfo
- bppllist
- bpplsched
- bpplschedrep
- bppolicynew
- bpps
- bprd
- bprecover
- bprestore
- bpretlevel
- bpschedule
- bpschedulerep
- bpsetconfig
- bpstsinfo
- bpstuadd
- bpstudel
- bpstulist
- bpsturep
- bptestbpcd
- bptestnetconn
- bptpcinfo
- bpup
- bpverify
- cat_convert
- cat_export
- cat_import
- configurePorts
- create_nbdb
- csconfig
- duplicatetrace
- importtrace
- jbpSA
- jnbSA
- ltid
- mklogdir
- nbauditreport
- nbcatsync
- NBCC
- NBCCR
- nbcertcmd
- nbcertupdater
- nbcomponentupdate
- nbcplogs
- nbdb_admin
- nbdb_backup
- nbdb_move
- nbdb_ping
- nbdb_restore
- nbdb_unload
- nbdbms_start_server
- nbdbms_start_stop
- nbdc
- nbdecommission
- nbdelete
- nbdeployutil
- nbdevconfig
- nbdevquery
- nbdiscover
- nbdna
- nbemm
- nbemmcmd
- nbexecute
- nbfindfile
- nbfirescan
- nbftadm
- nbftconfig
- nbgetconfig
- nbhba
- nbholdutil
- nbhypervtool
- nbjm
- nbkmsutil
- nboraadm
- nbpem
- nbpemreq
- nbperfchk
- nbplupgrade
- nbrb
- nbrbutil
- nbregopsc
- nbreplicate
- nbrestorevm
- nbseccmd
- nbsetconfig
- nbsnapimport
- nbsnapreplicate
- nbsqladm
- nbstl
- nbstlutil
- nbsu
- nbsvrgrp
- resilient_clients
- restoretrace
- stopltid
- tl4d
- tl8d
- tl8cd
- tldd
- tldcd
- tlhd
- tlhcd
- tlmd
- tpautoconf
- tpclean
- tpconfig
- tpext
- tpreq
- tpunmount
- verifytrace
- vltadm
- vltcontainers
- vlteject
- vltinject
- vltoffsitemedia
- vltopmenu
- vltrun
- vmadd
- vmchange
- vmcheckxxx
- vmd
- vmdelete
- vmoprcmd
- vmphyinv
- vmpool
- vmquery
- vmrule
- vmupdate
- vnetd
- vxlogcfg
- vxlogmgr
- vxlogview
- W2KOption
Name
tlmd — Tape library Multimedia (TLM) daemon-process
SYNOPSIS
[-v]
On UNIX systems, the directory path to this command is /usr/openv/volmgr/bin/
On Windows systems, the directory path to this command is <install_path>\Volmgr\bin\
DESCRIPTION
tlmd interfaces with Media Manager to automatically mount and unmount tapes in a tape library multimedia (TLM) robot. ltid is the Media Manager device daemon on UNIX systems and the NetBackup Device Manager service on Windows systems. ltid initiates tlmd if drives are defined to be in a tape library multimedia robot.
tlmd communicates with the ADIC Distributed AML Server (DAS) that controls the robot. This client and the server software product are designed to provide shared access to the family of ADIC Automated Media Libraries (AML). When the connection is established, tlmd puts the TLM robot in the UP state and can request inventories as well as media mounts and dismounts. If the connection cannot be established or DAS errors occur, tlmd changes the robot to the DOWN state but continues in operation. In this state, tlmd continues in operation and returns the robot to the UP state when the problem no longer exists.
The DAS server attribute defines the DAS server in the TLM robot entry in the Media and Device Management of the Administration Console. For each defined TLM robot, tlmd connects to this DAS server. From the perspective of DAS, tlmd connects as a DAS client. The host running tlmd establishes communication as the DAS client that the DAS_CLIENT entry in the Media Manager configuration file specifies: /usr/openv/volmgr/vm.conf. If no DAS_CLIENT entry exists, the DAS client name is the standard host name for the host that is running tlmd.
The drives are configured by using DAS drive names, which are based on the information that is obtained from the DAS server. You can use the robotic test utility, tlmtest (robtest if the robot is configured), to determine the drive names that are associated with the robot. You can also use ADIC's DASADMIN to verify library communications, status, and functionality.
UNIX systems: To stop or start tlmd independently of ltid, use /usr/openv/volmgr/bin/vmps or your server's ps command to identify the tldd process ID. Then enter the following commands:
kill tlmd_pid /usr/openv/volmgr/bin/tlmd [-v] &
The control daemon, tldcd, is on the host that has the robotic control. tldd on that host automatically starts it.
On UNIX systems, the Internet service port number for tlmd must be in /etc/services. If you use NIS (Network Information Service), place the entry in this host's /etc/services file in the master NIS server database for services.
On Windows systems, the Internet service port number for tlmd must be in %SystemRoot%\system32\drivers\etc\services.
The default service port number is 13716.
You must have administrator privileges to run this command.
OPTIONS
The following options operate only on UNIX systems.
- -v
Logs debug information by using syslogd. If you start ltid with -v, tlmd also starts with -v.
ERRORS
tlmd returns an error message if a copy of tlmd is in operation.
Media Manager logs TLM and network errors to syslogd (UNIX) or the Windows application event log. It also logs entries when the state changes between UP and DOWN.