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
 
 
HP-UX tape drive device file requirements for NetBackup
The following table describes the requirements for tape drive device files.
Table: Tape drive device file requirements
Requirement  | Description  | 
|---|---|
Berkeley-style close  | NetBackup requires Berkeley-style close for tape drive device files. The letter b in the file name indicates Berkeley-style close device files. In Berkeley-style close, the tape position remains unchanged by a device close operation. (Conversely, in AT&T-style close, the drive advances the tape to immediately after the next end-of-file (EOF) marker.) To establish the correct position for the next tape operation, applications must assume the tape's position after a close. NetBackup assumes Berkeley-style close on HP-UX systems.  | 
Fast-tape positioning (locate-block)  | HP-UX supports locate-block for most drive types for Fast Wide GSC SCSI adapters. For a list of drive types that NetBackup supports, see the Veritas Hardware Compatibility List: http://www.netbackup.com/compatibility NetBackup uses the locate-block command by default if a pass-through path is configured. To disable locate-block positioning, execute the following command: touch /usr/openv/volmgr/database/NO_LOCATEBLOCK When locate-block positioning is disabled, NetBackup uses the forward-space-file/record method.  | 
No rewind on close  | NetBackup requires no rewind on close for tape devices. The letter n in the file name indicates no rewind device files.  |