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
Marking the Fibre Transport media server HBA ports
You must mark the ports on the QLogic HBAs that you want to operate in target mode. The process modifies the port device IDs in NVRAM. When the FT server starts, the NetBackup target mode driver binds automatically to the QLogic HBA ports that you marked.
Before you mark ports, you must start nbhba mode.
See Starting nbhba mode.
The following procedures describe how to mark the HBA ports and if necessary how to reverse this process and return the ports to the initiator mode driver:
You must be the root user to make these changes.
To mark the HBA ports
- Display the QLogic HBA ports on the media server by using the nbhba command with the -l option. The following is an example; output on your system may differ:
/usr/openv/netbackup/bin/admincmd/nbhba -l 1 2312 21:00:00:E0:8B:83:9D:A1 "QLA2342 " 0 0 101 2 2312 21:01:00:E0:8B:A3:9D:A1 "QLA2342 " 1 0 101 3 2312 21:00:00:E0:8B:8F:28:7B "QLA2342 " 0 0 101 4 2312 21:01:00:E0:8B:AF:28:7B "QLA2342 " 1 0 101
For the QLA-234x series, the port WWNs on the same card differ in the second byte and the sixth byte. This output shows two, two-port HBAs. Lines 1 and 2 are one HBA; lines 3 and 4 are the other HBA. The HBAs are in initiator mode: the second rightmost column shows 0, and the rightmost column does not begin with 8.
Alternatively, use the nbhba -L option to produce verbose output, which lets you identify the mode more easily.
- Mark the ports by using the nbhba command. The following is the syntax:
/usr/openv/netbackup/bin/admincmd/nbhba -modify -wwn string -mode target
For example, the following two commands change the two ports on one of the HBAs from the example output in step 1:
nbhba -modify -wwn 21:00:00:E0:8B:8F:28:7B -mode target nbhba -modify -wwn 21:01:00:E0:8B:AF:28:7B -mode target
- Verify the changes by using the nbhba command and -L option to display the HBA card ports on the server. The following is an example; output on your system may differ:
/usr/openv/netbackup/bin/admincmd/nbhba -L HBA Port #1 Device ID = 2312 World Wide Name = 21:00:00:E0:8B:83:9D:A1 Model Name = "QLA2342 " Port = 0 Mode = initiator (designated for other use)(101) HBA Port #2 Device ID = 2312 World Wide Name = 21:01:00:E0:8B:A3:9D:A1 "QLA2342 Model Name = "QLA2342 " Port = 1 Mode = initiator (designated for other use)(101) HBA Port #3 World Wide Name = 21:00:00:E0:8B:8F:28:7B Slot = "" Port = 0 Fibre Not Attached Mode = target (designated for FT Server)(8101) HBA Port #4 World Wide Name = 21:01:00:E0:8B:AF:28:7B Slot = "" Port = 1 Fibre Not Attached Mode = target (designated for FT Server)(8101)
The nbhba -l option also produces the output that lets you identify the mode:
/usr/openv/netbackup/bin/admincmd/nbhba -l 1 2312 21:00:00:E0:8B:83:9D:A1 "QLA2342 " 0 0 101 2 2312 21:01:00:E0:8B:A3:9D:A1 "QLA2342 " 1 0 101 3 2312 21:00:00:E0:8B:8F:28:7B "QLA2342 " 0 1 8101 4 2312 21:01:00:E0:8B:AF:28:7B "QLA2342 " 1 1 8101
The rightmost two columns show the ports that are marked for target mode: the second rightmost column shows 1, and the rightmost column begins with 8. The other digits in the rightmost column are not significant.
- If necessary, transfer the HBAs to the appropriate media servers.
- If necessary, connect the HBAs to the SAN.
- Continue by configuring the FT services.
To revert to the initiator mode driver
- Invoke the nbhba command on the NetBackup FT server in which the HBA is installed. The following is the command syntax:
/usr/openv/netbackup/bin/admincmd/nbhba -modify -wwn world_wide_port_name -mode initiator