Robot control section

The Robot control section defines the type of control for the robot. The options you configure depend on the robot type and the media server type.

See About robot control.

See Robot is controlled locally by this device host.

See Robot control is attached to an NDMP host.

See Robot control is handled by a remote host.

See ACSLS host.

See DAS server.

See Library name.

See LMCP device file.

See NDMP host name.

See Robot control host.

See Robot device.

See Robotic device file.

See Robot device path.

See SCSI coordinates.

Robot is controlled locally by this device host

This option specifies that the host to which the robot is attached controls the robot.

You must configure other options (depending on the robot type and device host type).

See Library name.

See LMCP device file.

See Robot device.

See Robotic device file.

Robot control is attached to an NDMP host

The following applies only to NetBackup Enterprise Server.

This option specifies that an NDMP host controls the robot.

You must configure other options (depending on the robot type and device host type).

See NDMP host name.

See Robot device path.

See SCSI coordinates.

Robot control is handled by a remote host

The following applies only to NetBackup Enterprise Server.

Specifies that a host other than the device host controls the robot.

You must configure other options (based on the selected robot type and device host platform).

See ACSLS host.

See DAS server.

See Robot control host.

ACSLS host

The ACSLS host option applies only to NetBackup Enterprise Server.

The name of the Sun StorageTek ACSLS host; the ACS library software resides ACSLS host. On some UNIX server platforms, this host can also be a media server or EMM server.

The ACS library software component can be any of the following:

  • Automated Cartridge System Library Software (ACSLS)

    Examples are available.

    See the NetBackup Device Configuration Guide.

  • STK Library Station

  • Storagenet 6000 Storage Domain Manager (SN6000).

    This STK hardware serves as a proxy to another ACS library software component (such as ACSLS).

Note:

If the device host that has drives under ACS robotic control is a Windows server, STK LibAttach software must also be installed. Obtain the appropriate LibAttach software from STK. See the Symantec support Web site for the latest compatibility information.

An overview of ACS robots is available.

See the NetBackup Device Configuration Guide.

DAS server

The following applies only to NetBackup Enterprise Server.

The name of the ADIC DAS/SDLC server that controls TLM robots.

This server is an OS/2 workstation near or within the robot cabinet or a Windows server near the ADIC Scalar library.

An overview of TLM robots is available.

See the NetBackup Device Configuration Guide.

Library name

The following applies only to a TLH robot on NetBackup Enterprise Server only.

For UNIX device hosts (except AIX), the library name that is configured on the UNIX host.

For Windows devices hosts, do the following:

  • Determine the library name by viewing the C:\winnt\ibmatl.conf file.

    For example, in the following example entry in that file, 3494AH is the library name:

    3494AH 176.123.154.141 ibmpc1

  • Enter the library name.

An overview of TLH robots is available.

See the NetBackup Device Configuration Guide.

LMCP device file

Applies to NetBackup Enterprise Server on an AIX device host only.

The name of the Library Manager Control Point device file name for TLH robot types. Use the same name that is configured on the AIX device host.

NDMP host name

The name of the NDMP host to which the robot is attached.

Robot control host

The following applies only to NetBackup Enterprise Server.

This option specifies the host that controls the robot.

The name of the host on which the robot information is defined for TL8, TLD, or TLH robots.

See Robot control section.

Robot device

The following applies to a Windows device host only.

The name of the robot device.

Click Browse and then select a robot from the list that appears in the Devices dialog box.

If the discovery operation fails to discover a robot, click More in the Devices dialog box. Enter either the Port, Bus, Target, and LUN numbers or the device name in the next dialog box. If the browse operation fails for any other reason, a dialog box appears that lets you enter the information.

You can find Port, Bus, Target, and LUN numbers by using Windows management tools.

If the browse operation does not find attached robots, an error dialog box appears.

Robotic device file

The following applies to a UNIX device host only.

The device file that is used for SCSI connections. The device files are located in the /dev directory tree on the device host.

To specify the robotic device file, click Browse and then select a robotic device file from the list that appears in the Devices dialog box.

If the browse operation fails to show all of the attached robots, click More. Enter the path of the device file in the robotic device file field.

If the browse operation fails to show all of the attached robots, click Other Device. Enter the path of the device file in the next dialog box.

If the browse operation does not find attached robots, an error dialog box appears.

Information about how to add device files is available.

See the NetBackup Device Configuration Guide.

Robot device path

NDMP host only.

The name of the robotic device that is attached to the NDMP host.

SCSI coordinates

Windows systems only.

The device attributes on Windows system cannot change during NetBackup operation.

The Port, Bus, Target, and LUN SCSI coordinates for the robotic device.