|
|
Windows systems: <volmgr_dirpath>tpconfig -add -drive -type drvtype -port port -bus bus -target target -lun lun [-asciiname asciidrivename] [-index drvindex]] [-shared [yes|no]] [-cleanfreq hours] [-comment comment] [-drstatus [UP | DOWN | DISABLED]] [-scsi_protection [SPR | SR | NONE]] [-robot robnum -robtype robtype] [-noverify] [-robdrnum robdrvnum | -VendorDrvName vendor_drive_name] [-ACS acsnum -LSM lsmnum -PANEL panelnum -DRIVE drivenum] [preview]
Windows systems: <volmgr_dir_path>tpconfig -update -drive drvindex [-type drvtype] [-port port -bus bus -target target -lun lun ] [-nh ndmp_hostname -path drivepath] [-noverify] [-newasciiname asciidrivename]] [-shared [yes|no]] [-cleanfreq hours] [-comment comment] [-drstatus [UP|DOWN|DISABLED]] [-robot robnum -robtype robtype] [-robdrnum robdrvnum | -VendorDrvName vendor_drive_name] [-ACS acsnum -LSM lsmnum -PANEL panelnum -DRIVE drivenum]
<volmgr_dir_path>tpconfig -add -disk_array array_hostname -disk_user_id user_ID -arraytype_name "name:displayname" -requiredport IP_port_number [-password password [-key encryption_key]]
<volmgr_dir_path>tpconfig -update -disk_array array_hostname -disk_user_id user_ID -requiredport IP_port_number [-arraytype_name "name:displayname"] [-password password [-key encryption_key]]
<volmgr_dir_path>tpconfig -delete -disk_array array_hostname -disk_user_id user_ID [-arraytype_name "name:displayname"]
Windows systems: <volmgr_dir_path>tpconfig -add -robot robnum -robtype robtype -port port -bus bus -target target -lun lun
Windows systems: <volmgr_dir_path>tpconfig -add -robot robnum -robtype robtype [-nh ndmp_hostname] -robpath changername [-bus bus -target target -lun lun]
Windows systems: <volmgr_dir_path>tpconfig -update -robot robnum [-robtype robtype] [-port port -bus bus -target target -lun lun | -cntlhost cntlhost | -tlh_library_nametlh_library_name]
<volmgr_dir_path>tpconfig -update -robot robnum [-robtype robtype] [-robpath devfile] [-nh ndmp_hostname] [-bus bus] [-target target] [-lun lun]
<volmgr_dir_path>tpconfig -add -drpath -path drivepath [-nh ndmp_hostname] [-asciiname asciidrivename] [-drstatus [UP|DOWN|DISABLED]] [-noverify]
Windows systems: <volmgr_dir_path>tpconfig -update -drpath -old_port port -old_bus bus -old_target target -old_lun lun -port port -bus bus -target target -lun lun -asciiname asciidrvname [-drstatus [UP|DOWN|DISABLED]] [-noverify]
Windows systems: <volmgr_dir_path>tpconfig -delete -drpath [-port port -bus bus -target target -lun lun | -path drivepath [-nh ndmp_hostname]] -asciiname asciidrvname
<volmgr_dir_path>tpconfig -add -nh ndmp_hostname -user_id | -filer_user_id user ID [-password password [-key encryption_key]] -snap_vault_filer
<volmgr_dir_path>tpconfig -update -nh ndmp_hostname -user_id | -filer_user_id user ID [[-password password [-key encryption_key]]
<volmgr_dir_path>tpconfig -update -default_user_id user ID [-password password [-key encryption_key]]
<volmgr_dir_path>tpconfig -add | -update -disk_array disk_array_host_name -disk_user_id user_ID -arraytype disk_array_type -requiredport IP_port_number [-password password [-key encryption_key]]
tpconfig -delete -disk_array disk_array_host_name -disk_user_id user_ID [-arraytype disk_array_type]
<volmgr_dir_path>tpconfig -add | -update -virtual_machine virtual_machine_name -vm_user_id user_id -vm_type virtual_machine_type -requiredport IP_port_number [-password password [-key encryption_key]]
<volmgr_dir_path>tpconfig -delete -virtual_machine virtual_machine_name -vm_user_id user_id [-vm_type virtual_machine_type]
<volmgr_dir_path>tpconfig -add -storage_server server_name -stype server_type -sts_user_id user_ID [-password password] [-st storage_type]
<volmgr_dir_path>tpconfig -update -storage_server server_name -stype server_type -sts_user_id user_ID [-password password]
<volmgr_dir_path>tpconfig -delete -storage_server server_name -stype server_type -sts_user_id user_ID
<volmgr_dir_path>tpconfig -dev_ping [-drive -path drivepath | -robpath robotpath] [-nh ndmp_hostname]
tpconfig configures robots, drives, drive arrays, drive paths, and hosts for use with NetBackup.
On Windows systems, when your device configuration changes are complete, stop and restart the NetBackup Device Manager service.
The following four options apply only to NetBackup Enterprise Server. They specify the configuration for ACS (Automated Cartridge System) robots.
acsnum specifies the number for the robotic library as configured on the ACS library software host.
lsmnum specifies the Library Storage Module that has this drive.
panelnum specifies the robot panel where this drive is located.
Adds a drive or a robot, depending on the accompanying options.
Specifies the type of the disk array for which to add, update, or delete credentials.
The double quote marks (") are required only if name or displayname includes one or more spaces.
The disk array vendor provides the values for name:displayname. The name portion is a unique string used internally by NetBackup. The displayname portion is a more human-readable string that is used in NetBackup Administration Console displays and menus.
The values depend on the disk array vendor and the provider type that are used for the array, as follows:
To determine valid disk array type names, use the -list_array_types option.
Specifies a name for the drive. This name identifies the drive to Media Manager. If you do not specify a drive name, Media Manager generates a name. If you add or update shared drives (SharedDisk option), make this name as descriptive as possible.
Specifies the SCSI bus number to which the robot or drive connects.
You can find this information in the NetBackup Device Configuration Guide.
Specifies the number of hours between drive cleanings. When you add a drive, NetBackup starts to record the amount of time that volumes are mounted in that drive.
If the drive is in a robot and a cleaning volume is defined in the robot, the cleaning occurs in the following situation: The accumulated mount time exceeds the time that you specify for the cleaning frequency. NetBackup resets the mount time when the drive is cleaned.
If the drive is stand-alone or a cleaning tape is not defined, the following message appears in the tpclean -L output comment field: NEEDS CLEANING. To clean the drive, use the tpclean command.
A frequency-based cleaning is not needed if TapeAlert is used.
This option is only applicable for NetBackup Enterprise Server.
For a robot whose robotic control is on another host, this option specifies the host that controls the robotic library.
This option applies only for the TL8, TLD, and TLH robots that can have the robotic control on another host, and for ACS and TLM robots.
For an ACS robot, specify the host name where the ACS library software is installed. For a TLM robot, specify the host name where the DAS server software is installed.
Adds a comment about the drive. This field is useful for storing SCSI inquiry data so you can easily check the drive type and firmware level.
Lists the current configuration information. On UNIX and Linux systems, the listing is sent to stdout). This option may truncate drive names to 22 characters. It can determine if the robot is in a PIRD state (pend if robot down). "PIRD = yes" means that the robot is in a PIRD state.
Configures a user name and password for all media servers and NDMP host combinations under a given master server. You add a user name and password only once per filer. Use this option with the -add, -update, or -delete command to specify the user name and password.
Deletes a drive, robot, or host credentials, depending on the accompanying options.
Specifies the hostname of the disk array. This option can be used only if the NetBackup Snapshot Client license key has been installed.
Specifies the user name that NetBackup must use to communicate with a disk array. This option can be used only if the NetBackup Snapshot Client license key has been installed.
Displays the credentials on the NDMP host that is on the media server.
Use this option with the -add option to specify that the action is for a drive.
Specifies the drive index. Use this option with the -update, -delete,or the -multiple_delete command that specifies the action for a drive.
Sets the initial status of the tape drive to the UP, DOWN, or DISABLED state. Discovered drive paths are enabled (UP) by default. An administrator or operator can disable or configure the drive path up/down. The user can also perform this action with options in the Device Management window.
A drive status of DISABLED means NetBackup stores the path but never to use it. In addition, if subsequent discoveries of this drive path occur, NetBackup does not configure it for use.
Lists the complete tape device configuration as seen by the EMM database. This information includes all media servers, master server, NDMP hosts, and their credentials.
Configures a user name and password for all media servers that are connected to a filer. You add a user name and password only once per filer. Use this option with the -add, -update, or -delete command to specify the user name and password.
Specifies a drive index, a unique number that is used to identify the drive. When you add a drive, you are not required to supply a drive index, since Media Manager uses the next available drive index. Each drive on a particular host must have a unique index number.
Creates an encrypted key so that encrypted credentials can be safely sent over the network. If the -key option is specified, tpconfig assumes the password to be provided in MD5 encrypted format.
Lists the current device configuration (to stdout). On Windows systems, -l displays the Windows device paths in the {p,b,t,l} encoded form: p is the port, b is the bus, t is the target, and l is the LUN.
Lists the disk array types for which you can add and manage credentials.
To restrict the output to the disk array types that are valid for a specific media server, specify that media server.
The command output is in a name:displayname format for each array type.
The disk array vendor provides the values for name:displayname. The name portion is a unique string used internally by NetBackup. The displayname portion is a more human-readable string that is used in NetBackup Administration Console displays and menus.
The values depend on the disk array vendor and the provider type that are used for the array, as follows:
Specifies the logical unit number (or SCSI ID) to which the robot or drive connects.
For information about device paths, see the NetBackup Device Configuration Guide.
Deletes multiple drives or robots, depending on the accompanying options.
Specifies the hostname of the NDMP server or the PureDisk server.
Drive paths are not verified. Normally, tpconfig verifies that the no rewind on close drive path has the correct minor number bits that relate to the following: no rewind, variable, Berkeley-style, and so on. This option may be helpful if you use non-standard platform device files, so make sure that your device files are correct.
This option is used on Windows systems. It specifies the logical unit number (or SCSI ID) to which the robot or drive connects. You can find this information in the registry. Use this command to add, upgrade, or delete an existing logical unit number.
When this option is used with the -update command, you can change the path to one that already exists in the database. If the path does not exist, an error occurs.
This option is used on Windows systems. It specifies an existing target number (or SCSI ID) to which the robot or drive connects. Use this command to add, upgrade, or delete an existing target.
Sets the password to log in to the NDMP, PureDisk, OpenStorage, or virtual machine host.
Specifies the drive's device path on the NDMP filer.
On Windows systems, the drive_path variable is a non-NDMP Windows device path for drives. Use it in the {p,b,t,l} format: p is the port, b is the bus, t is the target, and l is the LUN. This information is located in the registry.
Sets or clears the PIRD state of the robot (pend if the robot is down). If a robot is in a PIRD state, any storage-unit-related mount requests for this robot pend when the robotic control is down.
Specifies the SCSI port number to which the robot or drive connects. You can find this information in the registry.
Specifies the IP port number on which the disk array accepts a connection from NetBackup.
Specifies the physical location (within the robot) of the drive. If you assign the wrong number, NetBackup does not detect it. An error eventually occurs because the robotic control tries to mount media on the wrong drive.
You can usually determine the physical location by checking the connectors to the drives or the vendor documentation.
A unique number that identifies the robot to NetBackup. You assign the robot number with the add option.
Robot numbers must be unique for all robots, regardless of the robot type or the host that controls them.
On NetBackup Enterprise Server, robot numbers must be unique for all robots that share the same EMM server (and use the same EMM database). This requirement applies regardless of the robot type or the host that controls them. For example, the same EMM server but different hosts control two TLD robots. If so, the robot numbers must be different.
Specifies the robot's device path on the NDMP filer.
On Windows systems, the drive_path variable is a non-NDMP Windows device path for drives. Use it in the {p,b,t,l} format: p is the port, b is the bus, t is the target, and l is the LUN. This information is located in the registry.
Specifies the type of robot that you plan to configure and can be any of the types that NetBackup supports. Check the support Web site to determine the robot type to specify for a particular model of robotic library.
Robot type can be any of the following for NetBackup Enterprise Server:
acs for Automated Cartridge System, tl4 for tape library 4mm, tl8 for tape library 8mm, tld for tape library DLT, tlh for tape library Half-inch, tlm for tape library Multimedia
Robot type can be any of the following for NetBackup server:
Specifies the access protection that NetBackup uses for SCSI tape drives.
SPR - SCSI Persistent Reserve In / Persistent Reserve Out
The -snap_vault_filer flag is used with the NetApp P3 feature. Set this flag when the user name and password for that filer are stored. If not set, the user interfaces do not allow the user to add volumes on this filer. If you stash the user name and password without this flag, do the following: Decide if you want its functionality, do a tpconfig -delete operation, and then re-add it with the flag. This flag is used with the NetApp P3 feature when used in the following context:
tpconfig -add -user_id root -nh mmnetapp2-target target -snap_vault_filer
Specifies a numeric value that identifies the storage server properties. The storage vendor provides this value. Whether the disk is formatted and how it is attached are mutually exclusive and complementary.
The storage_type value is the sum of whether the disk is formatted or raw (1 or 2) and how the disk is attached (4 or 8). The default value is 9 (a network attached, formatted disk).
Specifies the user name that is needed to log into the storage server. If the storage server does not require logon credentials, enter dummy credentials.
Specifies a string that identifies the storage server type. The storage vendor provides the string.
Specifies the target number (or SCSI ID) to which the robot or drive connects.
You can find this information in the registry (Windows systems) or the NetBackup Device Configuration Guide.
Specifies the type of drive that you configure.
Drive type can be any of the following for NetBackup Enterprise Server:
4mm for 4mm tape drive, 8mm for 8mm tape drive, 8mm2 for 8mm tape drive 2 , 8mm3 for 8mm tape drive 3, dlt for DLT tape drive, dlt2 for DLT tape drive 2, dlt3 for DLT tape drive 3, dtf for DTF tape drive, qscsi for QIC tape drive, hcart for Half-inch cartridge drive, hcart2 for Half-inch cartridge drive 2, hcart3 for half-inch cartridge drive 3. Drive type can be any of the following for NetBackup server :, 4mm for 4mm tape drive , 8mm for 8mm tape drive, dlt for DLT tape drive, hcart for Half-inch cartridge drive, qscsi for QIC tape drive.
Changes the configuration information for a drive or robot. For example, you can add a drive to a robot.
Specifies the user ID of a particular NDMP host on a media server for which you add credentials.
This option applies only to NetBackup Enterprise Server. It specifies the IBM device name for a TLH robotic drive or the DAS drive name for a TLM robotic drive.
Specifies the host name of the virtual machine whose credentials are to be added, updated, or deleted. This option can be used only if the NetBackup Snapshot Client license key has been installed.
Specifies the type of virtual machine. The following are possible values:
1 - VMware VirtualCenter Servers
This option can be used only if the NetBackup Snapshot Client license key has been installed.
Specifies the user name that NetBackup must use to communicate with a virtual machine's disk array. This option can be used only if the NetBackup Snapshot Client license key has been installed.
tpconfig -d may truncate drive names to 22 characters, and tpconfig -l may truncate drive names to 32 characters. To list the full drive name, use tpconfig -dl.
The delete multiple NDMP host credentials applies only to credentials that are specific to this host and the specified filer. In other words, it has no default or no filer credentials.
In the following examples, the command that is entered is shown on multiple lines because of page limitations. The actual command is entered on one line.
EXAMPLE 1: Robotic control on the local Windows server
The following example adds a robot that connects directly to a Windows host, and also adds drives to that robot.
The following procedure applies only to NetBackup server:
Add the robot by using the following command:
# tpconfig -add -robot 7 -robtype tld -port 0 -bus 0 -target 2 lun 0
If there are drives in the robot that have not been configured, add them.
The following command configures the drive with the system name of Tape0 under control of the robot that is configured in step 1. ( The server has attached and recognized Tape0.)
# tpconfig -add -drive -type dlt -port 1 -bus 2 -target 3 -lun 4 -comment "DEC DLT2000 8414" -index 0 -drstatus up -robot 7 -robtype tld -robdrnum 1 -asciiname DLT2000_D1
The command in this example uses the comment field. This field is useful for storing the drive's SCSI inquiry data so that drive type and firmware level can be easily checked.
If the robot contains any drives that are currently configured as stand-alone drives, update the drive configuration to place them under robotic control.
The following commands update the configuration for drives 1 and 2:
# tpconfig -update -drive 1 -type dlt -robot 7 -robtype tld -robdrnum 1 # tpconfig -update -drive 2 -type dlt -robot 7 -robtype tld -robdrnum 2
|
Note: |
Assign the correct robot drive number to the drives. If robot drive numbers are incorrect, tape mounts or backups may fail. |
EXAMPLE 2: Robotic control on the remote host
This example applies only to NetBackup Enterprise Server:
It assumes that one or more tape drives that are in the robot, connect to the Windows host where you currently manage devices.
The following is a sequence of tpconfig operations that adds a robot that connects to another host:
Add the robot by executing the following command:
# tpconfig -add -robot 9 -robtype tld -cntlhost perch
Ensure that the robot number matches the one on the control host.
If the robot contains any drives that are currently configured as stand-alone, update the drive configuration to place them under robotic control.
The following commands update the configuration for drives 1 and 2:
# tpconfig -update -drive 1 -type dlt -robot 9 -robtype tld -robdrnum 1 # tpconfig -update -drive 2 -type dlt -robot 9 -robtype tld -robdrnum 2
If there are drives in the robot that have not been configured, add them now.
The following command configures the drive with the system name of Tape0 under control of the robot that is configured in step 1. (The Windows server has attached and recognized Tape0.)
# tpconfig -add -drive -type dlt -port 1 -bus 2 -target 3 -lun 4 -comment 'DEC DLT2000 8414' -index 3 -drstatus up -robot 9 -robtype tld -robdrnum 3 -asciiname DLT2000_D3
EXAMPLE 3: Configuring new stand-alone drives
The following is an example of how to add a stand-alone drive after the drive is installed:
# tpconfig -add -drive -type dlt -port 1 -bus 2 -target 3 -lun 4 -comment 'DEC DLT2000 8414' -index 6 -asciiname DLT2000_standalone
EXAMPLE 4: Demonstrate how Windows displays device paths
This example demonstrates how to how the -l option displays the Windows device paths in the p, b, t, l format.
C:\Program Files\VERITAS\Volmgr\bin>tpconfig -l
Device Robot Drive Robot Drive Device
Type Num Index Type DrNum Status Comment Name Path
robot 0 - TLD - - - - {3,1,0,1}
robot 1 - TLD - - - - {3,1,0,3}
robot 2 - TLD - - - - {3,1,2,0}
drive - 0 pcd - DISABL - SONY.SDX-400V.000 {1,0,0,0}
drive - 1 hcart2 2 UP - IBM.ULTRIUM-TD2.001 {3,1,0,2}
drive - 1 hcart2 2 UP - IBM.ULTRIUM-TD2.001 {3,1,1,2}
drive - 2 hcart2 1 UP - IBM.ULTRIUM-TD2.002 {3,1,0,5}
drive - 2 hcart2 1 UP - IBM.ULTRIUM-TD2.002 {3,1,1,5}
drive - 3 hcart 1 DOWN - IBM.ULTRIUM-TD1.003 {3,1,0,6}
drive - 3 hcart 1 UP - IBM.ULTRIUM-TD1.003 {3,1,1,6}
drive - 4 hcart 2 UP - IBM.ULTRIUM-TD1.004 {3,1,0,7}
drive - 4 hcart 2 UP - IBM.ULTRIUM-TD1.004 {3,1,1,7}
drive - 5 hcart2 2 UP - IBM.ULTRIUM-TD2.005 {3,1,2,1}
drive - 6 hcart2 1 UP - IBM.ULTRIUM-TD2.006 {3,1,2,2}