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
Creating device files for SAN Clients on HP-UX
NetBackup SAN clients use tape drivers and SCSI pass-through methods for Fibre Transport traffic to NetBackup FT media servers. On HP-UX systems, NetBackup SAN clients require the sctl driver and pass-through tape drive device files.
The following table describes the tasks that create the device files. Before you create the device files, the NetBackup FT media server must be active and the SAN must be zoned correctly.
Table: SAN Client device file tasks
Step | Action | Description |
|---|---|---|
Step 1 | If the sctl driver is not the default pass-through driver on your system, install and configure the sctl driver. | See the HP-UX scsi_ctl(7) man page. |
Step 2 | Create the pass-through paths required. |
The media server FT devices appear as ARCHIVE Python tape devices during SCSI inquiry from the SAN client. However, they are not tape devices and do not appear as tape devices in NetBackup device discovery.
You can use legacy device files for SAN client pass-through paths for Fibre Transport traffic to NetBackup media servers.