Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
 - Section I. Operating systems
- AIX
- Before you begin configuring NetBackup on AIX
 - RS/6000 AIX adapter number conventions
 - About AIX persistent naming support
 - About configuring robotic control device files in AIX
 - About device files for SAN Clients on AIX
 - About configuring tape drive device files in AIX
- About choosing a tape driver on AIX
 - About non-QIC tape drives on AIX
 - About extended-file marks for drives
 - About fast-tape positioning (locate-block) on AIX
 - About no rewind device files on AIX
 - Creating AIX no rewind device files for tape drives
 - Using multiple tape densities on AIX
 - About SPC-2 SCSI reserve on AIX
 - Disabling SPC-2 SCSI reserve in AIX
 
 - About Sony AIT drives on AIX
 - AIX command summary
 
 - HP-UX
- Before you begin configuring NetBackup on HP-UX
 - About robotic control on HP-UX
 - About HP-UX device addressing schemes
 - HP-UX tape drive device file requirements for NetBackup
 - About device drivers and files for HP-UX persistent DSFs
 - About configuring persistent DSFs
 - About HP-UX legacy device drivers and files
 - Creating device files for SAN Clients on HP-UX
 - About configuring legacy device files
 - About SPC-2 SCSI reserve on HP-UX
 - Disabling SPC-2 SCSI reserve in HP-UX
 - About disabling the HP-UX EMS Tape Device Monitor for a SAN
 - HP-UX command summary
 
 - Linux
- Before you begin on Linux
 - About the required Linux SCSI drivers
 - Verifying the Linux drivers
 - About configuring robot and drive control for Linux
 - Verifying the device configuration on Linux
 - About SAN clients on Linux
 - About SCSI persistent bindings for Linux
 - About Emulex HBAs
 - Utilities to test SCSI devices
 - Linux command summary
 
 - Solaris
- Before you begin on Solaris
 - About the NetBackup sg driver
 - Determining if the NetBackup sg driver is installed
 - Special configuration for the Oracle StorEdge Network Foundation HBA driver
 - About binding Fibre Channel HBA drivers
 - Configuring Solaris 10 x86 for multiple drive paths
 - Installing/reinstalling the sg and the st drivers
 - Configuring 6 GB and larger SAS HBAs in Solaris
 - Preventing Solaris driver unloading
 - About Solaris robotic controls
 - About Solaris tape drive device files
 - Configuring Solaris SAN clients to recognize FT media servers
 - Uninstalling the sg driver on Solaris
 - Solaris command summary
 
 - Windows
 
 - AIX
 - Section II. Robotic storage devices
- Robot overview
 - Oracle StorageTek ACSLS robots
- About Oracle StorageTek ACSLS robots
 - Sample ACSLS configurations
 - Media requests for an ACS robot
 - About configuring ACS drives
 - Configuring shared ACS drives
 - Adding tapes to ACS robots
 - About removing tapes from ACS robots
 - Robot inventory operations on ACS robots
 - NetBackup robotic control, communication, and logging
 - ACS robotic test utility
 - Changing your ACS robotic configuration
 - ACS configurations supported
 - Oracle StorageTek ACSLS firewall configuration
 
 - Device configuration examples
 
 
An ACS robot on a UNIX server example
The following figure shows a UNIX server and ACS robot configuration.
This configuration uses an Automated Cartridge System (ACS) robot for storage. Host shark can be a UNIX NetBackup master server or media server.
The following are some items to note when you review this example:
The ACSLS Host (in the Add Robot dialog) is server 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, PANEL, LSM, and DRIVE numbers are part of the ACS library software configuration and must be obtained from that system.
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. That entry configures NetBackup to use the ACS Storage Server Interface (acsssi) to communicate with the ACS library software host.
The following table shows the robot attributes.
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 Name  | shark_drive_0  | 
Drive Type  | 1/2" Cartridge (hcart)  | 
No Rewind Device  | /dev/rmt1.1  | 
Drive is in a Robotic Library  | Yes  | 
Robotic Library  | ACS(0) - whale  | 
ACS  | ACS Number: 0 LSM Number: 2 PANEL Number: 0 DRIVE Number: 0  | 
The following table shows the drive 1 attributes.
Table: Add Drive dialog entries (drive 1)
Dialog box field  | Value  | 
|---|---|
Device Host  | shark  | 
Drive Name  | shark_drive_1  | 
Drive Type  | 1/2" Cartridge (hcart)  | 
No Rewind Device  | /dev/rmt1.1  | 
Drive is in a Robotic Library  | Yes  | 
Robotic Library  | ACS(0) - whale  | 
ACS  | ACS Number: 0 LSM Number: 2 PANEL Number: 0 DRIVE Number: 1  |