Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Device Configuration Guide
  3. Section I. Operating systems
  4. Solaris
  5. Preventing Solaris driver unloading
Veritas NetBackup™ Device Configuration Guide

Preventing Solaris driver unloading

When system memory is limited, Solaris unloads unused drivers from memory and reloads drivers as needed. Tape drivers are often unloaded because they are used less often than disk drivers.

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):

    forceload: drv/fcp

Feedback

Was this page helpful?
Previous

Configuring 6 GB and larger SAS HBAs in Solaris

Next

About Solaris robotic controls

Feedback

Was this page helpful?