Veritas NetBackup™ Appliance Troubleshooting Guide
- About using the Troubleshooting Guide
- Best practices
- About best practices
- Determining the NetBackup Appliance serial number
- About Fibre Channel HBA card configuration verification
- About Notification settings
- About IPMI configuration
- About password management and recovery
- About IPv4-IPv6-based network support
- About enabling BMR options
- About deleting users
- About troubleshooting tools
- Working with log files
- About NetBackup Appliance log files
- About the Collect Log files wizard
- Viewing log files using the Support command
- Where to find NetBackup Appliance log files using the Browse command
- Gathering device logs with the DataCollect command
- About gathering information for NetBackup-Java applications
- Enabling and disabling VxMS logging
- Disaster recovery
- About disaster recovery
- Disaster recovery best practices
- Disaster recovery scenarios
- Appliance sustained power interruption
- Appliance hardware failure
- Complete loss of appliance with recoverable operating system drives and attached storage disks
- Complete loss of appliance with recoverable attached storage disks
- Reimaging a NetBackup appliance from the USB drive
- Reconfiguring a 52xx master server appliance using the NetBackup Appliance Shell Menu
- Configuring a master server to communicate with an appliance media server
- Reconfiguring a 52xx or 5330 media server appliance using the NetBackup Appliance Shell Menu
- About NIC1 (eth0) port usage on NetBackup appliances
- Complete loss of appliance and attached storage disks
- NetBackup Appliance software corruption
- NetBackup Appliance database corruption
- NetBackup Appliance catalog corruption
- NetBackup Appliance operating system corruption
- NetBackup Appliance error messages
About gathering information for NetBackup-Java applications
If you encounter problems with the NetBackup-Java applications, use the following methods to gather data for support.
The following scripts are available for gathering information:
jnbSA (NetBackup-Java administration application startup script) | Logs the data in a log file in /usr/openv/netbackup/logs/user_ops/nbjlogs. At startup, the script tells you which file in this directory it logs to. Normally, this file does not become very large (usually less than 2 KB). Consult the file /usr/openv/java/Debug.properties for the options that can affect the contents of this log file. |
NetBackup-Java administration application on Windows | If NetBackup is installed on the computer where the application was started, the script logs the data in a log file at install_path\NetBackup\logs\user_ops\nbjlogs. If NetBackup was not installed on this computer, then no log file is created. To produce a log file, modify the last "java.exe" line in the following to redirect output to a file: install_path\java\nbjava.bat. If NetBackup was not installed on this computer, the script logs the data in a log file at install_path\Veritas\Java\logs. Note: When NetBackup is installed where the application is started, and when install_path is not set in the |
/usr/openv/java/get_trace | UNIX/Linux only. Provides a Java Virtual Machine stack trace for support to analyze. This stack trace is written to the log file that is associated with the instance of execution. |
UNIX/Linux: /usr/openv/netbackup/bin/support/nbsu Windows: install_path\NetBackup\bin\support\ nbsu.exe | Queries the host and gathers appropriate diagnostic information about NetBackup and the operating system. |
The following example describes how you can gather troubleshooting data for Veritas Technical Support to analyze.
An application does not respond. | Wait for several minutes before you assume that the operation is hung. Some operations can take quite a while to complete, especially operations in the Activity Monitor and Reports applications. |
UNIX/Linux only: Still no response after several minutes. | Run /usr/openv/java/get_trace under the account where you started the Java application. This script causes a stack trace to write to the log file. For example, if you started jnbSA from the root account, start /usr/openv/java/get_trace as root. Otherwise, the command runs without error, but fails to add the stack trace to the debug log. This failure occurs because root is the only account that has permission to run the command that dumps the stack trace. |
Get data about your configuration. | Run the nbsu command that is listed in this topic. Run this command after you complete the NetBackup installation and every time you change the NetBackup configuration. |
Contact Veritas Technical Support | Provide the log file and the output of the nbsu command for analysis. |