Veritas NetBackup™ Commands Reference Guide

Last Published:
Product(s): NetBackup (8.2)
  1. Introduction
    1.  
      About NetBackup commands
    2.  
      Navigating multiple menu levels
    3.  
      NetBackup command conventions
    4.  
      NetBackup Media Manager command notes
    5.  
      IPV6 updates
  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.  
      bpplschedwin
    62.  
      bppolicynew
    63.  
      bpps
    64.  
      bprd
    65.  
      bprecover
    66.  
      bprestore
    67.  
      bpretlevel
    68.  
      bpschedule
    69.  
      bpschedulerep
    70.  
      bpsetconfig
    71.  
      bpstsinfo
    72.  
      bpstuadd
    73.  
      bpstudel
    74.  
      bpstulist
    75.  
      bpsturep
    76.  
      bptestbpcd
    77.  
      bptestnetconn
    78.  
      bptpcinfo
    79.  
      bpup
    80.  
      bpverify
    81.  
      cat_convert
    82.  
      cat_export
    83.  
      cat_import
    84.  
      configureCertsForPlugins
    85.  
      configureMQ
    86.  
      configurePorts
    87.  
      configureWebServerCerts
    88.  
      create_nbdb
    89.  
      csconfig cldinstance
    90.  
      csconfig cldprovider
    91.  
      csconfig meter
    92.  
      csconfig throttle
    93.  
      csconfig reinitialize
    94.  
      duplicatetrace
    95.  
      importtrace
    96.  
      jbpSA
    97.  
      jnbSA
    98.  
      ltid
    99.  
      manageClientCerts
    100.  
      mklogdir
    101.  
      nbauditreport
    102.  
      nbcatsync
    103.  
      NBCC
    104.  
      NBCCR
    105.  
      nbcertcmd
    106.  
      nbcertupdater
    107.  
      nbcldutil
    108.  
      nbcloudrestore
    109.  
      nbcomponentupdate
    110.  
      nbcplogs
    111.  
      nbdb_admin
    112.  
      nbdb_backup
    113.  
      nbdb_move
    114.  
      nbdb_ping
    115.  
      nbdb_restore
    116.  
      nbdb_unload
    117.  
      nbdbms_start_server
    118.  
      nbdbms_start_stop
    119.  
      nbdc
    120.  
      nbdecommission
    121.  
      nbdelete
    122.  
      nbdeployutil
    123.  
      nbdevconfig
    124.  
      nbdevquery
    125.  
      nbdiscover
    126.  
      nbdna
    127.  
      nbemm
    128.  
      nbemmcmd
    129.  
      nbfindfile
    130.  
      nbfirescan
    131.  
      nbftadm
    132.  
      nbftconfig
    133.  
      nbgetconfig
    134.  
      nbhba
    135.  
      nbholdutil
    136.  
      nbhostidentity
    137.  
      nbhostmgmt
    138.  
      nbhypervtool
    139.  
      nbimageshare
    140.  
      nbinstallcmd
    141.  
      nbjm
    142.  
      nbkmsutil
    143.  
      nboraadm
    144.  
      nborair
    145.  
      nbpem
    146.  
      nbpemreq
    147.  
      nbperfchk
    148.  
      nbplupgrade
    149.  
      nbrb
    150.  
      nbrbutil
    151.  
      nbregopsc
    152.  
      nbreplicate
    153.  
      nbrepo
    154.  
      nbrestorevm
    155.  
      nbseccmd
    156.  
      nbsetconfig
    157.  
      nbsnapimport
    158.  
      nbsnapreplicate
    159.  
      nbsqladm
    160.  
      nbstl
    161.  
      nbstlutil
    162.  
      nbstop
    163.  
      nbsu
    164.  
      nbsvrgrp
    165.  
      resilient_clients
    166.  
      restoretrace
    167.  
      stopltid
    168.  
      tl4d
    169.  
      tl8d
    170.  
      tl8cd
    171.  
      tldd
    172.  
      tldcd
    173.  
      tlhd
    174.  
      tlhcd
    175.  
      tlmd
    176.  
      tpautoconf
    177.  
      tpclean
    178.  
      tpconfig
    179.  
      tpext
    180.  
      tpreq
    181.  
      tpunmount
    182.  
      verifytrace
    183.  
      vltadm
    184.  
      vltcontainers
    185.  
      vlteject
    186.  
      vltinject
    187.  
      vltoffsitemedia
    188.  
      vltopmenu
    189.  
      vltrun
    190.  
      vmadd
    191.  
      vmchange
    192.  
      vmcheckxxx
    193.  
      vmd
    194.  
      vmdelete
    195.  
      vmoprcmd
    196.  
      vmphyinv
    197.  
      vmpool
    198.  
      vmquery
    199.  
      vmrule
    200.  
      vmupdate
    201.  
      vnetd
    202.  
      vssat
    203.  
      vwcp_manage
    204.  
      vxlogcfg
    205.  
      vxlogmgr
    206.  
      vxlogview
    207.  
      W2KOption

