Veritas NetBackup™ Commands Reference Guide

Last Published:
Product(s): NetBackup (8.0)
  1. Introduction
    1.  
      About NetBackup commands
    2.  
      Navigating multiple menu levels
    3.  
      NetBackup command conventions
    4.  
      NetBackup Media Manager command notes
  2. Appendix A. NetBackup Commands
    1.  
      acsd
    2.  
      add_media_server_on_clients
    3.  
      backupdbtrace
    4.  
      backuptrace
    5.  
      bmrc
    6.  
      bmrconfig
    7.  
      bmrepadm
    8.  
      bmrprep
    9.  
      bmrs
    10.  
      bmrsrtadm
    11.  
      bp
    12.  
      bparchive
    13.  
      bpbackup
    14.  
      bpbackupdb
    15.  
      bpcatarc
    16.  
      bpcatlist
    17.  
      bpcatres
    18.  
      bpcatrm
    19.  
      bpcd
    20.  
      bpchangeprimary
    21.  
      bpclient
    22.  
      bpclimagelist
    23.  
      bpclntcmd
    24.  
      bpclusterutil
    25.  
      bpcompatd
    26.  
      bpconfig
    27.  
      bpdbjobs
    28.  
      bpdbm
    29.  
      bpdgclone
    30.  
      bpdown
    31.  
      bpduplicate
    32.  
      bperror
    33.  
      bpexpdate
    34.  
      bpfis
    35.  
      bpflist
    36.  
      bpgetconfig
    37.  
      bpgetdebuglog
    38.  
      bpimage
    39.  
      bpimagelist
    40.  
      bpimmedia
    41.  
      bpimport
    42.  
      bpinst
    43.  
      bpkeyfile
    44.  
      bpkeyutil
    45.  
      bplabel
    46.  
      bplist
    47.  
      bpmedia
    48.  
      bpmedialist
    49.  
      bpminlicense
    50.  
      bpnbat
    51.  
      bpnbaz
    52.  
      bppficorr
    53.  
      bpplcatdrinfo
    54.  
      bpplclients
    55.  
      bppldelete
    56.  
      bpplinclude
    57.  
      bpplinfo
    58.  
      bppllist
    59.  
      bpplsched
    60.  
      bpplschedrep
    61.  
      bppolicynew
    62.  
      bpps
    63.  
      bprd
    64.  
      bprecover
    65.  
      bprestore
    66.  
      bpretlevel
    67.  
      bpschedule
    68.  
      bpschedulerep
    69.  
      bpsetconfig
    70.  
      bpstsinfo
    71.  
      bpstuadd
    72.  
      bpstudel
    73.  
      bpstulist
    74.  
      bpsturep
    75.  
      bptestbpcd
    76.  
      bptestnetconn
    77.  
      bptpcinfo
    78.  
      bpup
    79.  
      bpverify
    80.  
      cat_convert
    81.  
      cat_export
    82.  
      cat_import
    83.  
      configurePorts
    84.  
      create_nbdb
    85.  
      csconfig
    86.  
      duplicatetrace
    87.  
      importtrace
    88.  
      jbpSA
    89.  
      jnbSA
    90.  
      ltid
    91.  
      mklogdir
    92.  
      nbauditreport
    93.  
      nbcatsync
    94.  
      NBCC
    95.  
      NBCCR
    96.  
      nbcertcmd
    97.  
      nbcertupdater
    98.  
      nbcomponentupdate
    99.  
      nbcplogs
    100.  
      nbdb_admin
    101.  
      nbdb_backup
    102.  
      nbdb_move
    103.  
      nbdb_ping
    104.  
      nbdb_restore
    105.  
      nbdb_unload
    106.  
      nbdbms_start_server
    107.  
      nbdbms_start_stop
    108.  
      nbdc
    109.  
      nbdecommission
    110.  
      nbdelete
    111.  
      nbdeployutil
    112.  
      nbdevconfig
    113.  
      nbdevquery
    114.  
      nbdiscover
    115.  
      nbdna
    116.  
      nbemm
    117.  
      nbemmcmd
    118.  
      nbexecute
    119.  
      nbfindfile
    120.  
      nbfirescan
    121.  
      nbftadm
    122.  
      nbftconfig
    123.  
      nbgetconfig
    124.  
      nbhba
    125.  
      nbholdutil
    126.  
      nbhypervtool
    127.  
      nbjm
    128.  
      nbkmsutil
    129.  
      nboraadm
    130.  
      nbpem
    131.  
      nbpemreq
    132.  
      nbperfchk
    133.  
      nbplupgrade
    134.  
      nbrb
    135.  
      nbrbutil
    136.  
      nbregopsc
    137.  
      nbreplicate
    138.  
      nbrestorevm
    139.  
      nbseccmd
    140.  
      nbsetconfig
    141.  
      nbsnapimport
    142.  
      nbsnapreplicate
    143.  
      nbsqladm
    144.  
      nbstl
    145.  
      nbstlutil
    146.  
      nbsu
    147.  
      nbsvrgrp
    148.  
      resilient_clients
    149.  
      restoretrace
    150.  
      stopltid
    151.  
      tl4d
    152.  
      tl8d
    153.  
      tl8cd
    154.  
      tldd
    155.  
      tldcd
    156.  
      tlhd
    157.  
      tlhcd
    158.  
      tlmd
    159.  
      tpautoconf
    160.  
      tpclean
    161.  
      tpconfig
    162.  
      tpext
    163.  
      tpreq
    164.  
      tpunmount
    165.  
      verifytrace
    166.  
      vltadm
    167.  
      vltcontainers
    168.  
      vlteject
    169.  
      vltinject
    170.  
      vltoffsitemedia
    171.  
      vltopmenu
    172.  
      vltrun
    173.  
      vmadd
    174.  
      vmchange
    175.  
      vmcheckxxx
    176.  
      vmd
    177.  
      vmdelete
    178.  
      vmoprcmd
    179.  
      vmphyinv
    180.  
      vmpool
    181.  
      vmquery
    182.  
      vmrule
    183.  
      vmupdate
    184.  
      vnetd
    185.  
      vxlogcfg
    186.  
      vxlogmgr
    187.  
      vxlogview
    188.  
      W2KOption

