Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- AIX
- About configuring tape drive device files in AIX
- Creating AIX no rewind device files for tape drives
- HP-UX
- About device drivers and files for HP-UX persistent DSFs
- About configuring persistent DSFs
- About HP-UX legacy device drivers and files
- About configuring legacy device files
- 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
- AIX
- 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
About persistent DSF pass-through paths
Although NetBackup requires the /dev/rtape DSFs to configure tape drives, NetBackup uses pass-through device files for drive access.
NetBackup creates pass-through paths for all valid /dev/rtape paths. NetBackup creates the paths during device discovery or when you run the /usr/openv/volmgr/bin/scan command. The following is the file name format:
/dev/pt/pt_tape#
The # represents the instance number that matches the number in the /dev/rtape/tape#_BESTnb device file or that is retrieved from the ioscan output.
Although NetBackup uses the pass-through device files during tape drive operations, you specify the /dev/rtape
device files if you configure the drives manually in NetBackup. NetBackup then uses the appropriate pass-through device files.