Veritas NetBackup™ SAN Client and Fibre Transport Guide
- 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
- 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 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
- 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
- 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 FCP (PA-RISC)
The following example shows how create a sctl device file for an HP VLS9000 robot. NetBackup uses the device file for robotic control.
To create an FCP robotic device file for HP-UX PA-RISC
- Invoke the ioscan -f command. The following output example is edited for readability:
ioscan -f Class I H/W Path Driver S/W State H/W Type Description ============================================================================= fc 0 0/2/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter fcp 4 0/2/0/0.10 fcp CLAIMED INTERFACE FCP Domain ext_bus 6 0/2/0/0.10.11.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface target 5 0/2/0/0.10.11.255.0.0 tgt CLAIMED DEVICE autoch 2 0/2/0/0.10.11.255.0.0.0 schgr CLAIMED DEVICE HP VLS tape 5 0/2/0/0.10.11.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 4-SCSI tape 6 0/2/0/0.10.11.255.0.0.2 stape CLAIMED DEVICE HP Ultrium 4-SCSI tape 7 0/2/0/0.10.11.255.0.0.3 stape CLAIMED DEVICE HP Ultrium 4-SCSI Examine the output for the card instance number and the SCSI ID and LUN of the robotic device. In this example, the interface card instance number (the I column) is 6. If you use the card's H/W Path value as a mask (0/2/0/0.10.11.255.0), you see the following:
An HP VLS9000 robot is at SCSI ID 0, LUN 0.
Three Ultrium 4-SCSI drives are at SCSI ID 0 and LUN 1, LUN 2, and LUN 3.
- Determine the character major number of the sctl driver by using the lsdev command, as follows:
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 file for the HP VLS9000 robotic control are as follows. The card instance number is 6, the target is 0, and the LUN is 0.
cd /dev/sctl /usr/sbin/mknod c6t0l0 c 203 0x060000
If you add the robot to NetBackup manually, specify the following pathname for robotic control:
/dev/sctl/c6t0l0