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
- 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 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
- Linux
- 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
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.