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. NetBackup™ SAN Client and Fibre Transport Guide
  3. Configuring SAN Client and Fibre Transport
  4. Configuring a Fibre Transport media server
  5. About the target mode driver
NetBackup™ SAN Client and Fibre Transport Guide

About the target mode driver

On NetBackup FT media servers, QLogic or Emulex Fibre Channel host bus adapter (HBA) ports connect to the NetBackup SAN clients. Veritas provides a special target mode driver for the ports on those HBAs. Those ports must operate in target mode; the target mode driver replaces the default, initiator mode driver. Target mode applies only to QLogic or Emulex HBAs; the target mode configuration process affects only QLogic or Emulex HBA ports.

After the target mode driver binds to the HBA ports, those ports appear as two ARCHIVE Python tape devices during SCSI inquiry. However, they are not tape devices and do not appear as tape devices in NetBackup device discovery. Each port appears as two tape devices because operating systems allow only one data stream per port. Two pseudo tape devices for each port increases throughput.

More Information

About Linux concurrent FT connections

Feedback

Was this page helpful?
Previous

Configuring a Fibre Transport media server

Next

About nbhba mode and the ql2300_stub driver

Feedback

Was this page helpful?