Please enter search query.
Search <book_title>...
Veritas NetBackup™ SAN Client and Fibre Transport Guide
Last Published:
2020-09-14
Product(s):
NetBackup (8.3.0.1)
- 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
Example of creating a no rewind device file
This topic provides an example of how to create a no rewind device file on AIX for NetBackup. Assume the device files for the wanted SCSI 8-mm tape drive (controller 1, SCSI ID 5) do not exist.
To create a no rewind device file for SCSI ID 5
- Determine the logical identifier for the SCSI controller as follows:
/usr/sbin/lsdev -C -c adapter | grep SCSI
The following output shows that scsi0 is the logical name for SCSI controller 1:
scsi0 Available 00-01 SCSI I/O Controller
- Determine if the device files exist for any device at SCSI ID 5.
/usr/sbin/lsdev -C -s scsi
The following output shows that some device files exist for tape and disk. However, a device files does not exist for the 8-mm tape drive at controller 1 (scsi0) and SCSI ID 5 (5,0):
hdisk0 Available 00-01-00-0,0 400 MB SCSI Disk Drive hdisk1 Available 00-01-00-1,0 400 MB SCSI Disk Drive rmt0 Available 00-01-00-3,0 Other SCSI Tape Drive
- Create the device file by using the following command:
mkdev -c tape -t ost -s scsi -p scsi0 -w 5,0
- Display the device files by issuing the following command:
/usr/sbin/lsdev -C -s scsi hdisk0 Available 00-01-00-0,0 400 MB SCSI Disk Drive hdisk1 Available 00-01-00-1,0 400 MB SCSI Disk Drive rmt0 Available 00-01-00-3,0 Other SCSI Tape Drive rmt1 Available 00-01-00-5,0 Other SCSI Tape Drive
- To ensure that the tape device is configured for variable-mode and extended file marks, use the following commands:
chdev -l rmt1 -a block_size=0 chdev -l rmt1 -a extfm=yes
- To configure the drive manually in NetBackup, enter the following device file pathname:
/dev/rmt1.1