Please enter search query.
Search <book_title>...
Veritas NetBackup™ Device Configuration Guide
Last Published:
2018-09-17
Product(s):
NetBackup (8.3.0.1, 8.3, 8.2, 8.1.2)
- 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
About SCSI persistent bindings for Linux
Veritas recommends that you use persistent bindings to lock the mappings between the SCSI targets that are reported to Linux and the specific devices. The Linux kernel device manager udev creates the /dev/tape/by-path symbolic links to /dev/nstx device paths that NetBackup uses to communicate with tape drives. The udev system creates the persistent paths using the /dev/tape/by-path symbolic links. Do not change the default udev rules that create these paths.
If you cannot use binding with the HBA in your configuration, add an ENABLE_AUTO_PATH_CORRECTION entry in the /usr/openv/volmgr/vm.conf
file on all Linux media servers.