Please enter search query.
Search <book_title>...
Veritas NetBackup™ SAN Client and Fibre Transport Guide
Last Published:
2020-09-14
Product(s):
NetBackup (8.3.0.1)
- Introducing SAN Client and Fibre Transport
- Planning your deployment
- About SAN Client storage destinations
- Preparing the SAN
- Licensing SAN Client and Fibre Transport
- Configuring SAN Client and Fibre Transport
- Configuring a Fibre Transport media server
- Configuring SAN clients
- Configuring SAN clients in a cluster
- Fibre Transport properties
- Configuring SAN client usage preferences
- Managing SAN clients and Fibre Transport
- Disabling SAN Client and Fibre Transport
- Troubleshooting SAN Client and Fibre Transport
- About unified logging
- Appendix A. AIX Specific Configuration Details
- Appendix B. HP-UX Specific Configuration Details
- About configuring legacy device files
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.