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
About legacy pass-through paths for tape drives
Although NetBackup requires the /dev/rmt device files to configure tape drives, NetBackup uses pass-through device files for drive access.
On media servers, NetBackup automatically creates pass-through device files if the appropriate/dev/rmt tape drive device files exist. NetBackup creates the pass-through device files in the /dev/sctl directory.
NetBackup does not modify or delete any existing pass-through paths.
NetBackup does not detect the type of adapter cards that are installed in the system. Therefore, NetBackup creates pass-through paths for tape drives connected to the adapter cards that do not support pass through. These pass-through paths do not cause problems.
Although NetBackup uses the pass-through device files during tape drive operations, you specify the /dev/rmt
device files when you configure the drives in NetBackup. NetBackup then uses the appropriate pass-through device files.
Usually, you do not have to create pass-through paths for drives. However, instructions to do so are provided for reference.
NetBackup SAN clients require legacy pass-through device files.
Note:
Pass-through paths are not supported on HP-PB adapters such asHP28696A - Wide SCSI or HP 28655A - SE SCSI.