Collecting debug logs
The Collect Debug Logs Wizard helps you gather debug logs to a location on the master server. The debug logs are enabled using the Setup Debug Logging Wizard.
To collect debug logs
- In the NetBackup Administration Console, in the left pane, select the Logging Assistant node.
- The right pane of the NetBackup Administration Console displays the list of Logging Assistant records. Select the record whose debug logs you want to collect.
- In the Actions menu, select Collect Debug Logs. The Welcome panel for the Collect Debug Logs Wizard appears.
Click Next to continue.
- The Selected Host and Process panel appears. Use this panel to confirm the host problem categories and processes for all debug logs that you want to collect. The hosts can be the master server, one or more media servers, and one or more clients.
Click Next to continue.
- The Collect Debug Logs panel appears.
The following describes the parameters on this panel:
Specify Log Duration
In the Specify Log Duration area, click one of the following:
Collect available logs gathers all messages for the selected debug logs. Make sure that you want to collect this potentially large amount of data before you select this option.
Collect logs spanning this time period collects logs from one of three periods of time: The last 24 hours, the last 3 days, or the last week.
Collect logs for specific time period collects log messages that are generated within a precise time window. Specify the start date and time and the end date and time. The statement at the top of this panel indicates when the debug logs for this Logging Assistant Record were enabled. This date-time may affect the time window you select.
Collect nbsu output
Click Collect nbsu output to collect the NetBackup Support Utility (nbsu) information to be bundled. nbsu contains a wide range of diagnostic information that Technical Support can use to troubleshoot.
Calculate
Click Calculate to display the estimated available disk space and default log location for each selected host. Use this information to determine if an alternate temporary location is necessary.
If you click Calculate, go to step 6.
Otherwise, click Next and go to step 8.
- The Calculate Disk Space on Hosts panel appears.
This panel displays the free disk space information and the default temporary location for each of the selected hosts. Verify that the required disk space on the host for the debug logs does not exceed the available free space on that host. If it does, you can select the host entry, then click Change Temporary Location to change the log location on the host.
- The Change Temporary Location panel appears.
This panel lets you move debug logs to a different location on a host to avoid running out of disk space. Enter an alternate temporary directory path location for the logs in the text window, then click Check Free Disk Space. The Free disk space on temporary location entry changes from Unknown to the free space available on the alternate location. Compare that value with the Estimated required disk space for logs entry to determine if the space is sufficient. If necessary, repeat until you find an alternate log location with sufficient disk space.
Click OK to return to the Calculate Disk Space panel.
Click OK again to return to the Collect debug logs panel.
Finally, click Nextto continue.
- The Results panel displays the results of the collect operation. The progress of the operation is recorded in a file on the master server.
Monitor the progress of the collect operation by returning to the Logging Assistant main screen. The Progress column of the main screen changes as the operation progresses.
Click Finish to complete the Collect Debug Logs Wizard.
If you have a case ID provided by Technical Support in the form ########, rename the log files with the case ID number. Then manually upload the files to the Veritas Evidence Server. See the following article for more information: