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
- Planning your SAN Client deployment
- SAN Client operational notes
- About SAN Client storage destinations
- How to choose SAN Client and Fibre Transport hosts
- About NetBackup SAN Client support for agents
- About NetBackup SAN Client support for clustering
- About NetBackup SAN Client support for Windows Hyper-V Server
- About NetBackup SAN Client unsupported restores
- About Fibre Transport throughput
- Converting a SAN media server to a SAN client
- Preparing the SAN
- Preparing the SAN
- About zoning the SAN for Fibre Transport
- About zoning the SAN for Fibre Transport for a 16-gigabit target mode HBA support
- About HBAs for SAN clients and Fibre Transport media servers
- About the 16-gigabit target mode HBAs for SAN clients and Fibre Transport media servers
- When selecting the HBA ports for SAN Client
- About supported SAN configurations for SAN Client
- Licensing SAN Client and Fibre Transport
- Configuring SAN Client and Fibre Transport
- Configuring SAN Client and Fibre Transport
- Configuring a Fibre Transport media server
- About the target mode driver
- About nbhba mode and the ql2300_stub driver
- About FC attached devices
- How to identify the HBA ports
- About HBA port detection on Solaris
- About Fibre Transport media servers and VLANs
- Starting nbhba mode
- Marking the Fibre Transport media server HBA ports
- Configuring the media server Fibre Transport services
- Configuring the media server Fibre Transport services for a 16-gigabit target mode HBA support
- Displaying the FTMS state for a 16-gigabit target mode HBA support
- Identifying the HBA ports for a 16-gigabit target mode HBA support
- Configuring SAN clients
- Configuring SAN clients in a cluster
- About configuring Fibre Transport properties
- Configuring Fibre Transport properties
- Fibre Transport properties
- About SAN client usage preferences
- Configuring SAN client usage preferences
- Managing SAN clients and Fibre Transport
- Enabling or disabling the Fibre Transport services
- Enabling or disabling the Fibre Transport services for a 16-gigabit target mode HBA support
- Rescanning for Fibre Transport devices from a SAN client
- Viewing SAN Client Fibre Transport job details
- Viewing Fibre Transport traffic
- Adding a SAN client
- Deleting a SAN client
- Disabling SAN Client and Fibre Transport
- Troubleshooting SAN Client and Fibre Transport
- About troubleshooting SAN Client and Fibre Transport
- SAN Client troubleshooting tech note
- Viewing Fibre Transport logs
- About unified logging
- Stopping and starting Fibre Transport services
- Stopping and starting Fibre Transport services for a 16-gigabit target mode HBA support
- Backups failover to LAN even though Fibre Transport devices available
- Kernel warning messages when Veritas modules load
- SAN client service does not start
- SAN client Fibre Transport service validation
- SAN client does not select Fibre Transport
- Media server Fibre Transport device is offline
- No Fibre Transport devices discovered
- Appendix A. AIX Specific Configuration Details
- Appendix B. HP-UX Specific Configuration Details
- HP-UX Reference Information
- Before you begin configuring NetBackup on HP-UX
- About HP-UX device drivers for legacy device files
- About legacy robotic control device files
- About legacy tape drive device files
- About legacy pass-through paths for tape drives
- Creating device files for SAN Clients on HP-UX
- About configuring legacy device files
- Index
Example of how to create a sctl device file for SCSI (PA-RISC)
In this example, the following robots exist:
An ADIC Scalar 100 library is on a SCSI bus with an instance number of 7, SCSI ID 2, and LUN 0.
The robotic control for an IBM ULT3583-TL library is on the same SCSI bus at SCSI ID 3 and LUN 0.
To create SCSI robotic device files for HP-UX PA-RISC
- Invoke the ioscan -f command, as follows:
ioscan -f Class I H/W Path Driver S/W State H/W Type Description ================================================================= ext_bus 7 0/7/0/1 c720 CLAIMED INTERFACE SCSI C896 Fast Wide LVD target 10 0/7/0/1.0 tgt CLAIMED DEVICE tape 65 0/7/0/1.0.0 stape CLAIMED DEVICE QUANTUM SuperDLT1 target 11 0/7/0/1.1 tgt CLAIMED DEVICE tape 66 0/7/0/1.1.0 stape CLAIMED DEVICE QUANTUM SuperDLT1 target 12 0/7/0/1.2 tgt CLAIMED DEVICE autoch 14 0/7/0/1.2.0 schgr CLAIMED DEVICE ADIC Scalar 100 target 13 0/7/0/1.3 tgt CLAIMED DEVICE autoch 19 0/7/0/1.3.0 schgr CLAIMED DEVICE IBM ULT3583-TL target 14 0/7/0/1.4 tgt CLAIMED DEVICE tape 21 0/7/0/1.4.0 atdd CLAIMED DEVICE IBM ULT3580-TD1 target 15 0/7/0/1.5 tgt CLAIMED DEVICE tape 19 0/7/0/1.5.0 atdd CLAIMED DEVICE IBM ULT3580-TD1
- Examine the output for the card instance number and the SCSI ID and LUN of the robotic device, as follows:
The card H/W Path is 0/7/0/1; the card instance number (I column) is 7. Apply the H/W Path value as a mask. The ADIC robotic device (schgr) is at SCSI ID 2, LUN 0 on this bus. The IBM robotic device (schgr) is at SCSI ID 3, LUN 0 on this bus.
- Determine the character major number of the sctl driver by using the following command:
lsdev -d sctl Character Block Driver Class 203 -1 sctl ctl
The output from this command shows that the character major number for the sctl driver is 203.
- The commands to create the device files follow. For the ADIC robot, the card instance number is 7, the target is 2, and the LUN is 0. For the IBM robot, the card instance number is 7, the SCSI ID is 3, and the LUN is 0.
cd /dev/sctl /usr/sbin/mknod c7t2l0 c 203 0x072000 /usr/sbin/mknod c7t3l0 c 203 0x073000
If you add the robots to NetBackup manually, you specify the following for ADIC robotic control and IBM robotic control respectively:
/dev/sctl/c7t2l0 /dev/sctl/c7t3l0