Please enter search query.
Search <book_title>...
NetBackup™ Device Configuration Guide
Last Published:
2023-10-23
Product(s):
NetBackup (10.3.0.1, 10.3)
- 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 Emulex HBAs
If you use a /usr/openv/volmgr/AVRD_DEBUG touch file on a NetBackup media server with an Emulex HBA driver, the system log may contain entries similar to the following:
Unknown drive error on DRIVENAME (device N, PATH) sense[0] = 0x70, sense[1] = 0x0, sensekey = 0x5
You can ignore these messages.