Veritas NetBackup™ Commands Reference Guide

Last Published:
Product(s): NetBackup (8.1.1)
  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.  
      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 cldinstance
    86.  
      csconfig cldprovider
    87.  
      csconfig meter
    88.  
      csconfig throttle
    89.  
      duplicatetrace
    90.  
      importtrace
    91.  
      jbpSA
    92.  
      jnbSA
    93.  
      ltid
    94.  
      manageClientCerts
    95.  
      mklogdir
    96.  
      nbauditreport
    97.  
      nbcatsync
    98.  
      NBCC
    99.  
      NBCCR
    100.  
      nbcertcmd
    101.  
      nbcertupdater
    102.  
      nbcldutil
    103.  
      nbcomponentupdate
    104.  
      nbcplogs
    105.  
      nbdb_admin
    106.  
      nbdb_backup
    107.  
      nbdb_move
    108.  
      nbdb_ping
    109.  
      nbdb_restore
    110.  
      nbdb_unload
    111.  
      nbdbms_start_server
    112.  
      nbdbms_start_stop
    113.  
      nbdc
    114.  
      nbdecommission
    115.  
      nbdelete
    116.  
      nbdeployutil
    117.  
      nbdevconfig
    118.  
      nbdevquery
    119.  
      nbdiscover
    120.  
      nbdna
    121.  
      nbemm
    122.  
      nbemmcmd
    123.  
      nbexecute
    124.  
      nbfindfile
    125.  
      nbfirescan
    126.  
      nbftadm
    127.  
      nbftconfig
    128.  
      nbgetconfig
    129.  
      nbhba
    130.  
      nbholdutil
    131.  
      nbhostidentity
    132.  
      nbhostmgmt
    133.  
      nbhypervtool
    134.  
      nbjm
    135.  
      nbkmsutil
    136.  
      nboraadm
    137.  
      nborair
    138.  
      nbpem
    139.  
      nbpemreq
    140.  
      nbperfchk
    141.  
      nbplupgrade
    142.  
      nbrb
    143.  
      nbrbutil
    144.  
      nbregopsc
    145.  
      nbreplicate
    146.  
      nbrestorevm
    147.  
      nbseccmd
    148.  
      nbsetconfig
    149.  
      nbsnapimport
    150.  
      nbsnapreplicate
    151.  
      nbsqladm
    152.  
      nbstl
    153.  
      nbstlutil
    154.  
      nbstop
    155.  
      nbsu
    156.  
      nbsvrgrp
    157.  
      resilient_clients
    158.  
      restoretrace
    159.  
      stopltid
    160.  
      tl4d
    161.  
      tl8d
    162.  
      tl8cd
    163.  
      tldd
    164.  
      tldcd
    165.  
      tlhd
    166.  
      tlhcd
    167.  
      tlmd
    168.  
      tpautoconf
    169.  
      tpclean
    170.  
      tpconfig
    171.  
      tpext
    172.  
      tpreq
    173.  
      tpunmount
    174.  
      verifytrace
    175.  
      vltadm
    176.  
      vltcontainers
    177.  
      vlteject
    178.  
      vltinject
    179.  
      vltoffsitemedia
    180.  
      vltopmenu
    181.  
      vltrun
    182.  
      vmadd
    183.  
      vmchange
    184.  
      vmcheckxxx
    185.  
      vmd
    186.  
      vmdelete
    187.  
      vmoprcmd
    188.  
      vmphyinv
    189.  
      vmpool
    190.  
      vmquery
    191.  
      vmrule
    192.  
      vmupdate
    193.  
      vnetd
    194.  
      vwcp_manage
    195.  
      vxlogcfg
    196.  
      vxlogmgr
    197.  
      vxlogview
    198.  
      W2KOption

Name

tl8d — Tape library 8MM (TL8) daemon (process)

SYNOPSIS

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

tl8d interfaces with Media Manager to mount and unmount volumes in a tape library 8MM robot.

ltid is the Media Manager device daemon on UNIX systems and the NetBackup Device Manager service on Windows systems. t18d runs on each host with a drive connection and sends mount and unmount requests to the control daemon.

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

kill tl8d_pid

/usr/openv/volmgr/bin/tl8d [-v] &

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

On Windows systems, tl8d is started when the NetBackup Device Manager service is started. They are stopped when this service is stopped. The control process, tl8cd, is on the host that has the robotic control. tl8d starts it automatically on that host (see EXAMPLES). tl8cd 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.

If the vm.conf configuration option PREVENT_MEDIA_REMOVAL is enabled when tl8cd is active, tl8cd disables access to the volumes and the media access port. It disables access by issuing a command to the TL8 robot. If it is necessary to open the door of the cabinet, you must terminate tl8cd first. By default, access to the library is allowed.

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 the drive.

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

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

The default service port number is 13705.

The following items apply only to NetBackup Enterprise Server:

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

  • If drives are on different NetBackup hosts, enter the robotic information in the Media Manager configuration on all machines. The robot number must be the same on all machines.

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

ERRORS

UNIX systems:

tl8d logs error messages if a copy of the daemon is running.

Media Manager logs any tape library 8MM and robotic errors to syslogd. Log entries are also made when the state changes between UP and DOWN.

Windows systems:

Media Manager logs any tape library 8MM and robotic errors to the Windows application event log. Log entries are also made when the state changes between UP and DOWN.

EXAMPLES

Example 1 - In the following diagram, the drives and the robotics are connected to a single host. ltid initiates tl8d, which in turn initiates tl8cd.

Figure: Use of tl8d with single host connected to TL8 robot

Use of tl8d with single host connected to TL8 robot

Example 2 - The following example applies only to NetBackup Enterprise Server:

In the following diagram, each host is connected to one drive in the robot and the robotics are connected to host A. ltid on each host initiates tl8d. The tl8d on host A also initiates tl8cd, since that is where the robotic control is defined. Requests to mount tapes from host B go to tl8d on host B, which sends the robotic command to tl8cd on host A.

Figure: Use of tl8d with two hosts connected to TL8 robot

Use of tl8d with two hosts connected to TL8 robot

See syslogd (UNIX command)