Veritas NetBackup™ SAN Client and Fibre Transport Guide
- Introducing SAN Client and Fibre Transport
- Planning your deployment
- Planning your SAN Client deployment
- About SAN Client best practices
- 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
About unified logging
Unified logging and legacy logging are the two forms of debug logging used in NetBackup. All NetBackup processes use one of these forms of logging. Server processes and client processes use unified logging.
Unified logging creates log file names and messages in a standardized format. These logging files cannot be easily viewed with a text editor. They are in binary format and some of the information is contained in an associated resource file. Only the vxlogview command can assemble and display the log information correctly.
Unlike legacy logging, unified logging does not require that you create logging subdirectories. Log files for originator IDs are written to a subdirectory with the name specified in the log configuration file. All unified logs are written to subdirectories in the following directory:
Windows | install_path\NetBackup\logs |
UNIX | /usr/openv/logs |
You can access logging controls in the NetBackup Administration Console. In the left pane, expand or . Double-click the server you want to change. In the left pane of the dialog box, click .
You can also manage unified logging by using the following commands:
vxlogcfg | Modifies the unified logging configuration settings.
|
vxlogmgr | Manages the log files that the products that support unified logging generate. |
vxlogview | Displays the logs that unified logging generates. |
These commands are located in the following directory:
Windows | install_path\NetBackup\bin |
UNIX | /usr/openv/netbackup/bin |
See the NetBackup Commands Reference Guide for a complete description about these commands.
More information about legacy logging is available.