tpautoconf

tpautoconf — discover and configure devices

SYNOPSIS

<volmgr_dir_path>tpautoconf -get_gdbhost

<volmgr_dir_path>tpautoconf -set_gdbhost host_name

<volmgr_dir_path>tpautoconf -verify ndmp_host_name

<volmgr_dir_path>tpautoconf -probe ndmp_host_name

<volmgr_dir_path>tpautoconf -report_disc

<volmgr_dir_path>tpautoconf -replace_drive drive_name -path drive_path

<volmgr_dir_path>tpautoconf -replace_robot robot_number -path robot_path

On Windows systems, <volmgr_dir_path> is <install_path>\Volmgr\bin\

DESCRIPTION

The Device Configuration Wizard normally uses tpautoconf to discover devices. This wizard calls tpautoconf with a different set of options.

The get and the set options are useful in special situations. For example, use them to specify a different host as the Enterprise Media Manager (EMM) server. The EMM server name is automatically defined when NetBackup is installed.

For more information about how to manage the EMM server, refer to "Managing the EMM server" of the NetBackup Administrator's Guide, Volume I.

Use -report_disc, -replace_drive, and -replace_robot to reconfigure the devices in the EMM database to reflect a serial number change that a configured device replacement caused. After hardware replacement, the correction process requires that at least one system is available through the operating system. You may need to re-map, rediscover, and reboot the system.

After you configure the server or servers, use the -report_disc option to scan the current hardware and compare it with the configured hardware. A list of discrepancies appears and shows the replaced hardware and the new hardware.

Note:

Not all servers have access to robotic hardware. Even though no access is expected, these robots are listed as missing.

The final step to add replacement hardware is to configure the hardware on all servers by their operating systems. Then run the Device Configuration Wizard to configure the new path information.

Refer to "Changing your hardware configuration" in the NetBackup Administrator's Guide, Volume II.

You must have administrator privileges to run this command.

OPTIONS

Note:

Only limited validation of the option parameters is done.
-get_gdbhost

Returns the name of the EMM server host.

-set_gdbhost host_name

Sets the name of the EMMSERVER entry in bp.conf.

-probe ndmp_host_name

Lists all devices that are attached to the NDMP host.

-report_disc

Enables the device data to be queried from the EMM server to enable a "diff" to be run on these data records against those scanned. You can run this command on reconfigured servers to produce a list of new and missing hardware. This command scans for new hardware and produces a report that shows the new and the replaced hardware.

-replace_drive drive_name -path drive_path, -replace_robot robot_number -path robot_path

The EMM database is used to query or to update robot drives and robot records.

-verify ndmp_host_name

Verifies the server name of the NDMP host.

EXAMPLES

EXAMPLE 1

This command returns the name of the host where the Enterprise Media Manager database is stored:

# tpautoconf -get_gdbhost

EXAMPLE 2

This command sets the Enterprise Media Manager Server to be the host server2:

# tpautoconf -set_gdbhost server2

EXAMPLE 3

This example shows how the -report_disc command reports discrepancies between detected devices and the EMM database. Included is an example of how to use the -replace_drive drive_name -path drive_path command.

# tpautoconf -report_disc
======================= New Device (Tape) =======================
 Inquiry = "QUANTUM DLT8000		 0250"
 Serial Number = PXB08P3242
 Drive Path = /dev/rmt/119cbn
 Found as TLD(6), Drive = 1
===================== Missing Device (Drive) =====================
 Drive Name = QUANTUMDLT800014
 Drive Path = /dev/rmt/9cbn
 Inquiry = "QUANTUM DLT8000		 0250"
 Serial Number = PXB08P1345
 TLD(6) definition Drive = 1
 Hosts configured for this device:
  Host = plum
  Host = avocado

# tpautoconf -replace_drive QUANTUMDLT800014 -path /dev/rmt/119cbn
Found a matching device in EMM DB, QUANTUMDLT800014 on host plum
  update on host plum completed
Found a matching device in EMM DB, QUANTUMDLT800014 on host avocado
  update on host avocado completed

SEE ALSO

tpconfig