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
- 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
Creating legacy SCSI and FCP robotic controls on HP-UX
You must create the robotic control device files for the sctl driver manually; they are not created automatically when the system boots.
Before you create the device files, you must do the following:
Install and configure the sctl driver. For more information, see the HP-UX scsi_ctl(7) man page.
The sctl driver may be the default pass-through driver on your system. If so, you do not have to configure the kernel to use the sctl pass-through driver.
Install and configure the schgr device driver. For more information, see the HP-UX autochanger(7) man page.
Attach the devices.
Examples of how to create the device files are available.
To create sctl device files
- Invoke the ioscan -f command to obtain SCSI bus and robotic control information.
Examine the output for the card instance number and the SCSI ID and LUN of the robotic device, as follows:
The instance number of the card is in the I column of the output.
The H/W Path column of the changer output (schgr) includes the SCSI ID and LUN. Use the card's H/W Path value to filter the changer's H/W Path entry; the SCSI ID and the LUN remain.
- Determine the character major number of the sctl driver by using the following command:
lsdev -d sctlExamine the output for an entry that shows sctl in the Driver column.
- Use the following commands to create the device file for the SCSI robotic control:
mkdir /dev/sctl cd /dev/sctl /usr/sbin/mknod 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.