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
vmd — run EMM daemon
SYNOPSIS
[-v]
The directory path to this command is /usr/openv/volmgr/bin/
DESCRIPTION
This command operates only on UNIX systems.
ltid does not require volumes to be defined in the EMM database before it is used.
The following paragraph applies only to NetBackup Enterprise Server:
The automatic mount of volumes in robotic devices does not take place until the following actions occur: the volumes are defined and their slot information (for non-API robots) is entered in the EMM database.
A direct interface to the EMM database is provided to facilitate EMM database administrative activities easily. Graphical, menu-driven, and command-line Media Manager utilities are provided.
vmd is also used for remote Media Manager device management and for managing the volume pool, barcode rules, and device databases.
The Internet service port number for vmd must be in /etc/services. If you use NIS (Network Information Service), place the entry that is in this host's /etc/services file in the master NIS server database for services. The default service port number is 13701.
The following paragraphs apply only to NetBackup Enterprise Server.
OPTIONS
- -v
Logs detailed the debug information if you create the
debug/daemondirectory (see ERRORS). Specify this option only if problems occur or if requested by Veritas support.
ERRORS
vmd logs an error message using syslogd if there is a copy of vmd in operation.
vmd logs an error message using syslogd if the port that it binds to is in use. If this message appears, you may need to override the services file by using the mechanism that is described under DESCRIPTION.
To run vmd in debug mode do the following:
Before you start vmd, create the following directory:
/usr/openv/volmgr/debug/daemon
If vmd is running, stop, and restart it after creating the directory.
Start vmd in verbose mode as follows or put a VERBOSE entry in vm.conf.
/usr/openv/volmgr/bin/vmd -v
Check the log message in
/usr/openv/volmgr/debug/daemon.
If problems persist, you can obtain more debug information on the requestor by creating the following directory: /usr/openv/volmgr/debug/reqlib.
One log per day is created in each debug directory. These logs continue to build until the debug directory is moved or removed, unless you specify a DAYS_TO_KEEP_LOGS entry in vm.conf. Do not remove the debug directory while vmd is running. Only run vmd in debug mode when necessary.
FILES
/usr/openv/volmgr/debug/daemon/* /usr/openv/volmgr/debug/reqlib/*
EMM database