Veritas NetBackup™ SAN Client and Fibre Transport Guide
- 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
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.