Name

tldcd — Tape library DLT (TLD) control daemon (process)

SYNOPSIS

tldcd [-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

tldd and tldcd interface with Media Manager to mount and unmount volumes in a tape library DLT (TLD) robot.

ltid is the Media Manager device daemon on UNIX systems and the NetBackup Device Manager service on Windows systems. tldd directly interfaces with ltid. tldd runs on each host with a drive connection and sends mount and unmount requests to the control daemon (tldcd). tldcd communicates directly with the robotics through a SCSI interface.

The following items apply only to NetBackup Enterprise Server:

  • TLD robotic control software permits drives in the same robot to be configured on different hosts. tldcd may be running on a different host than tldd, depending on where the interface connection resides (see EXAMPLES). When the connection is established (the path for robotics can be opened), tldd puts the TLD robot in the UP state. It then can mount and unmount volumes. If the robotics are inaccessible, tldd changes the robot to the DOWN state. In this state, tldd is still running and returns the robot to the UP state if tldcd is able to make a connection.

  • If drives are on different NetBackup 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, tldd and tldcd automatically start and stop when ltid is started and stopped. To stop or start tldd 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 tldd_pid
/usr/openv/volmgr/bin/tldd [-v] &

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

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

Before you access any volumes through the NetBackup Device Manager service (Windows systems), ltid, tl8d, and tl8cd, define the following information: the media ID and slot number for volumes in a robot in the EMM database.

If a cleaning volume is used, it must be defined in the volume configuration. See tpclean for information on setting the frequency to clean the drive automatically.

The drives are logically numbered 1 through n, where n is the number of drives in the robotic library. Use one or more of the following to determine the correct robot drive numbers:

  • The Device Configuration Wizard (if the robotic library and drives support serialization).

  • The robotic library vendor's documentation on how to index drives.

  • The robotic test utility, or experiment by mounting media and watch the operator display.

On UNIX systems, the Internet service port number for tldcd 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 tldcd must be in %SystemRoot%\system32\drivers\etc\services.

The default service port number is 13711.

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, tldd and tldcd are also started with -v.

-t

Terminates tldcd.

ERRORS

tldd and tldcd log an error message if another copy of the daemon is in operation.

Media Manager logs any tape library DLT and robotic errors to syslogd on UNIX systems, or to the Windows application event log on Windows systems. Log entries are also made when the state changes between UP and DOWN.

EXAMPLES

Example 1 - In the following diagram, the two drives and the robotics connect to Host A. ltid initiates tldd, which in turn initiates tldcd.

Figure: Use of tldcd with single host and TLD robot

Use of tldcd with single host and TLD robot

Example 2 - This example applies only to NetBackup Enterprise Server. In the following diagram, each host connects to one drive and the robotics connect to host A. ltid on each computer initiates tldd. The tldd on host A also initiates tldcd, since that is where the robotic control is defined. Requests to mount tapes from host B go to tldd on host B, which sends the robotic command to tldcd on host A.

Figure: Use of tldcd with two hosts connected to TLD robot

Use of tldcd with two hosts connected to TLD robot

SEE ALSO

See tldd.

See tpclean.

See tpconfig.

See ltid.

syslogd (UNIX command)