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. Appendix B. HP-UX Specific Configuration Details
  4. About legacy robotic control device files
NetBackup™ SAN Client and Fibre Transport Guide

About legacy robotic control device files

For SCSI robotic control, NetBackup can use the /dev/sctl device files. The device file names have the following format:

/dev/sctl/cCARDtTARGETlLUN c Major 0xIITL00

Where:

  • CARD is the card instance number of the adapter.

  • TARGET is the SCSI ID of the robotic control.

  • LUN is the SCSI logical unit number (LUN) of the robot.

  • Major is the character major number (from the lsdev command).

  • II are two hexadecimal digits that represent the card instance number.

  • T is a hexadecimal digit that represents the SCSI ID of robotic control.

  • L is a hexadecimal digit that represents the SCSI LUN of the robotic control.

A library may have more than one robotic device. Each robotic device requires a device file.

Feedback

Was this page helpful?
Previous

About HP-UX device drivers for legacy device files

Next

About legacy tape drive device files

Feedback

Was this page helpful?