05.01.2013 Views

NetBackup Troubleshooting Guide - Zedat

NetBackup Troubleshooting Guide - Zedat

NetBackup Troubleshooting Guide - Zedat

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Problem Report Information<br />

Follow these steps to get debug data for VERITAS support to analyze:<br />

1. If the application does not respond for a long time, it may be hung. However, some<br />

operations can take quite a while to complete. This is especially true in the Activity<br />

Monitor and Reports applications. So, wait for several minutes before assuming the<br />

operation is hung.<br />

If there is no response within several minutes, execute<br />

/usr/openv/java/get_trace under the account where you started the Java<br />

application. This causes a stack trace to be written to the log file.<br />

For example, if you started jnbSA from the root account, start<br />

/usr/openv/java/get_trace as root. Otherwise, the command executes without<br />

error, but fails to add the stack trace to the debug log. This occurs because root is the<br />

only account that has permission to execute the command that dumps the stack trace.<br />

2. Execute /usr/openv/netbackup/bin/goodies/support to get data about your<br />

configuration. Execute this script after completing <strong>NetBackup</strong> installation and each<br />

time after you change the <strong>NetBackup</strong> configuration.<br />

3. Provide the support-script output and log file to VERITAS support.<br />

8 <strong>NetBackup</strong> <strong>Troubleshooting</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!