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 using the vxlogview command to view unified logs
Use the vxlogview command to view the logs that unified logging creates. These logs are stored in the following directory.
UNIX | /usr/openv/logs |
Windows | install_path\NetBackup\logs |
Unlike the files that are written in legacy logging, unified logging files cannot be easily viewed with a text editor. The unified logging files 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.
You can use vxlogview to view NetBackup log files as well as PBX log files.
To view PBX logs using the vxlogview command, do the following:
Ensure that you are an authorized user. For UNIX and Linux, you must have root privileges. For Windows, you must have administrator privileges.
To specify the PBX product ID, enter -p 50936 as a parameter on the vxlogview command line.
vxlogview searches all the files, which can be a slow process. Refer to the following topic for an example of how to display results faster by restricting the search to the files of a specific process.