Name

tlhcd — Tape library half-inch (TLH) control daemon (process on Windows systems)

SYNOPSIS

tlhcd [-v] [-t]

 

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

Note:

This command applies only to the NetBackup Enterprise Server.

tlhd and tlhcd interface with Media Manager to mount and unmount tape volumes in a tape library half-inch (TLH) robot.

ltid is the Media Manager device daemon on UNIX systems and the NetBackup Device Manager service on Windows systems. tlhd interfaces directly with ltid. tlhd runs on each host with a drive connection and sends mount and unmount requests to the control daemon-process, tlhcd.

tlhcd communicates with the IBM Automated tape library (ATL) library manager, which processes all requests and all control functions for the robotic library. TLH robotic control software permits drives in the same robot to be configured on different hosts. tlhcd can be running on a different host than tlhd, depending on where the IBM library control is configured (see EXAMPLES). When communication with the library is established, tlhd puts the TLH robot in the UP state and can request volume mounts and unmounts. If the library or the control daemon is inaccessible, tlhd changes the robot to the DOWN state. In this state, tlhd is still running and returns the robot to the UP state if tlhcd is able to make a connection.

Note:

If drives are on different hosts, enter the robotic information in the Media and Device Management of the Administration Console on all computers. The robot number must be the same on all computers.

On UNIX systems, tlhd and tlhcd automatically start and stop when ltid is started and stopped. To stop or start tlhd independently of ltid, use /usr/openv/volmgr/bin/vmps or your server's ps command to identify the tlhd process ID. Then enter the following commands:

kill tlhd_pid
/usr/openv/volmgr/bin/tlhd [-v] &

The control daemon, tlhcd, is on the host that has the robotic control. tlhcd on that host automatically starts it (see EXAMPLES).

On Windows systems, tlhd and tlhcd are started when the NetBackup Device Manager service is started. They are stopped when this service is stopped. The control process, tlhcd, is on the host that has the robotic control. tlhd starts it automatically on that host (see EXAMPLES). tlhcd stops when you stop the NetBackup Device Manager service.

Before you access any volumes through the NetBackup Device Manager service (Windows systems), ltid, tlhd, and tlhcd, define the following information: the media ID and slot number for volumes in a robot in the EMM database. Both the initial EMM database population and future updates can be accomplished by using Media Manager robotic inventory options.

If a cleaning volume is used, it must be defined in the volume configuration. See tpclean about how to set the frequency to clean the drive automatically.

The drives are configured by using IBM device names. The robotic test utility, tlhtest (robtest if the robot is configured), can be used to determine the device names that are associated with the robot. You can also use this utility along with IBM's mtlib command-line interface to verify library communications, status, and functionality.

Configure the drive cleaning operation for the tape library half-inch robotic control through an IBM library manager console. The cleaning operations are not available to applications that use the IBM library manager. For this reason, you cannot define the volumes to clean through Media Manager. In addition, you cannot use the Media Manager utilities or the tpclean command for cleaning operations on drives under TLH robotic control.

On UNIX systems, the Internet service port number for tlhcd must be in /etc/services. If you use NIS, place the entry in the /etc/services file in the master NIS server database for services.

On Windows systems, the Internet service port number for tldcd must be in %SystemRoot%\system32\drivers\etc\services.

The default service port number is 13717.

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, tlhd and tlhcd also start with -v.

-t

Terminates tlhcd.

ERRORS

tlhd and tlhcd log an error message if a copy of the daemon or process is in operation. Media Manager logs any tape library half-inch and robotic errors to syslogd (UNIX systems) or to the application event log (Windows). Log entries are also made when the state changes between UP and DOWN.

EXAMPLES

In the following examples the device hosts can be any supported Windows server or the following UNIX servers: AIX, HP-UX, Solaris (SPARC), and Linux.

Example 1 - In the following diagram, the drives are attached to and the robotics are controlled from a single host. ltid initiates tlhd, which in turn initiates tlhcd. lmcpd must be running on Host A. lmcpd is the IBM library manager control-point daemon on UNIX systems and the IBM Automated tape library service on Windows systems.

Figure: Use of tlhd with single host connected to TLH robot

Use of tlhd with single host connected to TLH robot

Example 2 - In the following diagram, each host is connected to at least one drive and the robotics are controlled from Host A. ltid on each computer initiates tlhd. The tlhd on Host A also initiates tlhcd, since that is where the robotic control is defined. Requests to mount tapes from Host B go to tlhd on Host B, which sends the robotic command to tlhcd on Host A.

Figure: Use of tlhd with two hosts connected to TLH robot

Use of tlhd with two hosts connected to TLH robot

SEE ALSO

See tlhd.

See tpclean.

See tpconfig.

See ltid.

syslogd (UNIX command)