Veritas NetBackup™ Troubleshooting Guide
- Troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting vnetd proxy connections
- Troubleshooting security certificate revocation
- Verifying host name and service entries in NetBackup
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- About troubleshooting Auto Image Replication
- Using NetBackup utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the robotic test utilities
- Disaster recovery
- About disk recovery procedures for UNIX and Linux
- About clustered NetBackup server recovery for UNIX and Linux
- About disk recovery procedures for Windows
- About clustered NetBackup server recovery for Windows
- About recovering the NetBackup catalog
- About NetBackup catalog recovery and OpsCenter
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup relational database
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:
(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.
When NetBackup is installed where the application is started, and when install_path is not set in the
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.
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.
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.