Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- Additional configuration
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About the Shared Storage Option
- About configuring the Shared Storage Option in NetBackup
- Viewing SSO summary reports
- About the vm.conf configuration file
- Holds Management
- Menu user interfaces on UNIX
- About the tpconfig device configuration utility
- About the NetBackup Disk Configuration Utility
- Reference topics
- Host name rules
- About reading backup images with nbtar or tar32.exe
- Factors that affect backup time
- NetBackup notify scripts
- Media and device management best practices
- About TapeAlert
- About tape drive cleaning
- How NetBackup reserves drives
- About SCSI persistent reserve
- About the SPC-2 SCSI reserve process
- About checking for data loss
- About checking for tape and driver configuration errors
- How NetBackup selects media
- About Tape I/O commands on UNIX
About the tpconfig device configuration utility
UNIX systems only.
The NetBackup tpconfig device configuration utility is a character-based, menu-driven interface to configure robots, drives, and logon credentials. It can be used at any terminal (or terminal emulation window) for which termcap or terminfo is defined.
The NetBackup command utilities are alternatives to the NetBackup Administration Console. The terminology, general concepts, and results are the same regardless of which method you use.
After you configure devices, you can use the NetBackup Administration Console to configure volumes.
The following list describes the attributes of device configuration and how to use the tpconfig utility to configure those attributes.
The tpconfig device configuration utility attributes are as follows:
Robot number
You assign a robot number when you add a robot to the configuration. tpconfig prompts you to enter a number or accept the next available robot number that appears. This number identifies the robot in displays and listings, and it follows the robotic type in parentheses, such as TL8(2).
If you configure robots on multiple systems, robot numbers must be unique. If you connect drives from a robot to multiple systems, specify the same robot number for the robot on all systems.
For most robots, you or the operating system creates this path in the /dev directory when you add a robot to the configuration. When the tpconfig utility prompts you, enter the path to the robotic control as found in the /dev directory. If the entries do not exist, more information is available.
See the NetBackup Device Configuration Guide, available at the following URL:
http://www.veritas.com/docs/DOC5332
The control path to a robot may be on another host. If so, enter the host name of the host instead of a path. When you define a robot that another host controls by another host, the robot number must be the same on both hosts.
Information about how to configure robotic control is available.
See the NetBackup Device Configuration Guide, available at the following URL:
You must specify a host name in the following cases:
When you add an ACS robot, enter the name of the host on which the ACS Library Software resides instead of a robotic control path.
When you add a TLM robot, enter the DAS or Scalar DLC server name instead of a robotic control path.
When you add one of the following robots that has robotic control on another host, you are prompted for the name of that host: TL8, TLD, or TLH robot.
No rewind on close device name
You specify an no rewind on close device name when you add a drive. Usually the letter n precedes or follows the device name. If the device name entries do not exist, you must create them.
See the NetBackup Device Configuration Guide, available at the following URL:
http://www.veritas.com/docs/DOC5332
In tpconfig displays and tpconfig output, the device names are shown under the heading DrivePath.
Drive status
Drive status indicates whether NetBackup considers a drive available. You specify the initial drive status when you add a drive to the configuration. You can change the status. To do so, use the Update option of the Drive Configuration menu in tpconfig (ensure that the device daemonltid is not active). If the device daemon ltid is active, use the Administration Console Device Monitor or the vmoprcmd command.