Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- About the required Linux SCSI drivers
- About configuring robot and drive control for Linux
- 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
- 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
- NetBackup robotic control, communication, and logging for UNIX systems
- ACS robotic test utility
- ACS configurations supported
- Device configuration examples
Preventing Solaris driver unloading
The drivers NetBackup uses are the st driver (from Sun), the sg driver (from Veritas), and Fibre Channel drivers. Problems may occur depending on when the driver loads and unloads. These problems can range from a SCSI bus not able to detect a device to system panics.
Veritas recommends that you prevent Solaris from unloading the drivers from memory.
The following procedures describe how to prevent Solaris from unloading the drivers from memory.
To prevent Solaris from unloading the drivers from memory
- Add the following forceload statements to the /etc/system file:
forceload: drv/st forceload: drv/sg
To prevent Solaris from unloading the Fibre Channel drivers from memory
- Add an appropriate forceload statement to the /etc/system file.
Which driver you force to load depends on your Fibre Channel adapter. The following is an example for a Sun Fibre Channel driver (SunFC FCP v20100509-1.143):