Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- Linux
- About the required Linux SCSI drivers
- About configuring robot and drive control for Linux
- Solaris
- Installing/reinstalling the sg and the st drivers
- About Solaris robotic controls
- About Solaris tape drive device files
- Configuring Solaris SAN clients to recognize FT media servers
- Windows
- Linux
- Section II. Robotic storage devices
- Robot overview
- Oracle StorageTek ACSLS robots
- About removing tapes from ACS robots
- Robot inventory operations on ACS robots
- NetBackup robotic control, communication, and logging
- ACS robotic test utility
- ACS configurations supported
- Device configuration examples
An ACS robot on a Windows server example
The following figure shows a Windows server and ACS robot configuration.
This configuration uses an Automated Cartridge System (ACS) robot for storage. Server shark can be a Windows NetBackup master server or media server.
The following are items to note when you review this example:
The Oracle StorageTek ACSLS host (in the Add Robot dialog) is host whale, where the ACS library software resides. In this example, Automated Cartridge System Library Software (ACSLS) is installed as the ACS library software.
On some server platforms, you can run NetBackup media server software and ACS library software on the same server. Therefore, you need only one server.
The ACS, LSM, PANEL, and DRIVE numbers are part of the ACS library software configuration and must be obtained from the administrator of that host.
Robot number and ACS number are different terms. Robot number is the robot identifier used in NetBackup. ACS number is the robot identifier in ACS library software. These numbers can be different, although they both default to zero.
If you connnect the drives through an independent control unit, you must use the correct Logical Unit Numbers (LUNs) so that the correct tape name is used.
The Add Robot dialog entries include an ACSLS Host entry so that the ACS library software host communicates by using STK LibAttach software. This software must be installed on each Windows server that has the ACS drives attached to it.
The following table shows the robot attributes for the remote host shark.
Table: Add Robot dialog entries (remote host)
Dialog box field | Value |
---|---|
Device Host | shark |
Robot Type | ACS (Automated Cartridge System) |
Robot Number | 0 |
Robot control is handled by a remote host | Set (cannot be changed for this robot type) |
ACSLS Host | whale |
The following table shows the drive 0 attributes.
Table: Add Drive dialog entries (drive 0)
Dialog box field | Value |
---|---|
Device Host | shark |
Drive Type | 1/2" Cartridge (hcart) |
Drive Name | shark_drive_0 |
Path Information | [5,0,1,0] |
Drive is in a Robotic Library | Yes |
Robotic Library | ACS(0) - whale |
ACS | ACS: 0 LSM: 0 PANEL: 2 DRIVE: 0 |
The following table shows the drive attributes for drive 1.
Table: Add Drive dialog entries (drive 1)
Dialog box field | Value |
---|---|
Device Host | shark |
Drive Type | 1/2" Cartridge (hcart) |
Drive Name | shark_drive_1 |
Path Information | [4,0,1,1] |
Drive is in a Robotic Library | Yes |
Robotic Library | ACS(0) - whale |
ACS | ACS: 0 LSM: 0 PANEL: 2 DRIVE: 1 |